Exchange 2010 SP1 - EMC/EMS wont open
Hi Experts,
I am near my wits end, and come in search of an answer.
I have 2008 R2 Standard Server with Exchange 2010 SP1 and all the current windows updates, and exchange rollup update1. It is running on 1 server which is a domain controller and global catalogue, etc. It was a clean install, no migration.
When i go to open the EMC, i get the following error,
The attempt to connect to http://servername.domainname.school.nz/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more infomation, see the about_Rmote_Troubleshootin
Now i have trawled the internet and these forums and have done all the basic stuff, like the checking the that kerbauth.dll is pointing to the right path, etc. (not sure on spelling its from memory)
Also just to add to the mix, when i go to the powershell virtual directory, and click on any of the icons, for example authentication, i get a dialog box that says,
[b]There was an error while performing this operation. Details: Filename: \\?\C:\Program Files\Microsoft\Exchange Server\V14\Client Acess\Powershell\web.confi
And another question, which may aid in answering whats happening here, i also have an issue with OWA. In internet explorer, if i go to,
https://server.domainname.school.nz/owa, the outlook web app comes up. You put in some user credentials, then it goes to https://server.domain.school.nz/owa/auth.owa with a HTTP 400 bad request, webpage cannot be found.
I have a backup image of the server restored to a temp/test pc so i can play with it without interupting the business.
i really appreciate your time, this is my first posting in this forum, so I do hope its in the right place.
Thank you experts, i look forward to finding an answer. i dont really want to rebuild this network :)
Regards,
Adrian
I am near my wits end, and come in search of an answer.
I have 2008 R2 Standard Server with Exchange 2010 SP1 and all the current windows updates, and exchange rollup update1. It is running on 1 server which is a domain controller and global catalogue, etc. It was a clean install, no migration.
When i go to open the EMC, i get the following error,
The attempt to connect to http://servername.domainname.school.nz/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more infomation, see the about_Rmote_Troubleshootin
Now i have trawled the internet and these forums and have done all the basic stuff, like the checking the that kerbauth.dll is pointing to the right path, etc. (not sure on spelling its from memory)
Also just to add to the mix, when i go to the powershell virtual directory, and click on any of the icons, for example authentication, i get a dialog box that says,
[b]There was an error while performing this operation. Details: Filename: \\?\C:\Program Files\Microsoft\Exchange Server\V14\Client Acess\Powershell\web.confi
And another question, which may aid in answering whats happening here, i also have an issue with OWA. In internet explorer, if i go to,
https://server.domainname.school.nz/owa, the outlook web app comes up. You put in some user credentials, then it goes to https://server.domain.school.nz/owa/auth.owa with a HTTP 400 bad request, webpage cannot be found.
I have a backup image of the server restored to a temp/test pc so i can play with it without interupting the business.
i really appreciate your time, this is my first posting in this forum, so I do hope its in the right place.
Thank you experts, i look forward to finding an answer. i dont really want to rebuild this network :)
Regards,
Adrian
ASKER
Thanks Tony1044, i have tried that, and still no luck.
I had this issue with the EMC and EMS not opening last week...a simple reboot took care of it. Make sure your server's DNS is working properly and it can see the global catalog.
With your OWA you need to go set the internal and external URLs for your server so it doesn't redirect to an unreachable dns name.
With your OWA you need to go set the internal and external URLs for your server so it doesn't redirect to an unreachable dns name.
Yup - I was going to say reboot after the changes.
ASKER
Thanks renazonse, and Tony1044. i have restarted the server after the change above. it has made no difference. Im guessing i have to configure the OWA via the EMC or EMS?, which i cant get into.
The server DNS is working fine, there are no issues with it according to the best practices analysers when i scan the role. I dont have forwarders they are in the root hints, which are the 2 from the ISP.
The main thing for me is to be able to get into EMC or EMS, OWA is second at this stage.
anymore help would be extremely appreciated.
The server DNS is working fine, there are no issues with it according to the best practices analysers when i scan the role. I dont have forwarders they are in the root hints, which are the 2 from the ISP.
The main thing for me is to be able to get into EMC or EMS, OWA is second at this stage.
anymore help would be extremely appreciated.
Realise you've searched on here, but did you come across this?
https://www.experts-exchange.com/questions/24888607/Exchange-2010-RTM-EMC-error.html
https://www.experts-exchange.com/questions/24888607/Exchange-2010-RTM-EMC-error.html
And finally, this:
"You can often resolve this problem by removing the feature WinRM IIS Extension from Windows Server 2008 R2 and then readding it."
(Taken from http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/78e5cee2-a310-4187-80ff-b310645ccb5b/ )
"You can often resolve this problem by removing the feature WinRM IIS Extension from Windows Server 2008 R2 and then readding it."
(Taken from http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/78e5cee2-a310-4187-80ff-b310645ccb5b/ )
ASKER
hi, i have been through those articles as well while trawling through the web. unfortunately none of those have worked for me either. :(
As mentioned above regarding the DNS and forwarders, i have changed them from being root hints to being forwarders. Restarted the DNS Service, but still no difference.
The powershell directory on the server has 2 files, web.config, and web (2).config.
I have also removed and re-installed the WinRM role and still no avail.
thanks Tony
As mentioned above regarding the DNS and forwarders, i have changed them from being root hints to being forwarders. Restarted the DNS Service, but still no difference.
The powershell directory on the server has 2 files, web.config, and web (2).config.
I have also removed and re-installed the WinRM role and still no avail.
thanks Tony
ASKER
hold the phone....for the heck of it, i just removed and re-installed the WinRM IIS Extension feature, restarted, and now the powershell is behaving in IIS, i.e, i can open up the authentication with no error.
But still have an error with the EMC. It reads as follows:
[b]The attempt to connect to http://servername.domainname.school.nz/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: The WS-Management service does not support the request. For more infomation, see the about_Rmote_Troubleshootin
So the authentication in powershell is everything is disabled except Windows Authentication.
regards,
Adrian
But still have an error with the EMC. It reads as follows:
[b]The attempt to connect to http://servername.domainname.school.nz/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: The WS-Management service does not support the request. For more infomation, see the about_Rmote_Troubleshootin
So the authentication in powershell is everything is disabled except Windows Authentication.
regards,
Adrian
ASKER
Hi.
thanks Tony for helping me, you have pointed me in the right direction regarding the powershell. After playing around some more on my test machine, i removed and re-added the kerbauth.dll, into the powershell directory, and also removed and re-added WSMan to the powershell modules. Now i am able to open the EMC. I also re-ran the winrm quickconfig option from the powershell.
Now to fix the OWA.
if anyone can help or shed some light on that, i would be most appreciative.
thanks Tony for helping me, you have pointed me in the right direction regarding the powershell. After playing around some more on my test machine, i removed and re-added the kerbauth.dll, into the powershell directory, and also removed and re-added WSMan to the powershell modules. Now i am able to open the EMC. I also re-ran the winrm quickconfig option from the powershell.
Now to fix the OWA.
if anyone can help or shed some light on that, i would be most appreciative.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Tony,
It installed fine, with no failures, which is what makes it such a pain in the butt.
i'll try those commands and get back. its been the weekend here in NZ, hence the late reply.
Adrian
It installed fine, with no failures, which is what makes it such a pain in the butt.
i'll try those commands and get back. its been the weekend here in NZ, hence the late reply.
Adrian
ASKER
Tony,
i wish i could shake your hand sir, thank you very much for your help. we are all up and running. EMC, EMS and OWA. Thanks so much.
Adrian
i wish i could shake your hand sir, thank you very much for your help. we are all up and running. EMC, EMS and OWA. Thanks so much.
Adrian
http://technet.microsoft.com/en-us/library/dd298084.aspx