Tim Hackbart [MSFT]
Guest
|
Posted:
Fri Dec 10, 2004 6:03 am Post subject:
Re: OWA HTTP 500 Internal Server Error |
|
|
It is really hard to say for sure what happened, but there are some
processes that may have engaged to resolve the issue.
On a cluster, the IIS and the Metabase are NOT cluster resources, each node
has its own independent IIS Services and Metabase. The Exchange HTTP
Virtual Server resource has an Active Directory object, seen in the Exchange
System Manager under Servers-Protocols-HTTP. This object and its settings
are replicated to the Metabase on the Active Cluster Node's metabase by the
DS2MB, aka MSExchangeMU service which runs in the System Attendant. The
Directory Service to MetaBase (DS2MB) process is a one way replication form
the AD to the Metabase which runs at startup and then intermittently after
that.
It is possible that the Metabase on the Active Node was possibly corrupt or
incomplete and that the DS2MB service eventually updated or repaired it to a
condition where it could start.
See 843093 How to troubleshoot IIS metabase corruption on a computer that is
http://support.microsoft.com/?id=843093 for more information.
Once again this is only a guess, and a little more insight into the DS2MB
process
--
Tim Hackbart M.C.S.E.
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"CornExch" <cornetthd@yahoo.com> wrote in message
news:1102367573.164090.128120@z14g2000cwz.googlegroups.com...
| Quote: | We have a Back End cluster in Region 1 and a BE cluster in Region 2.
There is a Front End server in Region 1 for OWA and SMTP. We had to
shut down the server in Region 2 for a power outage. After being down
for 16 hours the servers were brought back online. Email traffic is
flowing normally from the Front end to Back End server via SMTP
traffic. When I logged in to the OWA server with an account located on
the Region 1 BE server everything worked fine. When I logged into the
BE server located in Region 2 I would get an HTTP 1/1 500 Internal
Server Error. After the BE server in Region 2 was online for about an
hour this error cleared up and OWA service was back to normal. What
would cause the OWA service to start working after being online for an
hour? Any help would be appreciated.
|
|
|