SQL 2005 Cluster Setup fails when server name has lower case letter in it - by Ben Miller - DBAduck

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 289092 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 7/25/2007 9:10:41 PM
Access Restriction Public


When setting up a SQL 2005 Cluster on Windows 2003 machines with any lowercase letters in the machinename will cause SQL Server 2005 cluster setup to fail at the end when it goes to set up SQL on the second node.

In SQL setup, it will have both server names in upper case letters and will target those to setup SQL on.  When the setup wizard gets to the point of setting up, it will complete the setup on the first node and then fail with "Parameter is Incorrect" and then roll back the setup.  

Related to this, is when SQL setup is rolled back, it leaves the resources it created in place which obviously will fail, and it leaves a reference to the dll for the Resource Type in the Cluster Resource Types, which will cause an error every time you launch Cluster Administrator.
Sign in to post a comment.
Posted by Ben Miller - DBAduck on 8/28/2007 at 1:22 PM
I have attached the log files for the failure that night.
Posted by Microsoft on 8/21/2007 at 10:53 AM
We will try and repro on R2 - but setting up cluster repros takes awhile. Can you also send us your logs?


Amy Lewis (amylewis@microsoft.com)
Posted by Ben Miller - DBAduck on 8/20/2007 at 11:23 AM
The repro should be attempted using Win2k3 R2. This has not been reproduced in Windows 2003 R1.

If you cannot reproduce it on R2 then I will package the logs and send them to you.
Posted by Microsoft on 8/8/2007 at 10:58 AM
We tried to repro this in house and could not do so. We used machines called stplowclusn11 and stplowclusn2. Can you provide us more info on your repro as well as logs?


Amy Lewis (amylewis@microsoft.com)