Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. The hierarchy of a new public folder database does not replicate on an Exchange Server 2010 SP1 server

The hierarchy of a new public folder database does not replicate on an Exchange Server 2010 SP1 server

View products that this article applies to.

Symptoms

You create a new public folder database on a Microsoft Exchange Server 2010 Service Pack 1 (SP1) server. However, the public folder hierarchy is not replicated from other public stores to this new database. Additionally, the following events are logged in the Application log:
Log Name: Application
Source: MSExchangeIS Public Store
Date: Date
Event ID: 3079
Task Category: Replication Errors
Level: Error
Keywords: Classic
User: N/A
Computer: Computer
Description:
Unexpected replication thread error 0x80070057 on database " First Storage Group\Public Folder Store (Server_Name)".


Log Name: Application
Source: MSExchangeIS Public Store
Date: Date
Event ID: 3089
Task Category: Replication Errors
Level: Warning
Keywords: Classic
User: N/A
Computer: Computer
Description:
Error 0x80070057 occurred while processing an incoming replication message on Public Folder Store " First Storage Group\Public Folder Store (Server_Name)".
Note The events are logged every time when the server tries to backfill the hierarchy.

↑ Back to the top

Cause

This issue occurs because the ReplidMap table in the public folder database contains a zero Global Universal Identification (GUID).

↑ Back to the top

Resolution

To resolve this issue, install the following update rollup:
2645995 Description of Update Rollup 1 for Exchange Server 2010 Service Pack 2
Note This update enables users who cannot run the isinteg command to skip the zero GUID check. For more information about how to run the isinteg command to resolve this issue, click the following article number to view the article in the Microsoft Knowledge Base:
2506049 The hierarchy of a new public folder database on an Exchange Server 2010 SP1 server is not replicated
After you apply this update, disable zero GUID detection for public folders on Exchange Server 2010 servers.

To have us disable zero GUID detection for public folders, go to the "Fix it for me" section. If you prefer to disable zero GUID detection for public folders yourself, go to the "Let me fix it myself" section.

Fix it for me



To disable zero GUID detection for public folders automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.




Notes
  • Install hotfix that is described in Microsoft Knowledge Base (KB) article 2645995 before you run this Fix it solution.
  • This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.
  • If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.

Then, go to the "Did this fix the problem?" section.



Let me fix it myself

To disable zero GUID detection for public folders, follow these steps on Exchange Server 2010 servers:
  1. Click Startstart button , type regedit in the Start Search box, and then press Enter.
  2. Locate and then click the following registry key:
    HKLM/SYSTEM/CurrentControlSet/Services/MSExchangeIS/ParametersPublic
  3. Click Edit, point to New, and then click DWORD Value.
  4. Type Disable Zero Guid Detection For Public Folders, and then press Enter.
  5. Click Edit, and then click Modify.
  6. In the Value data box, type 1.
  7. Exit Registry Editor.

Did this fix the problem?

  • Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support.
  • We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog or send us an email.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseinter, kbfixme, kbmsifixme, kb

↑ Back to the top

Article Info
Article ID : 2640218
Revision : 1
Created on : 1/7/2017
Published on : 6/26/2012
Exists online : False
Views : 332