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 |