Article ID: 823159 - Last Review: December 3, 2007 - Revision: 6.4 How to troubleshoot the "503 Service Unavailable" error message in Outlook Web Access in Exchange Server 2003On This PageSUMMARYAfter you type the address to Microsoft Outlook Web Access
(OWA) on a Microsoft Exchange Server 2003 computer, you may receive the
following error message in your browser before you receive the OWA log on
prompt: 503 Service Unavailable This problem occurs if the Davex.dll file cannot communicate with a mailbox store or with a public folder store. Make sure that all the services are runningThe "503 Service Unavailable" error message may occur if the Exchange 2003 services are not running, particularly if the System Attendant service and the Information Store service are not running. To view the services and make sure that all the services are running:
Make sure that the services are running under the Local System accountThe "503 Service Unavailable" error message may occur if the Exchange 2003 services are not running under the Local System account. To make sure that the services are running under the Local System account:
Mount the mailbox stores and the public folder storesThe "503 Service Unavailable" error message may occur if the mailbox stores and the public folder stores that you want to gain access to are not mounted. Therefore, you must mount the mailbox stores and the public folder stores. To mount the mailbox stores and the public folder stores:
See if a registry key that exceeds 259 characters exists in the HKEY_CLASSES_ROOT registry hiveThe "503 Service Unavailable" error message may occur if a registry key that exceeds 259 characters exists in the HKEY_CLASSES_ROOT registry hive. During initialization, the Exchange OLE DB provider (ExOLEDB) scans the HKEY_CLASSES_ROOT hive to identify registered file types. If any subkey has a default value that exceeds 259 characters, or if there is a discretionary access control list that is not valid on one of the subkeys, ExOLEDB may quit unexpectedly.If a subkey exceeds 259 characters, or if there is a discretionary access control list that is not valid, the following series of event ID messages are logged in the application event log when you restart the Exchange 2003 services: Event Type: Information
Event Source: MSExchangeSA Event Category: General Event ID: 9014 Description: Microsoft Exchange System Attendant has been started for Exchange server servername successfully. Event Type: Information Event Source: MSExchangeSA Event Category: Monitoring Event ID: 9095 Description: The MAD Monitoring thread is initializing. Event Type: Information
Event Source: MSExchangeSA Event Category: Monitoring Event ID: 9096 Description: The MAD Monitoring thread is initialized. Event Type: Information Event Source: EXOLEDB Event ID: 101 Description: Microsoft Exchange OLEDB has successfully shutdown. Event Type: Error
Additionally, the following event ID message may be logged in the
application event log multiple times. The Free/Busy service may also generate
some errors.Event Source: MSExchangeIS Event ID: 9542 Description: Initialization of external interface OLEDB failed; Error ecServerOOM. Event Type: Error
The following event ID message may be logged in the system log
multiple times:Event Source: EXCDO Event Category: General Event ID: 8206 Description: Calendaring agent failed with error code 0x800XXXXX while saving appointment. Event Type: Error
To help troubleshoot this issue, run the HKCRScan tool
(HKCRScan.exe). The HKCRScan tool enumerates the HKEY_CLASSES_ROOT registry
hive to locate subkeys that contain more than 259 characters. Additionally,
HKCRScan helps determine if there is an invalid discretionary access control
list by returning error code 0x5. This error code means "Access denied" when it
enumerates a registry key. The HKCRScan tool is an internal tool developed by
Microsoft. To obtain this tool, contact Microsoft Product Support Services
(PSS). For additional information about how to contact PSS, visit the following
Microsoft Web site: Event Source: DCOM Event Category: None Event ID: 10002 Description: Access denied attempting to launch a DCOM Server. The server is: {9DA0E106-86CE-11D1-8699-00C04FB98036} The user is SYSTEM/NT AUTHORITY, SID=S-1-5-18 http://support.microsoft.com
(http://support.microsoft.com/)
See if a Group Policy object exists that prevents the MSExchangeIS service from initializingThe "503 Service Unavailable" error message may occur if a Group Policy object (GPO) exists that prevents the MSExchangeIS service from initializing.You may notice event ID messages that are similar to the Event 101 EXOLEDB and the Event 9542 MSExchangeIS that this article describes. Note The descriptions of the event ID messages may be different from those that are listed in this article. You may also notice the following event ID messages: Event Type: Error
Event Source: EXCDO Event ID: 8208 Description: Calendaring agent failed with error code 0x8000ffff while expanding recurring appointments. Event Type: Error
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: Event Source: DCOM Event ID: 10009 Description: DCOM was unable to communicate with the computer RCC-EXH-02-W using any of the configured protocols. 322756
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows To work around this issue:
Reregister the MDAC ComponentsIf you view event ID 101 EXOLEDB messages and event ID 9542 MSExchangeIS messages such as the following event ID messages, some Microsoft Data Access Components (MDAC) may be incorrectly registered, and you must reregister them:Event Type: Information
Event Source: EXOLEDB Event ID: 101 Description: Microsoft Exchange OLEDB has successfully shutdown. Event Type: Error
Event Source: MSExchangeIS Event ID: 9542 Description: Initialization of external interface OLEDB failed; Error Unknown error. The following list contains the .dll files that you must have so that you can reregister the MDAC components to resolve this issue. You must stop the Information Store service before you reregister the files and then restart the Information Store service after you successfully reregister the following .dll files. Note The Oledb32.dll file version must be 2.8.1022.0 or later.
Load
library("path and file name") failed - The specified procedure could not be
found 837285
(http://support.microsoft.com/kb/837285/
)
Users may receive a "503 Service Unavailable" error message in Exchange Server 2003 when they try to use a Web browser to gain access to OWA
| Article Translations
|
Back to the top
