Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. WINS and DHCP Resources Do Not Failover in Mixed Server Cluster

WINS and DHCP Resources Do Not Failover in Mixed Server Cluster

View products that this article applies to.

This article was previously published under Q293302

↑ Back to the top

Symptoms

In a MicroSoft Cluster Server (MSCS) server cluster, if you are running in mixed mode with versions of Windows Server, you will be unable to fail a WINS or DHCP resource from the Windows Server 2003 to the Windows 2000 node. This type of scenario could be encountered in a Rolling Upgrade situation, and it may generate the following error message when you attempt to bring the resource online on the Windows 2000 node:
Event ID: 412
Type: Error
Source: esent
Description: wins (1044) Unable to read the log header. Error -530.
You may also receive the following error message:
WINS could not start due to a missing or corrupt database.
Restore the database using WINS Manager (or winscl.exe found in the Windows 2000 Resource Kit) and restart WINS. If WINS still does not start, begin with a fresh copy of the database
The WINS and DHCP databases are upgraded when they are moved to the Windows Server 2003 node for the first time, and you receive the following Event ID:
Event ID: 609
Type: Information
Source: esent
Description: wins (3432) The database engine is initiating index cleanup of database " as a result of an NT version upgrade
The new format of the JET databases cannot be read by the Windows 2000 node.

↑ Back to the top

Resolution

Do not run mixed Windows 2000 and Windows Server 2003 nodes in the same cluster when you are using DHCP and WINS resources for an extended amount of time. Because the DHCP and WINS resources can only run on the Windows Server 2003 nodes, there may be a single point of failure, and because of this, you may not have high availability. If you are performing a rolling upgrade to Windows Server 2003:
  1. Move the DHCP and WINS resources to node 2.
  2. Upgrade node 1 from Windows 2000 to Windows Server 2003.
  3. Move the DHCP and WINS resources to node 1.

    NOTE: The JET databases will now be upgraded, and you will not be able to failback the resources to node 2.
  4. Upgrade node 2 from Windows 2000 to Windows Server 2003. You will now be able to fail the resources back and forth without issue.
For additional information about Rolling Upgrade procedures, click the article number below to view the article in the Microsoft Knowledge Base:
174799� How to Install Service Packs in a Cluster

↑ Back to the top

More information

To roll the Cluster back to a pure Windows 2000 environment, you must restore the DHCP and WINS databases from a pre-Windows Server 2003 backup to the shared disk and then restore the Windows Server 2003 server back to Windows 2000. For additional information about restoring WINS or DHCP, click the article numbers below to view the articles in the Microsoft Knowledge Base:
244810� Restoring a Windows 2000 WINS Database from Other Backup Sources
173396� How to Restore a Corrupted DHCP Database File

↑ Back to the top

Keywords: KB293302, kbprb, kbnetwork

↑ Back to the top

Article Info
Article ID : 293302
Revision : 8
Created on : 2/28/2007
Published on : 2/28/2007
Exists online : False
Views : 307