Archive for Exchange 2007 Public Folders

MSExchangeIS 9519 0x972: Public Folders Container Deleted, or Missing Required Attributes

The Microsoft Exchange Database Troubleshooter Tool detected one or more MSExchangeIS 9519 events with error code 0x972 in the Application log. This indicates a failure of public folder databases to mount because the Public Folders container has been deleted or is missing needed attributes.


This error can occur when the Public Folders container has been deleted from Active Directory, or if the affected Public Store is not configured to use the Public Folders container, that is, the value for the Public Folder containers msExchOwningPFTreeBL attribute does not point to the Public Store. The most likely cause for this error is that the Administrative Group that contained the Public Folders container was deleted without the Public Folders container first being moved to a new Administrative Group.

User Action

To resolve this issue, use the ADSI Edit, or a similar tool, to determine whether the Public Folders container exists and the msExchOwningPFTreeBL attribute is properly configured to point to the relevant Public Store.
To determine the cause of the error

1. Using ADSI Edit or a similar tool, locate each administrative group object in Active Directory.

The Administrative Group object can be found at:

CN=Configuration,CN=Services,CN=Microsoft Exchange,CN=Organization,CN=Administrative Groups,CN=Administrative group

2. Expand each Administrative Group and check for the existence of a CN=Folder Hierarchies container. If the CN=Folder Hierarchies container exists, highlight the container and verify that a CN=Public Folders object exists in the right-hand pane. If no CN=Public Folders object exists under any Administrative Group, move on to Solution 1, Recreate Folder Hierarchies and Public Folders containers. If you do find a CN=Public Folders container, proceed to step 3.

3. Right-click the CN=Public Folders object, and then click Properties.

4. In the Attributes list, select the msExchOwningPFTreeBL attribute, and then click Edit.

5. Make sure that the affected Public Folder Store is shown in the Values list. If it is not listed, proceed to Step 2

Step 1: Recreate Folder Hierarchies and Public Folders containers

Open adsiedit.msc.

Select Configuration-Configuration-Services-Microsoft Exchange-Orgname-Administrative Groups-Exchange Administrative Group.

Create the “Folder Hierarchies” under the Exchange Administrative Group

1. Right click on Exchange Administrative Group

2. Select New Object

3. Select msExchPublicFolderTreeContainer for the class and click Next

4. Enter the following for the value: Folder Hierarchies, click Next

5. Click Finish

Create Public Folder Tree Object

1. Right click CN=Folder Hierarchies -> New Object

2. Selected msExchPFTree for the class

3. For the value we entered, “Public Folders” and clicked next

4. Clicked on the “More Attributes” button, selected msExchPFTreeType and set the

value to 1. Note: This is very important that this value is set to a value of 1 as

this tells Exchange that this is a MAPI Tree

5. Click Ok and then finish

Step 2: Repopulating the value of the msExchOwningPFTreeBL attribute for the Public Folders container object

Populate msExchOwningPFTreeBL attribute object of the PF Stores in the organization

(Since this attribute is not directly editable, you have to follow the below steps

to do this for each PF store)

. Get properties of the newly created “Public Folders” Tree object in ADSIEdit.

2. Copy the distinguishedname value to the clipboard and then click cancel.

3. Navigate to the Storage group that contains the Public Folder Store for this

server and get properties of the server. In my case it was : Configuration – CN=Services – CN=Microsoft Exchange – CN= Administrative Group –
CN=Servers – CN=E2007 – CN=InformationStore – CN=Second storage group. Right click on CN=Public folder Database

4. Locate the msExchOwningPFTree attribute and paste in the value that was copied

to the clipboard in step 2. Click OK.

5. Restart the Information Store Service

6. Now try to  mount the PF store and see if we can access it fine now.


Comments (2)