Article ID: 298570 - View products that this article applies to.
This article was previously published under Q298570
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 352185 (SHILOH_BUGS)
BUG #: 353952 (SHILOH_BUGS)
The SQL Server setup, for SQL Server 2000 and its service packs, may cause an Access Violation (AV) in the SQL Server Setup User Interface on a cluster setup when either or both nodes are domain controllers. If both nodes (of a two node cluster) are domain controllers, the unhandled Access Violation may occur when the setup authenticates the service account. When the AV occurs, the setup either stops responding (hangs) or the installation disappears from the screen leaving the setup files running in the background. Alternately, a machine name in excess of 15 characters on the domain controller may also cause the installation to fail.
NOTE: On a Microsoft Windows NT Server, Enterprise Edition 4.0-based computer, Microsoft recommends that you make cluster nodes backup domain controllers. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
171390However, if a domain controller is already local, or if there is reliable high-speed connectivity to a domain controller available, Microsoft does not recommend implementing a domain controller on cluster nodes on Microsoft Windows 2000-based computers.
(https://support.microsoft.com/kb/171390/EN-US/ )Cluster Service May Not Start if Domain Controller Is Unavailable
(https://support.microsoft.com/kb/281662/EN-US/ )Windows 2000 Cluster Nodes as Domain Controllers
To work around the problem, install SQL Server to a Microsoft Windows 2000 Cluster whose nodes are not domain controllers that have local or high-speed connectivity to a Microsoft Windows 2000 domain controller.
Steps to Reproduce the Behavior
(https://support.microsoft.com/kb/289828/EN-US/ )PRB: SQL Server Setup in a Cluster Environment Encounters an Access Violation If You Have a Long Computer Name