Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

SBS 2003 - After Restart Can't Browse OWA

Posted on 2010-09-21
13
901 Views
Last Modified: 2012-05-10
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?  
0
Comment
Question by:Fluid_Imagery
  • 7
  • 3
  • 3
13 Comments
 
LVL 6

Expert Comment

by:collins23
ID: 33725252
have you tried this

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

the last post at the end ?
0
 
LVL 6

Expert Comment

by:collins23
ID: 33725304
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
 

Author Comment

by:Fluid_Imagery
ID: 33725396
we have a single server, sbs 2003.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 

Author Comment

by:Fluid_Imagery
ID: 33725415
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
 
LVL 77

Expert Comment

by:Rob Williams
ID: 33725436
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
 

Author Comment

by:Fluid_Imagery
ID: 33725446
Just looked in Exchange System Manager, stores aren't mounted.  ID is c1041724
0
 
LVL 6

Expert Comment

by:collins23
ID: 33725488
0
 

Author Comment

by:Fluid_Imagery
ID: 33725551
its a problem dealing with teh database not being able to mount, any ideas onthat/
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 33725563
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
 

Author Comment

by:Fluid_Imagery
ID: 33725586
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
 
LVL 77

Expert Comment

by:Rob Williams
ID: 33725656
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
 

Accepted Solution

by:
Fluid_Imagery earned 0 total points
ID: 34006328
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
 

Author Closing Comment

by:Fluid_Imagery
ID: 34031754
The solutions didn't ultimately solve the issue.
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question