SQL2000 Cluster Problems

[pshankland]

Hi,

I have got a Windows 2000 Cluster installed on an IBM FAStT200 SAN. I have got Microsoft SQL2000 Enterprise Edition installed on the two nodes and have called these RPL-BMW and RPL-AUDI.

I have had to changed the IP Addresses of these two SQL Installs from ***.***.1.31 and ***.***.1.32 to ***.***.1.29 and ***.***.1.30. RPL-BMW worked fine after I re-started the Cluster Group. Unfortunatly, when I try to restart the RPL-AUDI server group I get a mixture of the following errors:

[sqsrvres] ODBC sqldriverconnect failed

and

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

and

[sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 43; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).

Can anyone shed any light on this problem?? I have put the IP address of RPL-AUDI back to what it was and I still get the same error.

Thanks.

 

[SQLBill]

Did RPL-AUDI work BEFORE the IP change?

Are RPL-AUDI and RPL-BMW the names of the NODES or the names of the SQL Server instances?

Is the cluster ACTIVE/ACTIVE or ACTIVE/PASSIVE?

-SQLBill

 

[pshankland]

RPL-AUDI did work before the IP change.

RPL-AUDI and RPL-BMW are the names of the SQL Server Instances.

The Cluster is ACTIVE/ACTIVE.

Thanks.

 

[SQLBill]

It looks like the IP change didn't get made in ODBC.

Go to Start>Control Panel>Administrative Tools>Data Source (ODBC)

Check all three DSN tabs (User, System, and File). On one or more of them you will find an entry for SQL Server. Select that and click on CONFIGURE. Go through the steps and check the information in two places. The initial window lets you enter either the name or the ip for the server. Then in the window where you set authentication, there will be a button for Client Configuration. Click that and make sure it has the correct information.

If those places have the Server Name and not the IP address, change them to IP address. It could be that DSN name resolution isn't set up or doesn't have your new IP addresses mapped to those names.

-SQLBill

 

[pshankland]

Have checked the ODBC settings on both nodes and get the following information -->

User DNS
========
Name = MQIS
Driver = SQL Server

System DNS
==========
Name = LocalServer
Driver = SQL Server

This is the same on both nodes. I have got RPL-BMW SQL Instance running on one of the nodes so if I edit the information above how do I know which SQL Instance it is changing??

Thanks.

 

[SQLBill]

As I said:

For each one click on CONFIGURE. Go through the steps and check the information in two places. The initial window lets you enter either the name or the ip for the server. Then in the window where you set authentication, there will be a button for Client Configuration. Click that and make sure it has the correct information.


But you need to go through the ODBC configuration windows to see what the settings are. If IPs are entered for the server information, you will need to put the correct IPs. But if Server Names are used, then you have a problem with DNS (Domain Naming Service) and you need to get your admin to register the names with the new IPs.

-SQLBill