Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 304598 - Last Review: October 9, 2001 - Revision: 1.1
FIX: Replication Sessions Terminate With Event 5027, Status 0x80070569
This article was previously published under Q304598
On This Page
SYMPTOMS
When you attempt to synchronize or deploy any Windows Management Instrumentation (WMI) changes (such as Health Monitor settings or networking settings) within a cluster, your synchronization fails and the following error message appears:
Event ID: 5027
Description: Could not connect to target server
Application Center could not connect to the target server <server name> during synchronization <replication ID> and Job <job number>. Status is 0x80070569 Logon failure: the user has not been granted the requested logon type at this computer.
CAUSE
The WMI replication driver attempts to use the ACC_
<controller name> account to log on locally on the target server. If you have removed ACC_
<controller name> from the
Log on locally user rights assignment window or have added ACC_
<controller name> to the
deny logon locally user rights assignment window, you may encounter this problem.
RESOLUTION
To resolve this problem, upgrade to Application Center 2000 Service Pack (SP) 1. For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
309384Â
(http://kbalertz.com/Feedback.aspx?kbNumber=309384/EN-US/
)
INFO: How to Obtain the Latest Application Center 2000 Service Pack
To work around this problem, you should make sure that the ACC_
<controller name> account is set up with
User Rights Assignment as
Log on locally and is not listed under
Deny logon locally. Note that you may have to adjust domain group policies or move your Application Center 2000 server computer accounts to another organizational unit if these user rights are being enforced by Windows 2000 domain Group Policy objects.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was corrected in Application Center 2000 SP1.
MORE INFORMATION
Steps to Reproduce Behavior
- Open the Local Security Settings Microsoft Management Console (MMC) snap-in on a cluster member. Expand Local Policies and then expand User Rights Assignment.
- Click Deny logon locally and add ACC_<controller name> to the list.
- Click Log on locally and remove the check for ACC_<controller name>.
- Right-click Security Settings and click Reload.
- Add a test data group to Health Monitor's Synchronized Monitors.
- Attempt to synchronize the cluster.
- View the Synchronizations node of the Application Center 2000 Admin snap-in and look for 5027 events on the Event tab.
APPLIES TO
- Microsoft Application Center 2000 Standard Edition
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