| Event Id | 3093 |
| Source | MSExchangeIS Public |
| Description | The replication startup status message was not sent out. |
| Event Information | According to Microsoft: It is strongly recommended that this registry entry only be used in the in cases described in the Symptoms section. Setting this registry entry and preventing the status messages from going out on startup has the following caveats: 1. If a replication connector between 2 Exchange Sites is torn down, the system folders from the foreign Site are marked as removed and they will not show up in the Systems Folder hierarchy. If these Sites are reconnected, the System folders from the foreign Site will still not show up since we are preventing the status message, which is the message that causes the marked as removed flag to be reset, from reaching the other Site. This registry entry must be set to 0, and then the IS re-started to get the System Folders to synch up again. 2. Public Folder hierarchies may temporarily become out of synch because changes are only known to other Sites when an actual hierarchy change message is received. WORKAROUND: You can do the following to try to work around this problem: 1. Remove the public information store from any Exchange Server computer possible. This will only be valid in multi-server sites with a dedicated public folder server. 2. Increase the speed of the WAN links where/when possible. 3. Perform ONLINE backups of the information store. |
| Reference Links | XADM: Disabling Public Folder Replication Status Messages on Information Store Startup |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.