Topic Last Modified: 2008-07-23

Product Name

Exchange

Product Version

8.0

Product Build Number

8.0

Event ID

8207

Event Source

MSExchangeFBPublish

Component

Cdopt

Symbolic Name

evtPublicFolderUpdateFailed

Message Text

Error updating public folder with free/busy information on virtual machine %1. The error number is %2.

Explanation

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. This event may occur if the public folder store, where Free Busy information is published, is in the Dismounted state.

  • If the specific error number displayed is 0x80070005, this Error event indicates that the Public Folder with the object class of MsexchPFtree, used for the Schedule+ Free Busy information, is missing from its expected location of CN=Folder Hierarchies,CN= Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>

User Action

To resolve this error, follow these steps:

  1. Make sure that at least one public folder store in your Exchange organization is in the Mounted state.

  2. Review other related Error and Warning events in the Application and System log. These related events may help you find the root cause of this event.

  3. If the error number displayed is 0x80070005, use the procedure below to determine the cause and resolution for the error.

ADSI Edit can be run from a client computer or server. The computer does not have to be a member of a domain, but the user must have the rights to view and edit the Active Directory directory service domain to which the user is connecting. For more information about how to use ADSI Edit, see Adsiedit Overview.

Important:
If you use ADSI Edit or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, serious problems may occur. These problems may require you to reinstall Windows Server 2003, Exchange 2007, or both Windows Server 2003 and Exchange 2007. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
To use ADSI Edit to verify the location of the CN=Public Folders container

  1. Use ADSI Edit to see if the CN=Public Folders container is present under the default location of CN=Folder Hierarchies,CN= Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>.

    1. If the CN=Public Folders container is not present in the default location, check to see if it has been moved to CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>.

    2. If the CN=Public Folders is located at CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>, move it back to the default location of CN=Folder Hierarchies,CN= Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain> and restart the information store service.

  2. If the CN=Public Folders container is not present in the default location of CN=Folder Hierarchies,CN= Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain> and the parent container CN=Folder Hierarchies is also missing, use the steps below to create the CN=Folder Hierarchies under the CN= Exchange Administrative Group (FYDIBOHF23SPDLT) container.

    1. Right-click the CN= Exchange Administrative Group (FYDIBOHF23SPDLT) container, point to New, and then click Object.

    2. From the Select a class list, click msExchPublicFolderTreeContainer, and then click Next.

    3. On the Attribute: cn page, in the Value box, enter Folder Hierarchies and then click Next.

    4. Click Finish to create the Folder Hierarchies object.

    5. Right-click the newly created CN=Folder Hierarchies object, then click New, and then Object.

    6. From the Select a class list, select msExchPFTree and then click Next.

    7. For the Value box, type Public Folders, and then click Next.

    8. Use the Exchange Management Console to dismount and then mount the public folder store.

  3. If the steps above do not resolve the issue,

    1. Dismount the public folder store and make a copy of the public folder store files, Pub1.edb and Pub1.stm.

    2. Rename the original Pub1.edb and Pub1.stm files to Pub1Old.edb and PubOld1.stm

    3. Mount the public store, causing the creation of new Pub1.edb and Pub1.stm files.

    4. Again dismount the public folder store and this time rename the public folder store files Pub1.edb and Pub1.stm to something different.

    5. Rename the Pub1Old.edb and PubOld1.stm from step 3b. to the original filenames of Pub1.edb and Pub1.stm in their original location.

    6. Mount the Public Folder Store and restart the Information Store service. The issues should now be resolved.

Note  If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.