all groups > sql server clustering > february 2006 >
You're in the

sql server clustering

group:

SQL Server Install of Named Instance on 2003 fails


SQL Server Install of Named Instance on 2003 fails Chris
2/23/2006 8:15:57 AM
sql server clustering:
I am installing an SQL Server 2000 Active Active cluster on a Windows
2003 cluster. I am unable to install the Virtual SQL Server as a Named
Instance. I can succefully install SQL Server as a local or default
named instance. I have added the client config utility to both nodes
and created a named pipes entry for the virtual server as described in
the KB article http://support.microssoft.com/?id=815431. This does not
seem to help. However the errors I am seeing seem to point me to this
article. The following is the sqlclstr.log. If anyone has any
thoughts of something I could try I would be very thankful. Also a
sample of the event log is as follows...

thanks
Chris

Eventlog:
[sqsrvres] ODBC sqldriverconnect failed
[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 11;
message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does
not exist or access denied.

SQLClstr.log:
calling ClusterGetComputerNames
ClusterGetComputerNames: m_LocalComputerName=[]
ClusterGetComputerNames: calling GetComputerName
ClusterGetComputerNames: m_LocalComputerName=[PHIF05]
ClusterGetComputerNames: calling ClusterOpenEnum
ClusterGetComputerNames: calling ClusterEnum[0]
ClusterGetComputerNames: calling ClusterEnum[1]
called ClusterGetComputerNames, status=0x0
CreateSQLResourceTypes: calling ClusterEnum(0)
ClusterEnum(0): enter
ClusterEnum(0): [IP Address]
CreateSQLResourceTypes: called ClusterEnum(0), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(1)
ClusterEnum(1): enter
ClusterEnum(1): [Network Name]
CreateSQLResourceTypes: called ClusterEnum(1), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(2)
ClusterEnum(2): enter
ClusterEnum(2): [Physical Disk]
CreateSQLResourceTypes: called ClusterEnum(2), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(3)
ClusterEnum(3): enter
ClusterEnum(3): [DHCP Service]
CreateSQLResourceTypes: called ClusterEnum(3), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(4)
ClusterEnum(4): enter
ClusterEnum(4): [Distributed Transaction Coordinator]
CreateSQLResourceTypes: called ClusterEnum(4), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(5)
ClusterEnum(5): enter
ClusterEnum(5): [File Share]
CreateSQLResourceTypes: called ClusterEnum(5), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(6)
ClusterEnum(6): enter
ClusterEnum(6): [Generic Application]
CreateSQLResourceTypes: called ClusterEnum(6), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(7)
ClusterEnum(7): enter
ClusterEnum(7): [Generic Script]
CreateSQLResourceTypes: called ClusterEnum(7), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(8)
ClusterEnum(8): enter
ClusterEnum(8): [Generic Service]
CreateSQLResourceTypes: called ClusterEnum(8), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(9)
ClusterEnum(9): enter
ClusterEnum(9): [Local Quorum]
CreateSQLResourceTypes: called ClusterEnum(9), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(10)
ClusterEnum(10): enter
ClusterEnum(10): [Majority Node Set]
CreateSQLResourceTypes: called ClusterEnum(10), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(11)
ClusterEnum(11): enter
ClusterEnum(11): [Microsoft Search Service Instance]
CreateSQLResourceTypes: called ClusterEnum(11), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(12)
ClusterEnum(12): enter
ClusterEnum(12): [MSMQ]
CreateSQLResourceTypes: called ClusterEnum(12), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(13)
ClusterEnum(13): enter
ClusterEnum(13): [Print Spooler]
CreateSQLResourceTypes: called ClusterEnum(13), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(14)
ClusterEnum(14): enter
ClusterEnum(14): [SQL Server]
CreateSQLResourceTypes: called ClusterEnum(14), status=0x0
CreateSQLResourceTypes: calling ClusterEnum(15)
ClusterEnum(15): enter
ClusterEnum(15): [SQL Server Agent]
CreateSQLResourceTypes: called ClusterEnum(15), status=0x0
ClusterGetClusterDiskInfo: i=0
ClusterEnum(0): enter
ClusterEnum(0): [Disk Q:]
ClusterGetClusterDiskInfo: GetClassType
ClusterGetClusterDiskInfo: ClusterResourcePhysDiskGetDevNames
ccNodeName=1024 ccGroupName=1024
szNodeName=[PHIF05] szGroupName=[Cluster Group]
csNodeName=[PHIF05] csGroupName=[Cluster Group]
csNodeName=[PHIF05].csGroupName=[Cluster Group]
ClusterGetClusterDiskInfo: i=1
ClusterEnum(1): enter
ClusterEnum(1): [I:\ LogFiles]
ClusterGetClusterDiskInfo: GetClassType
ClusterGetClusterDiskInfo: ClusterResourcePhysDiskGetDevNames
ccNodeName=1024 ccGroupName=1024
szNodeName=[PHIF04] szGroupName=[PHIF04_SQLSERVER1]
csNodeName=[PHIF04] csGroupName=[PHIF04_SQLSERVER1]
csNodeName=[PHIF04].csGroupName=[PHIF04_SQLSERVER1]
ClusterGetClusterDiskInfo: i=2
ClusterEnum(2): enter
ClusterEnum(2): [H:\ Data Files]
ClusterGetClusterDiskInfo: GetClassType
ClusterGetClusterDiskInfo: ClusterResourcePhysDiskGetDevNames
ccNodeName=1024 ccGroupName=1024
szNodeName=[PHIF04] szGroupName=[PHIF04_SQLSERVER1]
csNodeName=[PHIF04] csGroupName=[PHIF04_SQLSERVER1]
csNodeName=[PHIF04].csGroupName=[PHIF04_SQLSERVER1]
ClusterGetClusterDiskInfo: i=3
ClusterEnum(3): enter
ClusterEnum(3): [K:\ Backups]
ClusterGetClusterDiskInfo: GetClassType
ClusterGetClusterDiskInfo: ClusterResourcePhysDiskGetDevNames
ccNodeName=1024 ccGroupName=1024
szNodeName=[PHIF04] szGroupName=[PHIF04_SQLSERVER1]
csNodeName=[PHIF04] csGroupName=[PHIF04_SQLSERVER1]
csNodeName=[PHIF04].csGroupName=[PHIF04_SQLSERVER1]
ClusterGetClusterDiskInfo: i=4
ClusterEnum(4): enter
ClusterEnum(4): [J:\ MSDTC_LogFiles]
ClusterGetClusterDiskInfo: GetClassType
ClusterGetClusterDiskInfo: ClusterResourcePhysDiskGetDevNames
ccNodeName=1024 ccGroupName=1024
szNodeName=[PHIF04] szGroupName=[PHIF04_SQLSERVER1]
csNodeName=[PHIF04] csGroupName=[PHIF04_SQLSERVER1]
csNodeName=[PHIF04].csGroupName=[PHIF04_SQLSERVER1]
ClusterGetClusterDiskInfo: i=5
ClusterEnum(5): enter
ClusterEnum(5): [SQL IP Address1(IFORCE01)]
ClusterGetClusterDiskInfo: GetClassType
ClusterGetClusterDiskInfo: not a disk
ClusterGetClusterDiskInfo: i=6
ClusterEnum(6): enter
ClusterEnum(6): [SQL Network Name(IFORCE01)]
ClusterGetClusterDiskInfo: GetClassType
ClusterGetClusterDiskInfo: not a disk
ClusterGetClusterDiskInfo: i=7
ClusterEnum(7): enter
ClusterEnum(7): [SQL Server]
ClusterGetClusterDiskInfo: GetClassType
ClusterGetClusterDiskInfo: not a disk
ClusterGetClusterDiskInfo: i=8
ClusterEnum(8): enter
ClusterEnum(8): [SQL Server Agent]
ClusterGetClusterDiskInfo: GetClassType
ClusterGetClusterDiskInfo: not a disk
ClusterGetClusterDiskInfo: i=9
ClusterEnum(9): enter
ClusterEnum(9): [SQL Server Fulltext]
ClusterGetClusterDiskInfo: GetClassType
ClusterGetClusterDiskInfo: not a disk
ClusterGetClusterDiskInfo: i=10
ClusterEnum(10): enter
ClusterEnum(10): [Cluster IP Address]
ClusterGetClusterDiskInfo: GetClassType
ClusterGetClusterDiskInfo: not a disk
ClusterGetClusterDiskInfo: i=11
Re: SQL Server Install of Named Instance on 2003 fails Chris
2/23/2006 8:54:19 AM
It was in the year 2000 so I will try to find a newer version. If this
fixes it I would have never found this one thanks alot. I'll keep you
updated.

Chris
Re: SQL Server Install of Named Instance on 2003 fails Chris
2/23/2006 10:24:45 AM

Thanks for the update I am coping the 2003 version to the server right
now. It's a remote server so it's taking awile. I'll update you when
I finish. Thanks Again....
Chris
Re: SQL Server Install of Named Instance on 2003 fails Geoff N. Hiten
2/23/2006 11:46:39 AM
I have had some problems with cluster installs depending on the version of
SQL 2000 used. Check your i386 folder creation date on the SQL 2000 CD. If
it is in the year 2000, you need to obtain new media. If it is in 2003, we
will need to keep looking for the problem.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP




[quoted text, click to view]
Re: SQL Server Install of Named Instance on 2003 fails Chris
2/23/2006 12:20:18 PM
Geoff,

It worked....I can't tell you how happy I am right now. thanks again
for your help. I don't now how I would have found that one.

Chris
Re: SQL Server Install of Named Instance on 2003 fails Geoff N. Hiten
2/23/2006 12:46:49 PM
FYI, the fixed version is sometimes called SQL 2000a. All currently shipped
media is the updated version. The only change is that the slammer worm
vulnerability has been removed by replacing a single dll. Windows 2003
looks for the fix and won't allow SQL to activate its network libraries
unless it is patched, hence the need for the named pipes alias during setup.
Sometimes Windows 2003 can be over-eager and not allow installs at all from
the older media. And yes, this was a real hard one to track down.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP




[quoted text, click to view]

Re: SQL Server Install of Named Instance on 2003 fails Geoff N. Hiten
2/23/2006 3:37:26 PM
You are welcome.

--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP


[quoted text, click to view]

AddThis Social Bookmark Button