Home / file parsed but not updating / Msexchangefbpublish and error updating busy

Msexchangefbpublish and error updating busy

When done, mount the information store in the exchange system manager.

This error was in fact generated due to the autonegotiate port configuration of a switch.

This resulted in Outlook 2003 clients unable to see Free/Busy information when creating a meeting request.

Transient occurrences of this event are not a problem, but if the recurrence is every 25 to 30 minutes, then Free/Busy Publishing is down for all Outlook Web Access (OWA) users. After the upgrade, the Information Store was unable to mount.To add the replicas you will need to get the list of the sub-folders of the SCHEDULE FREE BUSY folder.You can see this list with this command (replace with the name of your server): [code]Get-Public Folder -server exchsvr "non_ipm_subtree SCHEDULE FREE BUSY" -recurse | Format-List[/code] Then to add the replicas run these commands (you’ll have to add your own server and organisation names): [code]Set-Public Folder -Identity "NON_IPM_SUBTREESCHEDULE FREE BUSYEX:/o=Company/ou=First Administrative Group" -Replicas "exchsrvr Public Folder Database" Set-Public Folder -Identity "NON_IPM_SUBTREESCHEDULE FREE BUSYEX:/o=Company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)" -Replicas "exchsrvr Public Folder Database"[/code] Once I did this and ran OUTLOOK.The server network card had 100 full duplex and the switch port 100 half duplex.The switch port was changed to 100 full duplex and Autonegotiate disabled and all is workking fine after without any reboot.This event was accompanied with event id 8206 from MSExchange FBPublish.I recently added 2 new Exchange 2000 servers to my 5.5/2000 mixed environment (running parallel while migration is taking place), and encountered this error on both servers after installing Exchange 2000 server SP3.I eliminated the error by stopping Exchange System Attendant and its dependent services, then restarting SA and each dependency individually.MS Exchange Free Busy Publish then initialized properly. Clicking on the link in the 8197 log entry, I found a suggestion from Microsoft to restart the System Attendant service.During a migration from Exchange Server 2003 to Exchange Server 2007 you need to add the Exchange 2007 server to replicas for each of the Public Folders (as you would need with any Exchange server migration) and this includes the System folders as well.In our case I missed the SCHEDULE FREE BUSY folder.


  1. Event ID 8197 Source MSExchangeFBPublish. As per Microsoft "Free/Busy Publishing has encountered errors when attempting to log on to the private or public Exchange. After the upgrade, the Information Store was unable to mount.

  2. Fixes an issue in which certain free/busy messages are not replicated from an Exchange Server 2010 server to an Exchange Server 2003

  3. Oct 6, 2017. Learn to Update BUSY to Latest Release. Update BUSY to Latest Release Hindi. BUSY Accounting Software. Loading. Unsubscribe from.

Leave a Reply

Your email address will not be published. Required fields are marked *