Article ID: 9460, created on Dec 19, 2010, last review on Sep 28, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5
  • Operations Automation 5.4
  • Operations Automation 5.0
  • Business Automation 6.0

Symptoms

An Exchange Public Folder provisioning task fails in Operations Automation (OA) with the following error message:

There is no existing PublicFolder that matches the following Identity

See an example of the problem below:

Task name Set limits for public folder 'New Folder' (id=15)
Last execution output:
Exception during execution of MPF request: 'Unknown error 0x80131500
[<response><errorContext description="There is no existing PublicFolder that matches the following Identity: '\P000000093\New Folder'. Please make sure that you specified the correct PublicFolder Identity and that you have the necessary permissions to view PublicFolder." code="0x80131500"
executeSeqNo="3"><errorSource namespace="Exchange2007ProviderEx"
procedure="ModifyFolder"/><errorSource namespace="SW Managed Exchange"
procedure="ModifyFolder"/></errorContext></response>]'.

Cause

Cause #1. The Public Folder was renamed or deleted directly in Exchange, e.g. using the Exchange Management Shell or Console.

Log into the Exchange server, run the Exchange Management Shell and check if the Public Folder from the failed task properties exists:

Get-PublicFolder -Identity "\P000000093\New Folder"

If you cannot find Public Folder '\P000000093\New Folder' this means that the Public Folder was renamed in Exchange or absent and must be created in Exchange and the OA database must be adjusted.

Cause #2. Exchange server where the Public Folder Store is located is malfunctioning. Find the ID of the problem Public Folder and get the name of the Exchange server where OA tries to create it from OA database. You can use an SQL query like this:

plesk=> SELECT primary_name, store_name FROM exch_public_folders pf JOIN exch_public_stores ps ON pf.store_id=ps.public_store_id JOIN hosts h USING(host_id) WHERE folder_id=72;
-[ RECORD 1 ]+---------------------
primary_name | EXVS01.hosting.local
store_name   | EXVS01PF01
ds_id        | 554

Try to connect to the Exchange server using the Public Folder DAV-based Administration Tool (Exchange 2003, Exchange 2007). If the tool cannot connect to the server, this means there are problems with the Exchange server itself.

Resolution

Problem #1. Imagine a Public Folder with the name 'New Folder' was renamed in Exchange to 'Old Folder'. Use the Exchange Management Shell cmd-let 'Set-PublicFolder' to rename the Public Folder in Exchange back to 'New Folder':

Set-PublicFolder -Identity "\P000000093\Old Folder" -Name "\P000000093\New Folder"

If you decide to rename the Public Folder in OA database, then the table 'exch_public_folders' has to be adjusted. The relevant fields are:

  • name
  • display_name
  • description
  • ldap_path
  • path
  • full_path
  • tree_ordering

Problem #2. In this instance, the issue is on Microsoft's side. We suggest contacting Microsoft Support to resolve the problem.

On OA side, the problem can only be worked around by changing the Exchange server where OA will create the Public Folder. This works if the brand new root Public Folder has to be created, not a sub-folder in an already existing Public Folder.

  1. Use the Public Folder DAV-based Administration Tool to find a functioning Exchange server with Public Folder store from the list in the OA Provider Control Panel at Top > Service Director > Hosted Exchange Manager > Public Folder Stores.

  2. With the ID of the working Public Folder store, reassign the Public Folder to the working store in the POA database:

    BEGIN;
    UPDATE exch_public_folders SET store_id = $STORE_ID WHERE ds_id = $DS_ID;
    UPDATE exch_domain_services SET pf_store_service_id = $SERVICE_ID WHERE ds_id = $DS_ID;
    

where

$STORE_ID - ID of the working public folder store from OA Control Panel (found on the previous step using the DAV-based Admin Tool)

$DS_ID - Domain service ID (returned by the SQL query above)

$SERVICE_ID - ID of the OA service Exchange Mailstore installed on the found server. This can be found in two places on the OA Provider Control Panel:

  • Deployment Director > Server Manager > Hardware Nodes > select Exchange server with working public folder store > Applications tab

or

  • System Director > Configuration Manager > Services > filter services by Exchange server name and application name Mailstore

Search Words

addPublicFolderHandler on OBJREF:Exchange:0:getPublicFolderManager:29858

public folder link broken

Task 'Collect public folders diskspace usage for service #17' (id=4490265) execution failed. Destination host 'EXVS01.hosting.local' (#13), IP '67.196.32.29' : Provisioning request failed. Unknown error 0x80131500 [<response><errorContext description="Could not find any available Domain Controller." code="0x80131500" executeSeqNo="2"><errorSource namespace="Exchange2007ProviderEx" procedure="GetPublicFolderActualSize"/><errorSource namespace="SW Managed Exchange" procedure="GetPublicFolderActualSize"/></errorContext></response>]

failed task

failed tasks

public folder link broken from parralels to backend

Exception during execution of MPF request: 'Unknown error 0x80131501 [<response><errorContext description="No existing 'PublicFolder' matches the following Identity: '\P0000001827\???????'. Make sure that you specified the correct 'PublicFolder' Identity and that you have the necessary permissions to view 'PublicFolder'." code="0x80131501" executeSeqNo="2"><errorSource namespace="Exchange2010ProviderEx" procedure="ModifyFolder"/><errorSource namespace="SW Managed Exchange" procedure="ModifyFolder"/></errorContext></response>]'.

Other

Provisioning request failed. Unknown error 0x80131500

Не удаляется общая папка

failed PF task

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e 5b048d9bddf8048a00aba7e0bdadef37 c27596ac4fff6cb4c8ec8891dae57001 e12cea1d47a3125d335d68e6d4e15e07 198398b282069eaf2d94a6af87dcb3ff 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF