SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Faulty node in SQL 2000 Clusting?


Faulty node in SQL 2000 Clusting?

Author
Message
quackhandle1975
quackhandle1975
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3261 Visits: 1240
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

Crazy

Who looks outside, dreams; who looks inside, awakes. – Carl Jung.
quackhandle1975
quackhandle1975
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3261 Visits: 1240
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.

:-P

qh

Who looks outside, dreams; who looks inside, awakes. – Carl Jung.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search