500 Winrm Error
“Connecting to remote server XXX.YYY.local failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic.” This happens when I try and do a bulk-mailbox add or the migration “fix” from the admin settings as well.
I’ve double-checked the suggestions in the KB, I can connect with test-wsman and enter-pssession without errors, so I don’t really know where to go from here.
I’m running the latest build of CP and Exchange 2013WCU8. Any suggestions on debugging?
Thanks!
Everytime this happens its either:
* CloudPanel Application isn’t assigned to an Application Pool running under a domain admin IDENTITY
* You didn’t enable “Basic Authentication” and choose “Basic authenticaiton” in the settings page and in Exchange /powershell virtual directory. Don’t enable it in IIS.. you enable it through EAC.
Hi Jacob,
Sorry to (re)open an old topic. Some time ago I’ve upgraded my CP installation to the latest version, and from that time I didn’t create new companies or mailboxes for my customers. Today I tried to create a new customer, all OK, but when I tried to Enable Exchange for this new customer 500 error [attachment file=”500 error.PNG”].
I’ve checked the settings and all seems to be OK.
[attachment file=”CP_settings.PNG”]
Also the CP application pool runs under a domain admin Identity. A few pointers?
Fixed. I’ve run in EMC “get-PowerShellVirtualDirectory -server <Exchange Server> |fl *auth*” and found that BasicAuthentication was not enabled ….
You could do that or in ECP/EAC you can go to servers -> virtual directories -> and choose the powershell virtual directory to enable basic authentication. Never do it in IIS though.
- 5 Forums
- 716 Topics
- 3,649 Posts
- 0 Online
- 258 Members