Re: Failover problems on 2 active/active SQK 2k clusters on Windows 2003

I did not do anything in particular with the Server Network Utility, but if
I open it on the nodes in question and select the instance names, then click
TCP/IP under enabled protocols and properties, it shows the correct ports
for each instance.

Do I need to configure anything more there?

Any suggestions on how I would troubleshoot the SQL Browser?

Thanks for the suggestions!

--john

"Geoff N. Hiten" <SQLCraftsman@xxxxxxxxx> wrote in message
news:%23AP9wMhPGHA.3896@xxxxxxxxxxxxxxxxxxxxxxx
Possibly a name resolution error. Did you use the Server Network Utility
to lock the port numbers for the named instances? That helps keep
consistency during failover. You may also be having a problem with the
SQL Browser, the listener service on port 1434 that resolves named
instance requests to the actual port number.

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




"John Wart, jr" <johnwartjr@xxxxxxxxxxxxxx> wrote in message
news:OYRwNxgPGHA.2472@xxxxxxxxxxxxxxxxxxxxxxx
Greetings

I recently deployed 2 new SQL clusters for our web environments.

We have a legacy cluster that runs windows 2000 server and has
active/active clustering with 2 instances of SQL Server. It works well
and has worked well for years, but we started to outgrow the hardware, so
we acquired hardware and software to build 2 clusters to replace the
original.

Our new clusters are having a strange problem though.

In both cases, we have active/active clustering with 2 instances of SQL.
The first cluster has instance names DBSERVER1 and DBSERVER2\DBSERVER2,
and the second cluster has instance names DBSERVER3 and
DBSERVER4\DBSERVER4.

The default named instances (DBSERVER1 and DBSERVER3) work just fine on
both clusters on either Win2k3 node, fail over and work seamlessly.
However, the named instances (DBSERVER2\DBSERVER2 and
DBSERVER4\DBSERVER4) have odd problems when they fail over. SQL Server
starts up perfectly on the node, I can use enterprise manager to browse
through the tables, etc, but the web apps give an error - 'SQL Server
does not exist or access denied'.

Any ideas? I've wondered if this might have something to do with aliases,
but am not certain. My experience with SQL is somewhat limited and I
followed advice from several books when I deployed these clusters - but
it's possible something was omitted in the procedure that was important.

Thanks!

--john









.

Relevant Pages