Microsoft Knowledge Base Email Alertz
All KB/RSS Links  |  Hot Kb!  |  New Kb!  |  Scott Cate  |  FAQ / KB  |  Web Hosting  |  Unsubscribe  

KBAlertz.com: The System Attendant resource cannot fail over in an Exchange Server 2003 cluster, and event IDs 1069, 1082 and, 1121 are logged

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.
Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 2.0 Web Hosting with SQL 2005: Click Here!
Discount ASP.NET Hosting

Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.

Community Site


We Send hundreds of thousands of emails using ASP.NET Email


Expert Web Design & Graphic Design
Design44.com




Mentioned In







Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks



The System Attendant resource cannot fail over in an Exchange Server 2003 cluster, and event IDs 1069, 1082 and, 1121 are logged

View products that this article applies to.
Article ID:951577
Last Review:April 21, 2008
Revision:1.0

SYMPTOMS

The System Attendant resource cannot fail over in a Microsoft Exchange Server 2003 cluster environment. Additionally, the following events are logged in the Application log on the active node.

Event ID 1069

Event Type: Error
Event Source: ClusSvc
Event Category: Failover Mgr
Event ID: 1069
Date: Date
Time: Time
User: N/A
Computer: Node2
Description:
Cluster resource 'SA' in Resource Group 'ResourceGroupName' failed.

Event ID 1082

Event Type: Erro
Event Source: ClusSvc
Event Category: Checkpoint Mgr
Event ID: 1082
Date: Date
Time: Time
User: N/A
Computer: Node2
Description:
Cluster service failed to restore a registry key for resource SA when it was brought online. This error code was 6001.

Event Type: Error
Event Source: ClusSvc
Event Category: Checkpoint Mgr
Event ID: 1082
Date: Date
Time: Time
User: N/A
Computer: Node2
Description:
Cluster service failed to restore a registry key for resource SA when it was brought online. This error code was 6001.

Event Type: Error
Event Source: ClusSvc
Event Category: Checkpoint Mgr
Event ID: 1082
Date: Date
Time: Time
User: N/A
Computer: Node2
Description:
Cluster service failed to restore a registry key for resource SA when it was brought online. This error code was 6001.

Event Type: Error
Event Source: ClusSvc
Event Category: Checkpoint Mgr
Event ID: 1082
Date: Date
Time: Time
User: N/A
Computer: Node2
Description:
Cluster service failed to restore a registry key for resource SA when it was brought online. This error code was 1917. Some changes may be lost.

Event ID 1121

Event Type: Error
Event Source: ClusSvc
Event Category: Checkpoint Mgr
Event ID: 1121
Date: Date
Time: Time
User: N/A
Computer: Node1
Description:
The crypto checkpoint for cluster resource 'SA' could not be restored to the container name 'ContainerName'. The resource may not function correctly.

Back to the top

CAUSE

This problem occurs if two nodes use different accounts to run the Cluster Service.

Back to the top

RESOLUTION

After you verify that different accounts are configured for the Cluster Service, configure the nodes to use the same account for the Cluster Service. To do this, follow these steps.

Note The following steps assume that you are running a typical two-node cluster.
1.Stop the Cluster Service on node 1.
2.Change the startup type of the Cluster Service to Manual.
3.Wait until all resources are listed under node 2 in Cluster Administrator.
4.Change the account of the Cluster Service on node 1.
5.Change the startup type of the Cluster Service back to Automatic.
6.Start the Cluster Service on node 1.
7.Test a failover between node 1 and node 2.

Back to the top

APPLIES TO
•Microsoft Exchange Server 2003 Enterprise Edition
•Microsoft Exchange Server 2003 Service Pack 1
•Microsoft Exchange Server 2003 Service Pack 2

Back to the top

Keywords: 
kbexpertiseadvanced kbtshoot kbexpertiseinter kbprb KB951577

Back to the top

        

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name
(Optional) Public URL Or Email
Comments
No HTML -- Text Only Please

 



Copyright © 2002-2007 KBALERTZ.COM.  All Rights Reserved. Terms / Privacy. Discount ASP.NET Hosting