Search Engine: Elastic

Article ID: 114263, created on Jul 2, 2012, last review on May 8, 2014

  • Applies to:
  • Operations Automation


A customer cannot create Hosted Exchange 2010 mail-enabled public folder in POA Control Panel, the task Create public folder fails with error message 'Unable to get Public Polder proxy DN: exiting by time out' like in the example below:Task ID                 326944
Task name               Create public folder 'TestPF' (id=7)
Task description        Create public folder 'TestPF' (id=7)
Queue name              DomainService00001304
Method name             addPublicFolderHandler
Execution status        Failed   
Start not earlier than  Apr-23-2012 11:19
Finished                Apr-23-2012 11:28
Output  Destination host '' (#101), IP '' :  Provisioning request failed. Unknown error 0x80131600 [<response><errorContext description="Unable to get Public Polder proxy DN: exiting by time out" code="0x80131600" executeSeqNo="5"><errorSource namespace="Exchange2010ProviderEx" procedure="MailEnableFolder"/><errorSource namespace="SW Managed Exchange" procedure="MailEnableFolder"/></errorContext></response>]

The problem affects only mail-enabled public folders.


Exchange installation is misconfigured.

POA is trying to run Exchange 2010 cmdlet Get-MailPublicFolder and it fails to be executed properly with the error message:[PS] C:\Windows\system32>Get-MailPublicFolder -Identity \P001011182
Can't log on to the Exchange Mailbox server ''. No existing 'PublicFolderProxyInformation' matches
the following Identity: '\P001000182'. Make sure that you specified the correct 'PublicFolderProxyInformation' Identity
and that you have the necessary permissions to view 'PublicFolderProxyInformation'..
    + CategoryInfo          : NotSpecified: (0:Int32) [Get-MailPublicFolder], MapiLogonFailedException
    + FullyQualifiedErrorId : 24913CE0,Microsoft.Exchange.Management.MapiTasks.GetMailPublicFolder


Make sure that the following conditions are satisfied:
  • Each mailbox server in Exchange cluster has at least one mailbox database in mounted state
  • If mailbox database is already mounted - verify the System Attendant is running and properly configured to point to a valid homeMDB

Try to restart the Microsoft System Attendant service on the Exchange server mentioned in the failed task properties.

How to check the homeMDB attribute value:
  • Start ADSI Edit and navigate to CN=Configuration,DC=,DC=,DC=/Services/Microsoft Exchange//Administrative Groups/Exchange Administrative Group (FYDIBOHF23SPDLT)//Servers/MBXServerWithIssue
  • Right-click Microsoft System Attendant, and then click Properties to display the Attributes list and find the homeMDB attribute.
  • If the homeMDB attribute has a value make sure  it points to a valid mailbox database. If the value of the homeMDB attribute is empty (not set) or incorrect fix it.

Additional Information

Refer to the following Microsoft articles for more details:

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF