Hi Guys, We're having a repeat problem with the above event each night when maintenance is run. From my digging around on various forums, there are some great responses regarding IIS Host Headers and missing Schedule+ Free Busy system folders however this does not match my case. Can someone please provide some more pointers on resolving this one - here is the event detail... Application log generated Error Event 8277 on gguswsfo001.server.physical.us.bfc For more information see http://www.eventid.net/display.asp?eventid=8277&source=MSExchangeFBPublish Log: Application Type: Error Event: 8277 Agent Time: 2010-08-27 19:03:59Z Event Time: 09:00:55 AM 27-Aug-2010 UTC Source: MSExchangeFBPublish Category: General Username: N/A Computer: xxxxxx Description: Error while getting sorted message table for duplicate message deletion on virtual machine xxxxxx. The error number is 0x80004005. For more information, click http://www.microsoft.com/contentredirect.asp.

What’s the exchange version? I assume it’s exchange 2003, please correct me if it’s not You have also verified that the host name is blank in the default website (The one that contains /Exadmin virtual directory), right? Have you verified the replica list of the subfolders under the “Schedule+ Free Busy” folder? Have you assigned the valid IP address in the IIS? Have you seen KB 555406?James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Hi there James and thankyou for your reply. I have checked KB 555406 just now and the siteFolderServer is indeed correct as it should be. I can also confirm that this server is Exchange 2003 SP 2, IIS has a blank host header (is only using Default Website). As for valid IP in IIS - it is set to Unassigned, so I can't see any problem there. Before I posted here, I had configured a replica on all exchange servers for the Schedule+ Free/Busy folder (it was currently only on the affected server), forced a replication however that night still logged an error when maintenance kicked in. Now since that night, I've not seen another error. Perhaps there was an issue with replication that took longer than expected? Not sure - but that was the 31st of August and no error since. I would be happy to mark this one as answered, and the fix being adding other replicas of the Schedule+ Free/Busy folder. Regards, Nathan.