SQL Server Setup in a cluster environment encounters an access violation if you have a long computer name

Article translations Article translations
Article ID: 289828 - View products that this article applies to.
This article was previously published under Q289828
BUG #: 352185 (SHILOH_BUGS)
BUG #: 56504 (SQLBUG_70)
Expand all | Collapse all

SYMPTOMS

A SQL Server Setup in a cluster encounters an access violation after an account is assigned to perform a remote installation in a Microsoft Clustering Services (MSCS) environment if following are true:

  • With SQL Server 2000 Enterprise Edition, all the nodes in the cluster are configured as possible nodes of the virtual server.

  • The computer name of the primary domain controller (PDC) of the domain in which the cluster resides contains 14 or 15 characters.
Typically, this problem occurs when two nodes of the cluster are set up as the only domain controllers in the domain and both have a computer name containing 14 or 15 characters.

NOTE: For SQL Server 7.0, you will encounter the problem even if you run a setup of the Standard Edition in a cluster environment.

If you have the correct configuration for Dr. Watson, Dr. Watson captures the InstallShield application error.

WORKAROUND

To work around this problem, change the computer name so that it contains no more than 13 characters.

Properties

Article ID: 289828 - Last Review: April 6, 2006 - Revision: 3.3
APPLIES TO
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 7.0 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
Keywords: 
kbtshoot kbbug kbpending kbprb KB289828

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com