Damaged Phantom Object Prevents Infrastructure Phantom Cleanup Task from Running (318170)


The information in this article applies to:

  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2
This article was previously published under Q318170

SYMPTOMS

The infrastructure master in a domain may log events 1655 and 1126 that are similar to these events:
Event Type: Error
Event Source: NTDS General
Event Category: Global Catalog
Event ID: 1126
Date: date
Time: time
User: Everyone
Computer: DC
Description: Unable to establish connection with global catalog.

Event Type: Warning
Event Source: NTDS General
Event Category: Global Catalog
Event ID: 1655
Date: date
Time: time
User: Everyone
Computer: DC
Description:
The attempt to communicate with global catalog \\GC.root.com failed with the following status:

An invalid parameter was specified for this replication operation.

The operation in progress might be unable to continue. The directory service will use the locator to try find an available global catalog server for the next operation that requires one.
The record data is the status code.

Data: 0000: f5 20 00 00
These events appear in periodic intervals, shortly after you restart your domain controller, and then every 24 hours.

CAUSE

This problem may occur if you have a damaged object. You may be able to see this object by dumping the Ntds.dit file by using LDP:

451667 187189 false 11 0 0 2002-01-17 10:37.32 - - - - - [GarbledCharacters]
CNF:f956fe15-d932-4cc2-b15d-71bd07f8efca

This object is a damaged phantom object that results in ERROR_DS_DRA_INVALID_PARAMETER on the GC when the infrastructure master runs its phantom cleanup task every 24 hours.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

STATUS

Microsoft has confirmed that this is a problem in Microsoft Windows 2000. This problem was first corrected in Windows 2000 Service Pack 3.
Modification Type:MajorLast Reviewed:12/3/2003
Keywords:kbbug kbDirServices kbenv kberrmsg kbfix kbWin2000PreSP3Fix kbWin2000sp3fix KB318170
©2003 Microsoft Corporation. All rights reserved.