Microsoft KB Archive/821907

= How to Troubleshoot Exchange Server 2003 System Attendant When It Does Not Start =

Article ID: 821907

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition

-





SUMMARY
This article describes how to troubleshoot Exchange Server 2003 System Attendant in situations when it does not start. If System Attendant does not start, none of the other Exchange Server 2003 services start. To help you determine the cause of this problem, you can use Exchange System Manager to run diagnostic logging on System Attendant.



MORE INFORMATION
To use Exchange System Manager to start Exchange Server 2003 System Attendant diagnostic logging, follow these steps:  Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. Expand  , and then expand Servers. Right-click  , and then click Properties.

Note If System Attendant is not running, you receive the following error message:

The Microsoft Exchange System Attendant service is unavailable. Verify that the Server is running and that the System Attendant service has been started. ID no: c1031668

Click OK to close this error message. Click the Diagnostic Logging tab, and then click MSExchangeSA in the Services list. In the Categories list, click each of the following sub-components, and then click the logging level that is appropriate for your troubleshooting scenario in the Logging Level box:  Mailbox Management NSPI Proxy</li> RFR Interface</li> OAL Generator</li> Proxy Generation</li> RPC Calls</li></ul> </li> Use Event Viewer to monitor the logged events.</li></ol>

System Attendant may not start in the following scenarios: <ul> Exchange Server 2003 System Attendant acts as a proxy between requests from earlier versions of client programs (Microsoft Outlook 97 and Microsoft Outlook 98) and the Microsoft Active Directory directory service, and it refers client requests (for clients such as Microsoft Outlook 2000) to Active Directory. If System Attendant cannot locate a domain controller to issue proxy requests or referrals to, System Attendant may not start. You can determine the destination server by reviewing the events that System Attendant logs in Event Viewer.</li> System Attendant loads the following dynamic-link libraries (DLLs) to its address space: <ul> Dsaccess.dll</li> Dsproxy.dll</li> Seckm.dll</li> Abv_dg.dll</li> Ds2mb.dll</li> Madfb.dll</li> Oabgen.dll</li></ul>

If any of these files are missing, corrupted, or have the incorrect permissions applied to them, System Attendant may not start.</li></ul>

Keywords: kbhowto KB821907

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.