Msexchangefbpublish error updating public folder
Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers.Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. For more information, see Resources to help you upgrade your Office 2007 servers and clients.Make sure Autodiscover and OAB URL are set correctly,to set the URL follow KB This entry was posted on November 4, 2011 at am and is filed under Exchange Server 2007 Posts.You can follow any responses to this entry through the RSS 2.0 feed.This Error event indicates that the Microsoft® Exchange Server that logged this event did not update a public folder that has Schedule Free Busy information.Schedule Free Busy information is published to a public folder for Microsoft Office Outlook® 2003 or earlier clients.
These problems may require you to reinstall Windows Server 2003, Exchange 2007, or both Windows Server 2003 and Exchange 2007.This topic provides information about why you receive the following error message in the Administrative Events log or the Application log on a computer that is running Microsoft Exchange Server 2007: This issue occurs when the CN=Folder Hierarchies container is missing under the First Administrative Group or when the CN= Public Folders name does not exist under the CN=Folder Hierarchies container for the First Administrative Group in Exchange 2007.Exchanhe server you have Exchange OAB folder which is shared (this will be -created if 2007 server is generating OAB)and you will see a folder inside it with guid value.(It was done by another company so I'm not sure how they went about doing it) I have run the following command in the Exchange 2007 Shell: get-publicfolder -Identity "\NON_IPM_SUBTREE\SCHEDULE FREE BUSY" -Recurse | fl name, Replicas The result: Name : SCHEDULE FREE BUSY Replicas : Name : EX:/o= refers to the name of the server where the information store was migrated from, it no longer exists on the network.Does anyone have any suggestions on what might be causing the problem or how to fix it? when I run step 1 I get the following output Name : SCHEDULE FREE BUSY Replicas : Name : EX:/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT) Replicas : Name : EX:/o=First Organization/ou=First Administrative Group Replicas : Now the article should fix the line relating to Schedule Free Busy however should I be concerned about the last line relating to First Administrative Group as this relates to the old Exchange 2003 server which is now decommissioned? 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.The user would see this error in Outlook when attempting to see another users schedule: Event Type: Error Event Source: MSExchange FBPublish Event Category: General Event ID: 8207 Date: 8/05/2007 Time: PM User: N/A Computer: EXCHSVR Description: Error updating public folder with free/busy information on virtual machine exchsrvr. After a bit of digging around, it occurred to me that I’d missed adding the new server to the Public Folder replicas.To add the replicas you will need to get the list of the sub-folders of the SCHEDULE FREE BUSY folder.New computers are added to the network with the understanding that they will be taken care of by the admins.Keeping an eye on these servers is a tedious, time-consuming process.