dbTalk Databases Forums  

sql2k on W2003 cluster issues

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering


Discuss sql2k on W2003 cluster issues in the microsoft.public.sqlserver.clustering forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Hans
 
Posts: n/a

Default sql2k on W2003 cluster issues - 06-01-2004 , 02:55 PM






Hi,

we have installed sql2K on a W2003 cluster and ran into a few issues.

First one was during installation : if we would chose processor licensing,
setup failed. We have two Compaq/HP servers with each 4 Xeons 2GHz and it
made no difference whether we indicated 4 (real) processors or 8
(hyperthreaded). We then tried client licensing and that worked perfectly.
We still would like to go to processor licensing though so any clues are
appreciated.

Second issue came later. We had already created a default instance and a
named instance which are running perfectly on node A. Last weekend we setup
a second named instance and it was running perfectly on node B until today.
I wanted to stop and restart it to kill some ghost connections. When I
restarted, it failed. The eventlog showed it started up perfectly, opening
and analyzing all databases but just after it started looking for client
connections, we got error messages :

[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.

We found out that the Named Pipes name in the registry was wrong and
corrected it (Server Network Utility doesn't always show the correct info
when a server is down, sometimes it shows the info for the next server in
the list).
However restarting did not work. The trick was to move the server to node
A, restart node B and move the server back to B. We now have to do this
every time.
Any ideas?

thanks

hans

Reply With Quote
  #2  
Old   
Rand Boyd [MSFT]
 
Posts: n/a

Default RE: sql2k on W2003 cluster issues - 06-02-2004 , 08:34 AM






Your first problem may be related to the following article:

FIX: SQL Server Setup May Fail If You Select Per Processor Licensing Mode
http://support.microsoft.com/?id=273769


The second one appears to be that the cluster service is having a problem
connecting to SQL Server to verify that it is running. I am not sure why it
is occurring, but you may be able to workaround the problem by creating an
alias on the node where it fails pointing to the virtual server name and
using the ip address as the server name.

Rand
This posting is provided "as is" with no warranties and confers no rights.


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.