Search Engine: Elastic

Article ID: 116504, created on Jul 19, 2013, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation


Exchange service provisioning task fails with the following error message:

Exception of type 'System.OutOfMemoryException' was thrown.

More detailed diagnostics is provided in the example below:

Destination host ' (#82), IP '' : Provisioning request failed. Unknown error 0x80131600
[<response><errorContext description="Exception of type 'System.OutOfMemoryException' was thrown.
Cmdlet='Get-Mailbox' DomainController=''
code="0x80131600" executeSeqNo="2"><errorSource namespace="Exchange 2007 Provider"
procedure="ModifyMailbox"/><errorSource namespace="SW Managed Exchange" procedure="ModifyMailbox"/>


A certain Exchange service or provisioning engine consumes too much memory, this causes failure. The problem most probably has nothing to do with POA.


Try the following actions in order to resolve the issue.

  1. First of all, try to restart the failed task in POA, the problem may be already resolved and the task will go through.

  2. Restart Exchange services on the affected host. The IP address and/or hostname of the server may be found in the error message in the failed task in the POA Task Manager.

  3. Depending on the provisioning engine used in POA try to restart it:

    • Microsoft Provisioning System (MPS) - follow the istructions in the Parallels Knowledgebase article #1851

    • Windows Provisioning Engine (WPE) - restart IIS on the WPE host using the iisreset command

  4. As the last resort - recycle the affected Exchange server and provisioning engine host (MPS or WPE).

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF