Microsoft KB Archive/297881

= &quot;Error 0x80071392&quot; May Be Displayed When the Cluster Node Is Unable to Join the Cluster =

Article ID: 297881

Article Last Modified on 3/2/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

-



This article was previously published under Q297881



SYMPTOMS
When you attempt to join a node to a cluster, you may receive the following error message:

An error occurred attempting to add this computer to the sponsor cluster database.

Error 0x80071392: The object already exists

Also, the following error may be logged in the Configuration log (ClCfgSrv.log):

yyyy-mm-dd hh:mm:ss.sss NodeName: (null)

(hr=0x80071392,{BAD76434-CE21-4BA0-A295-3CBFA8C72142},{3222E708-EEF3-4667-8CCE-BB0C9223130E},0,2,1), (null)

The following error may also be logged in the Cluster log:

00000fd4.00000a30::2001/05/10-19:20:54.359 WARN [NMJOIN] Failed to create object for node nodename, status 5010.

00000fd4.00000a30::2001/05/10-19:20:54.359 INFO [DM] DmAbortLocalUpdate Entry

00000fd4.00000a30::2001/05/10-19:20:54.359 INFO [LM] LogAbortXsaction : Entry, hXsaction=0x001377f8

00000fd4.00000a30::2001/05/10-19:20:54.359 INFO [LM] LogWrite : Entry TrId=398 RmId=5 RmType = 0 Size=0

00000fd4.00000a30::2001/05/10-19:20:54.359 INFO [LM] LogWrite : Exit returning=0x00000980

00000fd4.00000a30::2001/05/10-19:20:54.359 INFO [LM] LogAbortXsaction : Exit, returning, dwError=0x00000000

00000fd4.00000a30::2001/05/10-19:20:54.359 INFO [DM] DmpRestartFlusher: Entry

00000fd4.00000a30::2001/05/10-19:20:54.390 INFO [DM] DmAbortLocalUpdate Exit, returning 0x00000000

00000fd4.00000ffc::2001/05/10-19:20:54.390 INFO [DM] DmpRegistryFlusher: restarting

00000fd4.00000a30::2001/05/10-19:20:54.390 ERR [GUM] Update routine 17186173 failed with status 5010

00000fd4.00000a30::2001/05/10-19:20:54.406 INFO [GUM] GumpDoUnlockingUpdate releasing lock ownership

00000fd4.00000a30::2001/05/10-19:20:54.406 WARN [GUM] Queued lock attempt for send type 2 failed 5010

00000fd4.00000318::2001/05/10-19:21:40.437 INFO [LM] LogFlush: pLog=0x00151d50 writing the 1024 bytes for active page at offset 0x00000800



CAUSE
This problem can occur when you attempt to add a node to a cluster that had previously been a member of that cluster. You removed the Cluster service, and then reinstalled it on the node. However, you removed the Cluster service before you removed the node from the cluster database.



RESOLUTION
To resolve this problem, start the Cluster Administrator tool (CluAdmin.exe), right-click the node name that you want to add, and then click Evict Node. Then, you must re-run the Configuration Wizard and re-add the node to the cluster.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
If you remove the node, but this problem is not corrected, you may have to manually remove the Cluster service with the cluster node /force command.

Additional query words: MSCS install setup 80071392 5010

Keywords: kbbug kbenv kberrmsg kbpending KB297881

-

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

© Microsoft Corporation. All rights reserved.