Link to home
Start Free TrialLog in
Avatar of james_ecker
james_ecker

asked on

Exchange 2010 Management Console: Initialization failed

Connecting to the remote server 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.

I have followed this link: http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/5f6950b0-7215-479d-9e5e-fb93c76699ce/ and I have restarted the server several times, but no change.

What I did notice is if I enter a get, new, or anyother command I get the error:
The term 'get' is not recognized as the name of a cmdlet, function, script file, or operable program

The server has 4Gb Ram, 4 Processors, 150Gb free hard disk space, and is running Windows Server 2008 R2 Standard Edition. The server is also up to date with all of its updates.

 Anyone have any ideas?
Avatar of Illusionist
Illusionist

When you get the Initialization failed it seems there are some issues in the IIS /WinRM.

1) Run the command WinRM QuickConfig
this will let you know if WinRM is listening on this server or not.

2) Check if port 80/443 are open in the firewall and not blocked. For the timebeing you can turn off the firewall on the server.

3) Did you make any changes to the authenticaltion on the IIS default website, like unchecking the SSL?
if yes enable the SSL on the default website.

4) In the IIS Manager -> Defautl Web site -> Powershell Virtual DIrectory -> Modules -> Kerbauth.dll & Wsman.dll should be present.

5) Uninstall Winrm IIS Extension and reinstall it.

6) Do you get any event ID in the Application / System Log for Windows remote management
If yes then need to fix these events.
Avatar of james_ecker

ASKER

Ok, I  made some change last night and wanted to wait until this morning to double check I fixed the couple of errors.

1) Yes the WinRM is listening

2) The ports 80 and 443 are open for the Domain and not for Home/Work and Public

3) No, I didn't make any changes to the IIS default website

4) I have double checked the Kerbauth.dll, but I cannot find Wsman.dll. There is a WSman entry but it does not point to wsman.dll, if wsman.dll is correct where is this file located?

5) I just tried uninstalling WnRM IIS Extension and reinstalling it, but no change.

6) No, mno Windows remote management errors.

Is there a method to recompile/reregister the Exchange cmdlets?
ASKER CERTIFIED SOLUTION
Avatar of james_ecker
james_ecker

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial