Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Faulty node in SQL 2000 Clusting? Expand / Collapse
Author
Message
Posted Tuesday, November 17, 2009 9:18 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 9:33 AM
Points: 2,317, Visits: 855
Here we have numerous (7+) SQL 2000 Enterprise 8.0.2040 instances running on a 2-node cluster (Win2003 Server SP2) that are load balanced when ever possible. This has been working fine, however recently I have found that if a number of SQL instances are running on one of those nodes (say node 2) then I struggle to connect to them (timeout error), via MS in 2000/5/8. Sometimes I do eventually connect however I am not presented with any SQL Server Agent info.

I have checked event viewer and not spotted anything untowards, however have spotted this error:

[sqsrvres] ODBC sqldriverconnect failed

[sqsrvres] checkODBCConnectError: sqlstate = HYT00; native error = 0; message = [Microsoft][ODBC SQL Server Driver]Timeout expired

I have checked the registry settings for all SQL instances in case this is a tcp/ip or named pipes issue but all details are the same. Has anyone experienced this type of issue before? When I move any SQL instance back to say node 1 everything works fine. Very odd.


Thanks In Advance,

qh




SQL 2K acts like a spoilt child - you need to coax it round with lollipops.
Post #820167
Posted Wednesday, November 18, 2009 3:15 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 9:33 AM
Points: 2,317, Visits: 855
Solved this one ourselves. Didn't realise that there were different service accounts runnning on the SQL instances (old system) and the instances with a newer account worked fine on both nodes, however ones with an older service account with and older domain has lost trust with one of the nodes.

Rebooted that node, reset the PDC and everything is peachy.



qh


SQL 2K acts like a spoilt child - you need to coax it round with lollipops.
Post #820670
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse