In Exchange 2010 on SBS 2011 Standard getting Initialization failed when starting EMC
I am getting the following error when starting the Exchange 2010 EMC on a SBS 2011 Standard:
The following error occurred while attempting to connect to the specified Exchange server 'domain name'
The attempt to connect to http://domain.local/PowerShell using 'Kerberos' authentication failed: Connecting to remote server failed with the following error message: The WInRM client cannot process the request.
The authentyication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication mechanisms
supoorted by the server. To use Kerberos, specify the computer name as the remote destination. Alsoverfy that the client computer and the destination computer are joined to a domain. To user Basic, specify the computer name as the remote destination, specify
Basic authentication and provide user name and password. Possible authentication mechanisms reported by server:
March 27th, 2012 4:43pm
To add to the above comment, I have checked many configuration and the look all good.
Big help is needed. Thank you
Free Windows Admin Tool Kit Click here and download it now
March 27th, 2012 4:52pm
Hi
Please confirm that whether you have other applications using the same port (80) with Default website .
For instance whether you have sharepoint deployed.(SBS will install it)
If indeed, try to change the application to use other port and test again.
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
tngfb@microsoft.com
Terence Yu
TechNet Community Support
March 27th, 2012 10:42pm
Hi
Do you have anything update ?Terence Yu
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2012 4:44am
Hi,
Yes it was that I had another application was using port 80. How it got there its a mistery.
All i had to do is the stop the application in the IIS and reset the IIS.
Now working fine.
March 29th, 2012 6:37am