POA background task Initialize mailbox with E-Mail Address '
<;mailbox_id>) fails with the one of error messages below:
A connection with the server could not be established
Init mailbox: Unable to login in OWA. Status code: 200
The detailed diagnostics is provided below:
Destination host '<hostname>' (#<host_id>), IP '<IP address>' : Provisioning request failed. Unknown error 0x80072EFD [<response><errorContext description="(37,16) msxml6.dll: A connection with the server could not be established" code="0x80072efd" executeSeqNo="2"><errorSource namespace="Scripting Provider" procedure="ExecuteScript"/><errorSource namespace="SW Managed Exchange" procedure="InitMailbox"/></errorContext></response>] OutputDestination host_id #131 : Provisioning request failed. Unknown error 0x8A010001 [<response><errorContext description="(38,20) Init Mailbox: Unable to login in OWA. Status Code: 200" code="0x8a010001" executeSeqNo="2"><errorSource namespace="Scripting Provider" procedure="ExecuteScript"/><errorSource namespace="SW Managed Exchange" procedure="InitMailbox"/></errorContext></response>]
The task executes a script on Exchange mailbox server that tries to log in to OWA (Outlook Web Access) using its internal URL. It cannot reach OWA using the URL due to whatever reason.
The first step is to figure out the actual URL used to connect to OWA.
This is typically 'https://
<CAS hostname>.provider.com/owa', where 'CAS hostname' is the hostname for one of the CAS servers in the Exchange installation, and 'provider.com' is AD domain.
To verify the exact URL you can use either MPS of WPE request tracer (depending on the provisioning system you use - for Exchange 2010 and above in POA 5.4 and above only WPE is used) to catch content of the request that POA sends to the provisioning engine and which fails, details can be found in the following KB articles:
- How to catch requests from POA to Microsoft Provisioning System
In the caught XML request, there will be a script to execute and the
<owaURL>field containing the URL that is used to login to OWA and initialize the mailbox.
Verify that the URL in the provisioning request is accessible from the server whose hostname was listed in the failed task's error message.
Typical problems can include DNS resolution - Exchange server where task is being executed cannot resolve hostname of the owaURL to IP address (in which case you can either add appropriate records to AD DNS servers or to hosts file on the server), or IP address the owaURL resolves to not being added to IIS on the appropriate CAS server, in which case you can add it and configure IIS to listen to port 443 on this IP.