• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 117197, created on Sep 10, 2013, last review on May 31, 2014

  • Applies to:
  • Operations Automation 5.4

Symptoms

Task for Microsoft Exchange fails with the following error:

Provisioning request failed. Error in 'SW Managed Exchange.UpdateSMTPDomains'.
Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.

Error position:
At C:\Program Files\Parallels\Windows Provisioning Engine\Providers\SW Managed Exchange\Utils\ExchangeUtils.ps1:97 char:17
+ $p._session = <<<< New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri $connectionUri -Credential $credential -Authentication Kerberos -SessionOption $PSSessionOptionOverride

Type: Parallels.Wpe.PowerShell.PowerShellException.

Cause

WPE server processes the request, and transfers it to the appropriate Exchange server. This request is being executed within Exchange Management shell, however, the shell is unable to connect to that server. When you start EMS on WPE server, you get the same error message:

The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.

Resolution

Make sure that it is possible to open a remote powershell session to the Exchange server from WPE server, use

PS> Test-WsMan 

commandlet.

Refer to Microsoft knowledge base for troubleshooting details.

Search Words

Exchange

provisioning failed

tasks failed

domains

The WinRM client cannot complete the operation within the time specified

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e ac82ce33439a9c1feec4ff4f2f638899 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF