Microsoft KB Archive/325964

= System Attendant Service Does Not Start, Error with a 9022 in Event Viewer =

Article ID: 325964

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition
 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition

-



This article was previously published under Q325964



SYMPTOMS
If you try to manually start the Microsoft Exchange System Attendant service, the service may not start, and some or all of the following events are logged in the Application event log:

Event Type: Error

Event Source: MSExchangeSA

Event Category: General

Event ID: 9022

Date: 11/14/2000

Time: 4:05:23 PM

User: N/A

Computer: servername

Description: Microsoft Exchange System Attendant encountered an error while processing the security data for Exchange server servername.

-or-

Event Type: Error

Event Source: MSExchangeSA

Event Category: General

Event ID: 9149

Date: 11/14/2000

Time: 4:05:23 PM

User: N/A

Computer: servername

Description: Microsoft Exchange System Attendant failed to start Exchange server servername. Error code '0x8009000f'.

-or-

Event Type: Error

Event Source: MSExchangeSA

Event Category: General

Event ID: 1005

Date: 11/14/2000

Time: 4:05:23 PM

User: N/A

Computer: servername

Description: Unexpected error Object already exists. ID no: 8009000f Microsoft Exchange System Attendant occurred.

where drive is the drive on which Windows is installed.



CAUSE
The system attendant may have a problem when it accesses the key container on the Microsoft Windows 2000 Server-based computer. The first time that system attendant tries to open an existing container, you receive an &quot;NTE_BAD_KEYSET&quot; error message. The system attendant then tries to create a key container with the same name. The key container is rejected, and you receive an &quot;NTE_EXISTS (0x8009000f)&quot; error message, because permissions on one of these key containers are corrupted.



RESOLUTION
To resolve this issue, make sure that the permissions on the MachineKeys folder are not corrupted.

For additional information about how to verify permissions on the MachineKeys folder, click the article number below to view the article in the Microsoft Knowledge Base:

280432 XADM: System Attendant Stops Working with a 9022 Event

After you verify that the permissions on the MachineKeys folder are not corrupted, rename the folder. When you rename the MachineKeys folder, you can manually start the Microsoft Exchange System Attendant service. The Microsoft Exchange System Attendant service then creates a new MachineKeys folder.

To rename the MachineKeys folder, follow these steps:  In Windows Explorer, locate the following folder:

Drive:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys

NOTE: Where drive is the drive on which Windows is installed.

 Right-click the MachineKeys folder, and then click Rename. Type MachineKeys.Old, and then press ENTER. Quit Windows Explorer. Manually start the Microsoft Exchange System Attendant service.

<div class="moreinformation_section">

MORE INFORMATION
For additional information about System Attendant that does not start after disaster recovery, click the article number below to view the article in the Microsoft Knowledge Base:

325674 XADM: System Attendant Does Not Start After Disaster Recovery Installation and Event ID 9022, 9149, 1005 Messages Occur

Additional query words: 9022 9149 1005 SA MSExchangeSA MachineKeys XADM

Keywords: kberrmsg kbprb KB325964

-

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

© Microsoft Corporation. All rights reserved.