You cannot install AD DS in Windows Server 2008 in a Windows Server 2003-based domain if another computer that is in the same domain has MSCS installed

Consider the following scenario:

  • You install Microsoft Cluster Service (MSCS) on a computer that is running Windows Server 2003 Service Pack 2 (SP2).

  • You join this computer to a Windows Server 2003-based domain.

  • You try to install Active Directory Domain Services (AD DS) on a computer that is running Windows Server 2008 in the domain.

In this scenario, the installation operation of Active Directory Domain Services (AD DS) fails together with an Active Directory Replication error. Additionally, the following event is added to the Active Directory Domain Services log:

This issue occurs because the Cluster service on the computer that is running Windows Server 2003 SP2 calculates the buffer size for the service principal name (SPN) of the Cluster service incorrectly. This behavior causes the SPN entry not to have a null terminator in the Active Directory database. Therefore, some random characters are appended to the valid SPN names in the Active Directory database.

When AD DS is installed on the computer that is running Windows Server 2008, an Active Directory replication occurs from the domain controller that is running Windows Server 2003 to the computer that is running Windows Server 2008. However, the Active Directory replication fails because of these invalid SPN names. Therefore, the issue occurs.

To resolve this issue, install this hotfix on the affected cluster nodes that are running Windows Server 2003 SP2.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

To apply this hotfix, you must be running Windows Server 2003 Service Pack 2 (SP2). Additionally, you must have MSCS installed.

For more information about how to obtain a Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

To use the hotfix in this package, you do not have to make any changes to the registry.

You do not have to restart the computer after you apply this hotfix.

This hotfix does not replace a previously released hotfix.

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

  • In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.

File name

File version

File size

Date

Time

Platform

SP requirement

Service branch

Clusdisk.sys

5.2.3790.4700

69,120

28-Apr-2010

14:42

x86

SP2

SP2QFE

Clusres.dll

5.2.3790.4700

477,696

29-Apr-2010

05:27

x86

SP2

SP2QFE

File name

File version

File size

Date

Time

Platform

SP requirement

Service branch

Clusdisk.sys

5.2.3790.4700

112,128

29-Apr-2010

03:43

x64

SP2

SP2QFE

Clusres.dll

5.2.3790.4700

649,216

29-Apr-2010

03:43

x64

SP2

SP2QFE

File name

File version

File size

Date

Time

Platform

SP requirement

Service branch

Clusdisk.sys

5.2.3790.4700

214,528

29-Apr-2010

03:43

IA-64

SP2

SP2QFE

Clusres.dll

5.2.3790.4700

1,152,000

29-Apr-2010

03:43

IA-64

SP2

SP2QFE

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about the SPN, view the following Microsoft website:

General information about the SPNFor more information about the name formats for unique SPNs, view the following Microsoft website:

The name formats for unique SPNsFor more information about how a service registers its SPNs, view the following Microsoft website:

How a service registers its SPNsFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Meer hulp nodig?

Uw vaardigheden uitbreiden
Training verkennen
Als eerste nieuwe functies krijgen
Deelnemen aan Microsoft insiders

Was deze informatie nuttig?

Wat heeft uw ervaring beïnvloed?

Hebt u aanvullende feedback? (Optioneel)

Bedankt voor uw feedback.

×