August 31, 2005 at 3:36 pm
Hello Everyone,
We're trying to set up an active/active SQL 2K (32-bit) cluster on a Windows 2K3 64-bit environment. I was able to successfully setup the first node (Node1). When I install SQL on the second node (Node2\Node2), its erroring out with a lot ODBC unable to connect messages. Below is a sample of the message:
The description for Event ID ( 17052 ) in Source ( MSSQL$CL1DBS07 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: [sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 35; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Has anyone seen this?
Thank you in advance for your assistance.
September 1, 2005 at 1:36 am
Hi, yeh just done a cluster install but 32bit sql on 32bit o/s so your problem may be different.
I had heaps of issues with creation of the second instance. Firstly ensure all failed installs have been cleanly removed. I found that the failed instance creation left a mess on both nodes and I needed to cleanup using a number of things. First rerun install from CD and choose remove option, this may work but in my case the uninstall also failed, and a local instance of sql server was left on each node. Used add remove prgms on each node to clear out the local instances that the failed cluster install had left. Reboot both nodes and basically ensure no trace of the instance exists.
I had two issues that may be causing you the same grief.
1. Ensure that you create a named pipe alias on both nodes via the client network utility. The installer needs the named pipe to exist for named instances. Yeh I know the first instance you created didn't need the alias so why does the second, I have no idea but it just does.
2. I would try a reinstall after performing 1. It may still fail and then you need to do the cleanup again. Hey if it works after creating Aliases as per 1. then great. Else
3. I had a weird issue which caused the same error you are experiencing for the second instance install that finally turned out to be a permissions issue. I fought this one and gave in against my desire to follow all best practices and finally needed to supply the following for the account that the sql /agent services will run under. The account must be a domain account and it needed to be a local admin.
Hope this helps
Derek
September 1, 2005 at 10:38 am
Thanks for your response Derek. I just want to make sure that I got it rigt before I proceed again.
My first node that I did a successful install is called DBS06 and the one that's failing I'm going call DBS07\DBS07. So, if I understood you correctly, I'm going to set up a named pipe alias in the second node pointing to the first node (DBS06).
September 1, 2005 at 10:12 pm
Hmm ok lets try to explain. Your first install was on node1 (dbs06) first what did you call the sql virtual name? Lets say it was 'sql1' and the instance name was 'instance001' for example. During the sql install on dbs06 you would have specified the other node (dbs07) as part of the cluster (the node that sql server would failover to if required).
Ok if I have got that correct so far, now for the second install. You would now be installing sql server on dbs07, again lets say the sql virtual name is 'sql2' and the instance name is 'Instance002'.
Remember that you cannot use default insances on both nodes because in the event of a failover you would have the potential of two default instances trying to run on the same as the failover node and this is not allowed.
ok so prior to the install on dbs07 you create a named pipe alias on both nodes via the client network utility and they point to the second sql server instance you are yet to create, ie
sql2\instance002
September 1, 2005 at 10:35 pm
That cleared it up for me. I'll give that a shot and will let you know. One other mistake I made was I installed SQL on the first node and then installed SQL on the second node. From researching, it looks like I should have installed SQL and SP4 before I went to node2.
One other question for you, can I have default instance on node1 (sql1) and named instance on the node2 (sql2\instance1)? That way you won't have two default instances. I'm assuming the answer is yes.
Thank you so much for your assistance.
September 2, 2005 at 1:29 am
Yeh unlike active /passive which applies the service pack to both nodes automatically.
Yes default on one and named on the other is fine, basically so long as when failover occurs the instances are unique on the node you are ok. Also make sure you have considered load, because during failover the single node must have sufficient memory for all instances to run.
Derek
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply