Error 80004005-501-4B9-560

[Gokul20]

I have an Exchange server and all clients running Outlook 2003. Most recently I installed Office 2007 in a client, and you exploit Outlook 2007 for e-mail client. It is slow, and could one day it is not connected to the Exchange server, so I have to push Send / Receive often. Then I uninstall Office 2007 and back to 2003. Auspiciously, I had not uninstalled Office 2003 (with the exception of Outlook 2003, I had uninstalled it). So, I reinstalled Outlook 2003. Everything seems ok, except I do not have the global address list from Exchange Server. It does not download the address book from Exchange Server. It is the synchronization error: 16 Error synchronizing folder [80004005-501-4B9-560]. I didn't find any appropriate solutions on Internet. So thought that you would be helpful.

[Janet J]

You should try the following things,
Turn off offline files and folders, get convinced that the client is not in cached mode, delete any ost files (*.ost) if it is present on the machine. Also be persuaded that you search hidden files and folders are exposed when doing this search. Then put the client back in cached mode or offline files/folders, whichever you have configured and permit it to resync.

[machok]

According to me, your problem seems to be generating because of the Public Folder Replicas. You can store the same content of public folders on several computers running Microsoft Exchange Server by creating replicas of public folders. In doing so, you can make the information contained in public records available for multiple users. However, when you create replicas of your public folders, update Exchange Server needs to public folder replicas to make sure they all contain the same data.

[Dodge]

Exchange Server executes this function by conveyance and receiving replication messages among Exchange Server computers that restrains a replica of the public record public records. If the public folder replication does not work appropriately in your organization, you can use these messages replication to follow all the following:

• If a computer sends messages of public folder replication.
• If a computer receives messages from public folder replication.
• If a computer responds to messages received public folder replication.

[Pauline]

In Exchange 2000 Server and in Exchange Server 2003, all public folder replication is based messages. These messages from public folder replication are hurled from public folder store one to an additional public folder store. Messages in public folder replication cannot be flinged or delivered if the objects of public folder store have not been embossed with proxy addresses by the service recipient update configuration Enterprise.

[wllwnn]

Usually, if this problem subsists, Exchange Server computer that includes the public folder store is not marked do not receive the public folder hierarchy from another Exchange Server. Therefore, the Exchange Server computer that contains the public folder store is not marked do not distinguish a list of public folders, excluding for public folders that were produced locally using the Exchange System Manager tool. Devoid of this public folder hierarchy, no public record can be replicated. To restate this, the public folder hierarchy must be replicated before the public folder content can be replicated.