Link to home
Start Free TrialLog in
Avatar of abhijitmdp
abhijitmdpFlag for India

asked on

EMC WINRM error Exchange 2010

We are using windows server 2008 R2 standard for exchange 2010 and Windows server 2003 with an existing exchange 2003 environment we have started the migration process recently. Just installed exchange 2010. The AD is installed on windows Server 2003. Configured the send and receive connector for internal and external messaging. Also installed a certificate from GoDaddy and configured redirection from http to https in IIS. Changed internal and external OWA addresses. Restarted the services and after that we are facing following issues (FIG1) after this the exchange management console is not opening but we are able to access the webmail of exchange 2010. We were using IPv4 not v6. Help......... User generated image User generated image User generated imageI have also checked the WINRM service, re-registered it and also checked the Karborus permissions at powershell. Everything is fine. Plz help
Avatar of abhijitmdp
abhijitmdp
Flag of India image

ASKER

I have also checked the WINRM service, re-registered it and also checked the Karborus permissions at powershell. Everything is fine. Plz help
Have you double checked the WSMAN entry in your applicationhostconfig?
http://msexchangeteam.com/archive/2010/02/04/453946.aspx
Do you have WINRM 2.0?
Did you run winrm /qc? (not to sound redundant, I see you mentioned it above but did you run this command?)
Check IIS under default websites->modules->wsman and kerbauth.dll listed as native

The above link has most of the error messages associated to WINRM failure.
Is there any event logged?
Hello Abhijit,

I can help you... but i will need to live meeting.
let me know.  I am avaialble only for 30 mins.

Regards,
:)
SOLUTION
Avatar of R--R
R--R
Flag of India image

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
Dear dexIT and R--R,

Please stop googeling, I have already gone through all above articles, I wanted to hear from you.
SOLUTION
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
Abhijit ,

Do you really need help ?

Reagrds,
:)
If yes then please , this type of issues will not get resolve by following Articles, we need to have look
on the server.

let me know
Dear jawad1481,

I am not able to provide any remote session to our servers. Can you provide any help without the remote session that will be appreciated.
Hi Dex,

I have already already went through the links but it did not help me .
Hello Abhijit,

Its very difficult then....:)

Regards,
:)
Abhijit.,

You still thinking ?

Bye take care...

Reagrds,
:)
Have you verified the settings in IIS for all the Exchange VDIRs?
Yes all are the same as microsoft recommends.
Hello,

Do you need assistance ?

One thing......what happens when you browse powershel VD on port 80 and 443 ?

Regards,

jawad
ASKER CERTIFIED SOLUTION
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
None of the solutions was accurate and resolved my issue. I have researched byself on this and found a solution.
My solution to this problem was the following......


Edit the following file.

C:\Windows\System32\Inetsrv\config\ApplicationHost.config


Scroll down to the <globalModules> tag,

add the following  <add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" />

restart iis.