SQL Server State Unknown

Question

SQL Server State Unknown

James Hibbert

SSC Rookie

Points: 40
More actions
August 22, 2005 at 10:00 pm

#102725

We recently built a new Active\Passive SQL2000 Cluster. After registering the server in my enterprise manager I find that the state (circle with green arrow) never shows unless I connect. It's always just a white circle. Also, after connecting, the SQL Agent state never appears either.
Anyone have any ideas on what the problem might be?
Thanks!
Jim

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Eoin The Forge SSCrazy Points: 2932 More actions · Answer 1

In EM. Right click on the relevant server. Select edit sql server registration properties. Then check the "Display SQL server state in console" box.

James Hibbert SSC Rookie Points: 40 More actions · Answer 2

Thanks, but I already know that. That's not the problem.

Thanks!

icata Hall of Fame Points: 3176 More actions · Answer 3

I am experiencing the same issue with some of the servers that I am taking care.

I guess is that is has something to do with the network latency/DNS/AD configuration.

James Hibbert SSC Rookie Points: 40 More actions · Answer 4

That's what I'm wondering, but we have other SQL Servers that are showing status just fine both stand-alone and clustered. This IS the first one we've clustered on Windows 2003 Advanced Server (the others are 2000). Could something about 2003 be the culprit perhaps?

Thanks!

icata Hall of Fame Points: 3176 More actions · Answer 5

I have this annoyance with a Win 2000 cluster (SQL2kSP3a) and a Win 2003 (SQL2kSP3a)

Eddy White Valued Member Points: 57 More actions · Answer 6

I have a similar issue.

Win 2003 EE SQL2KSP3a with the 818 security fix

Clustering is managed by Veritas Clustering for Windows v 4.3.

I have found that they will show up when the default instance is on the same node.

For example, I have 4 instances; A, B, C and D.

By design A is primary on Node1 and B, C and D are on Node 2.

Instance A (a named instance) shows not started and the other 3 show up no problem.

When I switch the default instance (let's call it D) to Node 1, Instance A and D show up as started and the other two show as not started.

It seems to me that EM is looking for the default instance and is enumerating off of that instead of using the entry in the Network Client Utility that is required for clustered instances (Microsoft or not).

icata Hall of Fame Points: 3176 More actions · Answer 7

I am not familiar with Veritas Clustering but this is happening to me for clustered and unclustered servers, win2k or win 2k3, all default installations.