tamray_tech
asked on
Cannot launch Exchange Console / IIS 500 Internal Errors
Have no idea why, but came in today to find Exchange 2010 not working. Upon investigation, found that all Exchange services were disabled, along with IIS.
I re-enabled all services and now Exchange is processing messages, but I cannot manage the console. It has something to do with IIS and Kerberos. I followed this doc:
http://technet.microsoft.com/en-us/library/ff607221(v=EXCHG.80).aspx, but still am having problems.
I did have to change the account used for testing the powershell path to Administrator in Default web Site, Powershell, Actions, Basic Settings
See attached screen shots
Screenshot-1.png
Screenshot-2.png
I re-enabled all services and now Exchange is processing messages, but I cannot manage the console. It has something to do with IIS and Kerberos. I followed this doc:
http://technet.microsoft.com/en-us/library/ff607221(v=EXCHG.80).aspx, but still am having problems.
I did have to change the account used for testing the powershell path to Administrator in Default web Site, Powershell, Actions, Basic Settings
See attached screen shots
Screenshot-1.png
Screenshot-2.png
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The rollups are service pack specific. If you Google your version it will tell you.
Exchange 2010 SP1 I think is on Rollup 7 or 8, Exchange 2010 SP2 is on rollup 4.
Although if you are on Exchange 2010 SP1, I would suggest you install Exchange 2010 SP2 to start with. That will correct a lot of issues.
Simon.
Exchange 2010 SP1 I think is on Rollup 7 or 8, Exchange 2010 SP2 is on rollup 4.
Although if you are on Exchange 2010 SP1, I would suggest you install Exchange 2010 SP2 to start with. That will correct a lot of issues.
Simon.
It seems Microsoft guys sneaked into your box and messed it up so to make life for you pretty bad.
Jokes apart, WinRM is pretty tricky to troubleshoot, cause it never gives you the reason WHY it is failing to provide connection to your server. Read the following links, that I normally follow on such issues
http://support.microsoft.com/kb/2027063
http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx
Read through event viewer logs very carefully to understand WHAT GOT MESSED up over night. If you can, install a newer rollup - just so that it would bring in increased version of binaries and thereby correcting what may have gone wrong.
Regards,
Exchange_Geek
Jokes apart, WinRM is pretty tricky to troubleshoot, cause it never gives you the reason WHY it is failing to provide connection to your server. Read the following links, that I normally follow on such issues
http://support.microsoft.com/kb/2027063
http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx
Read through event viewer logs very carefully to understand WHAT GOT MESSED up over night. If you can, install a newer rollup - just so that it would bring in increased version of binaries and thereby correcting what may have gone wrong.
Regards,
Exchange_Geek
ASKER
I had made progress by re installing Sp2. Things were up and running, until a reboot. For a very extended period of time the server stayed on update 9 of 10 and seemed to be hung for 15-20 minutes. being a VM, I finally forced it to shutdown. When it was restarted all Exchange services were disabled, as it was the last time. I found rollup 4 was waiting to be installed, but instead, chose to attempt to reinstall Sp2, but there was not an Upgrade option, only Install of new features. I finally did install the rollup, which took a very long time. No errors cropped up and I rebooted as instructed, but the Exchange services are still disabled.
Any ideas how to get past this?
Any ideas how to get past this?
ASKER
Manually turning the services back on and a reboot, did what I expected would have been accomplished with an install of rollout 4 and a reboot.
Seems good to go now.
Seems good to go now.
ASKER