• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 504
  • Last Modified:

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
0
tamray_tech
Asked:
tamray_tech
  • 3
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
That sounds like a rollup installation was started and failed. The rollup disables all services.
You need to correct the services start up, as not everything is Automatic, some are manual. I would also suggest that you verify that a rollup installation wasn't attempted, if it was, it probably didn't completely correctly.

For the Keberos errors, start here:
http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx

However you may find that reinstalling the latest rollup for Exchange 2010 resolves the issue.

Simon.
0
 
tamray_techAuthor Commented:
Hmmm.... I was not informed any such installation had been attempted. Do you know of a link that I could download and install?
0
 
Simon Butler (Sembee)ConsultantCommented:
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.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Exchange_GeekCommented:
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
0
 
tamray_techAuthor Commented:
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?
0
 
tamray_techAuthor Commented:
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.
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now