Search Engine: Elastic

Article ID: 114553, created on Aug 13, 2012, last review on Aug 24, 2015

  • Applies to:
  • Operations Automation 5.4


OA tasks related to Exchange Public Folder fail with the error message:

Property 'AcceptMessagesOnlyFromSendersOrMembers' object is null', the example is provided below:
Task ID           12345678
Queue name        DomainService00003051
Task name         Show in address book public folder 'info' (id=5357)
Task description  Show in address book public folder 'info' (id=5357)
Subscription ID   9876543
Queue status      Failed
Start not earlier than    Jun-20-2012 11:35
Method name       toggleHiddenFromAddressBookHandler on OBJREF:Exchange:0:getPublicFolder:5357
Last execution output    Provisioning request failed. Error in 'SW Managed Exchange.ModifyMailEnabledFolder'.
Exception calling "Execute" with "3" argument(s):
"Property 'AcceptMessagesOnlyFromSendersOrMembers' object is null
Parameter name: obj"
Error position:
At C:\Program Files\Parallels\Windows Provisioning Engine\Providers\Common\ProviderUtils\ProviderUtils.psm1:53 char:26
+ [void]$Context.Execute <<<< ($Provider, $Method, $exec_data)

Type: Parallels.Wpe.PowerShell.PowerShellException.


The Public Folder in question either does not exist or is not mail-enabled. Corresponding Exchange System Object in Active Directory searched by LDAP path is missing.


  1. Using WPE Tracer Tool you may find what Exchange System Object OA is trying to find in Active Directory. Make sure that object exists.

  2. Check if Public Folder exists using Exchange cmdlets Get-PublicFolder, Get-MailPublicFolder.

If the Public Folder does not exist in Exchange and it is brand new Public Folder (without any data) consider to remove it in OA Customer CP and create it from scratch.

If the Public Folder exists and it is not mail-enabled, then consider to mail enable it using Exchange cmdlet Enable-MailPublicFolder.

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07 ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF