SBS 2003 - After Restart Can't Browse OWA

Client of mine called this morning saying they had to restart the server, I connected after to see it give me the error about improper shutdown, not sure if they held the power button or not.  

Now I try to browse the https://domain/exchange and getting a HTTP 500 error, was getting a HTTP 1.1/ 503 Service is no longer available.

Read some articles, and reset the HKEY Classes Root Permission.  Still having same issue.

Any ideas?  
Fluid_ImageryAsked:
Who is Participating?
 
Fluid_ImageryConnect With a Mentor Author Commented:
We've replaced the entire server after the exchange crash since the server needed to be replaced anyway.  A full exchange rebuild is what was finally needed.
0
 
collins23Commented:
have you tried this

http://forums.techarena.in/small-business-server/79473.htm

the last post at the end ?
0
 
collins23Commented:
also found this somewhere

Well, we finally found the solution. On a Google message board someone wrote that you need to:

The solution is to copy  \Program Files\Exchsrvr\exchweb\6.5.7226.0 from the
back-end to the front-end server. It worked perfectly after we did this.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows PowershellĀ® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Fluid_ImageryAuthor Commented:
we have a single server, sbs 2003.
0
 
Fluid_ImageryAuthor Commented:
Under IIS and under the Exchange site, i changed Application Settings to Exchange, and Application Pool to ExchangeApplicationPool, I am now getting the login page, but now it goes to HTTP/1.1 503 Service Unavaliable.  
0
 
Rob WilliamsCommented:
Can you try a second reboot?  RWW often needs a second reboot, especially after some updates.
Also verify in IIS that that all sites are running, and in the services management console all "automatic" services are running, especially WWW publishing.
0
 
Fluid_ImageryAuthor Commented:
Just looked in Exchange System Manager, stores aren't mounted.  ID is c1041724
0
 
Fluid_ImageryAuthor Commented:
its a problem dealing with teh database not being able to mount, any ideas onthat/
0
 
Rob WilliamsCommented:
Careful making changes, it is unlikely a reboot made configurations changes automatically. Can you mount the store or a reboot will likely do that for you. If they hit the power button it can affect Exchange, or any database. Databases do not like sudden shutdowns but a followup proper shut down will usually resolve, though it may take longer than usual the first time.

It is also possible a suddenshutdown has corrupted the database.
0
 
Fluid_ImageryAuthor Commented:
I have restarted multiple times, trying to mount is giving errors.  

Error 0xffffff01 starting Storage Group /DC=com/DC=ABC/DC=local/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=ABC/CN=Administrative Groups/CN=first administrative group/CN=Servers/CN=W2K3SERVER/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.
Storage Group - Initialization of Jet failed.
0
 
Rob WilliamsCommented:
The Exchange troubleshooting assistant 'can' help to determine issues relating to mounting the database:
http://www.microsoft.com/downloads/en/details.aspx?familyid=4BDC1D6B-DE34-4F1C-AEBA-FED1256CAF9A&displaylang=en

It may ultimately require restoring the Exchange database:
http://technet.microsoft.com/en-us/library/aa996859(EXCHG.80).aspx
0
 
Fluid_ImageryAuthor Commented:
The solutions didn't ultimately solve the issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.