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

OWA errors out with HTTP/1.1 503 Service Unavailable

Here is a little background on this.

Several weeks ago a 5.5 server was transitioned to a new machine running Win2K and Exchange 2000.  From what I am told the install did not go well, but eventually everything worked with the exception of OWA.  When I got there, if you tried to access OWA you were prompted for credentials.  You then received "error: Access is denied".  Followed MS KB 317471 for resetting permissions.  Now the error is "HTTP/1.1 503 Service Unavailable" after supplying credentials.  Incidentally, once I try to log on after closing my browser I no longer get prompted for credentials and just get the 503 service unavailable message.  

I then started going through KB 305030 and was stopped when I tried to re-register the dll's.  For some reason I regsvr32 would not allow me to register them again.  Unfortunately, I didn't  writed down the exact error message.  Does anyone have a suggestion?

Thanks-Pete
0
Pete23
Asked:
Pete23
  • 3
  • 2
  • 2
4 Solutions
 
David WilhoitSenior Consultant, ExchangeCommented:
This looks like a permissions error. Are users able to contact the mailbox with Outlook? If not, have you checked to see that the stores are mounted?

Check the permissions on the information store, ensure that these permissions are present:

Administrators: Full Control
Authenticated Users: Read and Execute, List Folder Contents, Read
Creator Owner: None
Server Operators: All except Full Control
System: Full Control


D
0
 
tbird008Commented:
Hi Pete23,

Here is the offical link for this problem
http://support.microsoft.com/?ID=282230

you can download a troubleshooting white paper here
http://support.microsoft.com/default.aspx?scid=kb;en-us;326303

Tbird008
0
 
Pete23Author Commented:
Apparently I have walked in to a train wreck.  Things just keep getting more interesting...checked the permissions per Kidego's post without any noticeable change (except that the users/groups were not there).  I then tried Tbird008's suggestion of KB article 282230 (which I had mistakenly rejected last night).  What I saw in IIS was that the configuration was incomplete.  I haven't done much with Exchange or IIS in a long while, so I didn't pick up on it right away.  The Exchange website still showed as a folder with globe rather than the open box.  I clicked "create" from within Virtual Directory properties.  I then removed the davex entry and tried the site.  

Things are better, but they are also worse.  I can now log in, but now I see a directory listing of all the mailboxes which I can click through until I get to an actual message.  When I click the message in the FTP-like view I get a file not found.

For some reason, the guy that set up the server reset permissions on C:\ to everyone-full control.  Is it me or do I see a rebuild coming?
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

 
tbird008Commented:
Hi Pete23,

Not to worry about it c:\ root is by default security permissions is allow full access to everyone.
Can you specify on the problem about what you trying to accomplish and the problem it produce.
I'll check back a bit later go to finish my project here : )

Tbird008
0
 
David WilhoitSenior Consultant, ExchangeCommented:
you can always reinstall Exchange to reset the default permissions, and of course reapply your service pack. You don't have to remove it. The default IIS perms for Exchange should get reset as well.

D
0
 
Pete23Author Commented:
Alright, not looking forward to reinstalling Exchange/IIS.  I am encouraged that I see an FTP-like listing of the mailboxes (not sure why I am seeing all of them when I log on as a user, but user has administrative privs).

Can you tell me which virtual directories are supposed to be published?  When I started, Exchange was the only published virtual directory.  After publishing Exchweb I get the FTP-like listing of mailboxes.  

If it do have to reinstall Exchange/IIS can you give me an idea of how long the backup/reintall/restore would take with a 3 gig IS on a brand new machine?  Will I have to do a restore?

Thanks for the help.
0
 
David WilhoitSenior Consultant, ExchangeCommented:
reinstall does NOT entail removing Exchange or the databases. Only reinstall and reapply the service packs.
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.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

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