Just recently upgraded Exchange 2013 to CU22, now I am unable to create new mailboxes but I can update / change settings on already created mailboxes within SolidCP.
When creating new mailboxes, the following error is produced – The WinRM client received an HTTP bad request status (400). No settings have been changed on the SolidCP server after the upgrade.
This issue was fixed with paid SolidCP support, which I would recommend. The issue turned out to be a missing https bind for ip 127.0.0.1 on the default web directory.
Have you rechecked the Powershell virtual directory for windows users?
Most easy is to check it in ECP,
It needs “Integrated Auth” checked (and nothing else) on the auth tab.
After thats correctly set you could do an iisreset as sometimes it caches the connection/ auth method.
Even with the authentication set to Windows Intergrated, the error still happens. Can you confirm if you have a WinRM HTTPS listener?
System.Exception: Error executing ‘CREATE_MAILBOX’ task on ‘User Name’ EXCHANGE —> System.Web.Services.Protocols.SoapException: Server was unable to process request. —> Connecting to remote server mailbox.cloudmotion.ca failed with the following error message : The WinRM client received an HTTP bad request status (400), but the remote service did not include any other information about the cause of the failure
It should communicate over https yes (and no additional changes for Exchange is needed for that other then the auth method).
Can you verify your using the local powershell url for solidcp? (https://myserver1.mydomain.local/Powershell )
- Views2232 times
- Answers7 answers