Event 12297 Logged on PDC Role Transfer When Domain Controller Is Not the New PDC

This article was previously published under Q265192
This article has been archived. It is offered "as is" and will no longer be updated.
When you transfer the primary domain controller (PDC) Flexible Single Master Operation (FSMO) role from one domain controller to another, event 12297 may be logged in the System event log with the name of the new PDC. However, this event may be logged on all domain controllers in the domain with the name of the local domain controller as the name of the new PDC. The event message is not correct and is only valid for the new PDC.
The event is logged every time a PDC role change is detected. The code that logs the event does not check whether the local domain controller becomes the PDC.
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 theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
This event does not affect the role transfer; you can ignore the messages on other domain controllers.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.

Article ID: 265192 - Last Review: 10/20/2013 21:52:48 - Revision: 2.2

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server

  • kbnosurvey kbarchive kbbug kbfix KB265192
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)