Article ID: 114948, created on Oct 12, 2012, last review on May 1, 2014

  • Applies to:
  • Operations Automation

Symptoms


After Exchange 2010 SP2 Update Rollup 3 installation POA task 'Initialize mailbox' to init Exchange mailbox fails with the error message 'Operation is not valid due to the current state of the object' like in the example below:

Task ID 8779327
Task name       Initialize mailbox with E-Mail Address 'jdoe@customer.com' (id=9180)
Task description        Initialize mailbox with E-Mail Address 'jdoe@customer.com' (id=9180)
Subscription ID 1000264
Queue name      DomainService00000920
Method name     initMailBoxByCURLHandler
Execution status        Failed
Start not earlier than  Oct-02-2012 11:59
Finished        Oct-02-2012 11:59
Output  Provisioning request failed. Error in 'SW Managed Exchange.InitMailbox'.
Operation is not valid due to the current state of the object.

Error position:
At C:\Program Files\Parallels\Windows Provisioning Engine\Providers\SW Managed Exchange\InitMailbox.ps1:130 char:35
+ Set-MailboxJunkEmailConfiguration <<<< -Identity $userDN -DomainController $ExecData.preferredDomainController -Enabled $true

Type: Parallels.Wpe.PowerShell.PowerShellException.


Cause


The Exchange cmdlet Set-MailboxJunkEmailConfiguration cannot be executed after Exchange update.

Resolution


The problem is going to be fixed in the future updates to POA.

In the meantime the following solution may be applied:
1. Log into POA Windows Provisioning Engine server by RDP
2. Open the file C:\Program Files\Parallels\Windows Provisioning Engine\Providers\SW Managed Exchange\InitMailbox.ps
3. Comment the string where the Exchange cmdlet Set-MailboxJunkEmailConfiguration is called
4. Run the failed task in POA
5. Roll the changes made to the InitMailbox.ps file back - unomment the string where the Exchange cmdlet Set-MailboxJunkEmailConfiguration is called
6. Execute the cmdlet Set-MailboxJunkEmailConfiguration manually on any Exchange server using the Exchange Management Shell using the command like this:
[PS] C:\Windows\system32>Set-MailboxJunkEmailConfiguration -Identity AD_USER_IDENTITY -DomainController PREFERRED_AD_DC -Enabled $true
Replace AD_USER_IDENTITY with actual identity of the Active Directory user, replace PREFERRED_AD_DC witl actual IP of the AD Domain Controller.


Notes:

1. AD user identity may be found using the Active Directory Users and Computers snap-in:
  • Run dsa.msc on any AD Domain Controller
  • Find the needed Organizational Unit
  • Right-click on the problem user
  • Select Properties
  • In the opened window switch to the Account tab
  • User identity is shown in the 'User logon name' field.

2. The preferred AD Domain Controller may be found in POA Provider Control Panel:
  • Log into POA PCP
  • Go to Deployment Director > Server Manager > Hardware Nodes
  • Click on any Domain Controller in the needed Windows domain
  • Switch to the Applications tab
  • Click on the ADDOmainController application
  • Switch to the Preferred Domain Controller tab
  • The preferred AD domain controller may be found on the screen

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF