Outlook synchronization error [80004005-501-4B9-560] with a Microsoft Exchange Server 2010 mailbox

Outlook synchronization error [80004005-501-4B9-560] with a Microsoft Exchange Server 2010 mailbox

  • Comments 4
  • Likes

I’ve seen a couple of cases where Outlook users get the following error in the \Sync Issues folder:

17:27:28 Synchronizer Version 14.0.4760
17:27:28 Synchronizing Mailbox 'user name'
17:27:28 Synchronizing Hierarchy
17:27:44 Synchronizing Forms
17:27:44 Downloading from server 'server.corp.com'
17:27:45 Error synchronizing folder
17:27:45 [80004005-501-4B9-560]
17:27:45 The client operation failed.
17:27:45 Microsoft Exchange Information Store
17:27:45 For more information on this failure, click the URL below:
17:27:45 http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80004005-501-4b9-560
17:27:45 Done

The following is from a soon to be publicly published article. Many thanks to Charlotte Raymundo and Greg Mansius for writing and editing this article!

Outlook synchronization error [80004005-501-4B9-560] with a Microsoft Exchange Server 2010 mailbox

Symptoms

If you view the \Sync Issues folder in Microsoft Outlook, you find a synchronization log with an entry similar to the following:

17:27:28 Synchronizer Version 14.0.4760
17:27:28 Synchronizing Mailbox 'user name'
17:27:28 Synchronizing Hierarchy
17:27:44 Synchronizing Forms
17:27:44 Downloading from server 'server.corp.com'
17:27:45 Error synchronizing folder
17:27:45 [80004005-501-4B9-560]
17:27:45 The client operation failed.
17:27:45 Microsoft Exchange Information Store
17:27:45 For more information on this failure, click the URL below:
17:27:45 http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80004005-501-4b9-560
17:27:45 Done

Cause

The 4B9 portion of the error code translates to ecNullObject from Store, indicating that the failure occurred because an object that was referenced was null.  This could be due to number of resons including, but not limited to, a permissions issue or because the Outlook client is not able to access the public folder replica.

Resolution

Possible Resolutions:

Resolution 1:  Problems with the Replica

If there are multiple Exchange servers in the environment there could be a possible replication issue with the EFORMS REGISTRY system folder, removing the replica and adding it back has resolved the issue in some cases.

Use the following commands to remove and re-add the replica:

  1. To check which Public Folder Database the Exchange Mailbox is using, run the following cmdlet in Exchange Management Shell:

    get-MailboxDatabase |fl Name, PublicFolderDatabase

    Example:
    Name                        :  MailboxDatabase1
    Public Folder Database:  Public Folder Database 1

    Name                        :  MailboxDatabase2
    Public Folder Database:  Public Folder Database 2 <-- Users on this mailbox database are getting the sync errors

    Name                        :  MailboxDatabase3
    Public Folder Database:  Public Folder Database 1

  2. To get a list of the replicas for the EFORMS REGISTRY run the following cmdlet:

    get-publicfolder -Identity "\NON_IPM_SUBTREE\EFORMS REGISTRY" -Recurse | fl Name,Replicas

    Example:
    Name      : EX:/o=contoso/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)
    Replicas : {Public Folder Database 1}

    Name      : EX:/o=contoso/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)
    Replicas : {Public Folder Database 2}

     

  3. Remove the replica from the database you found in step #1.  This is most easily accomplished using the Public Folder Managment Console from Exchange Management Console (EMC):

    1. In the console tree, click Toolbox.

    2. In the result pane, double-click Public Folder Management Console.

    3. In the console tree of the Public Folder Management Console, expand System Public Folders, and then expand the EFORMS REGISTRY public folder and click on Organizational Forms Library.
    4. In the result pane, click the public folder you want, and then, in the action pane, click Properties.
    5. Use the Replication tab to view the and set the content replication schedule and to specify the databases on which the public folder content will be replicated.

      • Under Replicate content to these public folder databases select a database from the list

      • Click the X to remove it from the replication list.

  4. Re-Add the replica from the database you found in step #1 using the same Public Folder Management Console:

    1. In the console tree, click Toolbox.

    2. In the result pane, double-click Public Folder Management Console.

    3. In the console tree of the Public Folder Management Console, expand System Public Folders, and then expand the EFORMS REGISTRY public folder and click on Organizational Forms Library.

    4. In the result pane, click the public folder you want, and then, in the action pane, click Properties.

    5. Use the Replication tab to view the and set the content replication schedule and to specify the databases on which the public folder content will be replicated.

      • Under Replicate content to these public folder databases click the Add button to open the Select Public Folder Database dialog box.  Use this dialog box to specify which public folder databases this public folder should be replicated to. 

      • Select the public folder database, and then click OK
         

Resolution 2:  Problems with the Permissions

The error can be caused by incorrect permissions on the EFORMS REGISTRY for the Default user.

  1. To check permissions on the EFORMS REGISTRY, run the following cmdlet in the Exchange Management Shell:

    Get-PublicFolderClientPermission “\NON_IPM_SUBTREE\EFORMS REGISTRY” | fl user, accessrights

Example:
User           : Default
AccessRights: {Reviewer}

User           : Anonymous
AccessRights: {None}

  1. In the output, examine the permissions given to the Default user.  They should not be set to None.  The following is a list of accepted permissions for the Default user: 

    - Owner
    - PublishingEditor
    - Editor
    - PublishingAuthor
    - Author
    - NonEditingAuthor
    - Reviewer
    - Contributor
  2. If the Default user has it's permissions set to None, run the following command to set the permissions to Reviewer

    Add-PublicFolderClientPermission “\NON_IPM_SUBTREE\EFORMS REGISTRY” -User Default -AccessRights Reviewer

More Information

For more information about the Set-PublicFolder command, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/aa998596.aspx

For more information about the Add-PublicFolderClientPermission command, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/bb124743.aspx

Configure Public Folder Properties
http://technet.microsoft.com/en-us/library/bb691327.aspx

 

Comments
  • <p>I have also seen encoutered this error message. This seemed to be a know issue with Exchange 2010, I made a post regarding this, please see my post :)</p> <p><a rel="nofollow" target="_new" href="http://curly-live.hubpages.com/t/2e636f">curly-live.hubpages.com/.../2e636f</a></p>

  • <p>I have also seen this error occur when an automated Outlook client process copies/creates a message and then deletes it. &nbsp;I haven&#39;t done timing threshold analysis, but the errors I&#39;m seeing occur when a copy/delete occur within about 30 seconds of each other. &nbsp;So far, I&#39;ve only noticed the error when the Outlook client is running in Cached-Mode.</p> <p>This can be disconcerting because, in this case, they&#39;re not really errors at all. &nbsp;Is there anyway to control the logging of this error on the basis of the application or the Outlook Folder ?</p>

  • <p>This was a known bug which I reported to Microsoft Support last year. &nbsp;Exchange 2010 SP RU3 has fixed the issue. &nbsp;I have confirmed that I no longer receive this error after the SP2 RU3 update.</p>

  • <p>Hi Ken, in our environment SP2 RU3 didn&#39;t fixed this issue.</p>

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment