<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 7,2000
»
In The Enterprise
»
Faulty node in SQL 2000 Clusting?
Faulty node in SQL 2000 Clusting?
Rate Topic
Display Mode
Topic Options
Author
Message
quackhandle1975
quackhandle1975
Posted Tuesday, November 17, 2009 9:18 AM
SSCommitted
Group: General Forum Members
Last Login: Thursday, May 16, 2013 8:24 AM
Points: 1,610,
Visits: 590
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
quackhandle1975
quackhandle1975
Posted Wednesday, November 18, 2009 3:15 AM
SSCommitted
Group: General Forum Members
Last Login: Thursday, May 16, 2013 8:24 AM
Points: 1,610,
Visits: 590
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 »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
