Problem solve Get help with specific problems with your technologies, process and projects.

Registry-related Exchange replication failure

Exchange 5.5 and Exchange 2000 use a certain registry key to govern how replication behaves. If this key is damaged or has an invalid value written to it, replication may fail.

Please let others know how useful this tip is via the rating scale at the end of it. Do you have a useful Exchange or Outlook tip, timesaver or workaround to share? Submit it to our tip contest and you could win a prize.


Exchange 5.5 and Exchange 2000 use a certain registry key to govern how replication behaves -- i.e., whether to disable it completely, use the standard defaults, or use replication period overrides specified elsewhere in the registry.

If this key is damaged or has an invalid value written to it, replication may fail. Neither the public folder hierarchy, nor the content of folders, will replicate to or from the server in question.

The most obvious symptom (aside from replication not working, of course) is Event ID 3093 appearing in the Exchange application log, along with the following error description:

Error -2147221233 reading property 0x67480014 on object type tbtOwningFolders from database "First Storage Group\Public Folder Store <computer>"

-- where <computer> is the name of the Exchange server.

The registry entry that controls replication for a given Exchange server is found at:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\<servername>\Public-<guid>

-- where <servername> is the name of the server, and <guid> is the GUID for the public store on that server.

Within this key is a decimal value named Replication, which can have three values:

  • 0: Replication is disabled.
  • 1: Replication is enabled with the default settings.
    (Hierarchy replication takes place every five minutes and content replication occurs every 15 minutes.)
  • 2: Replication is enabled with override settings for public folder replication.

Delete the Replication value entirely and restart the server to see if this affects replication. Note that if the Replication value is missing, Exchange will assume that replication is enabled with the default settings.

About the author: Serdar Yegulalp is editor of the Windows 2000 Power Users Newsletter and a regular contributor to SearchExchange.com.


Do you have comments on this tip? Let us know.
Related information from SearchExchange.com:

  • Tip: Watch out for replication failures in mixed Exchange environments
  • Reference Center: Exchange replication and synchronization tips and resources



  • Dig Deeper on Microsoft messaging and collaboration services

    Start the conversation

    Send me notifications when other members comment.

    Please create a username to comment.

    -ADS BY GOOGLE

    SearchServerVirtualization

    SearchCloudComputing

    SearchSQLServer

    SearchEnterpriseDesktop

    SearchVirtualDesktop

    Close