The SQL Server \\Servername is not know to be running.

[lpmlaine]

The SQL Server \\ is not know to be running. Do you still want to connect?

So I get this message when I connect to a server in EM. I know this message is just informational, but here's my question.
I have 6 servers registered in my EM console. I get the "not know to be ruuning" error whenever I connect to 5 of them. However, one of the servers lets me connect without first returning the message "The SQL Server \\ is not know to be running. Do you still want to connect? "
I have looked at all the connect/Registration properties to compare the 1 that automatically connects to the others that do not.
I can't figure out why this is happening. Now granted, it's not like it is hindering me from connecting or anything. But it is really bugging me that I can't figure out why this is happening.
Does anyone know?

Thanks in advance.

 

[tlbroadbent]

Open the registration properties of each server. Near the bottom, you'll see "Show SQL Server state in console." It is probably checked on for the one server and off for the other five.

If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:

http://tlbroadbent.home.attbi.com/sql/sql_articles.htm

 

[lpmlaine]

I checked all the registration properties and they were all the same. Even the "Display SQL Server State in Console".
So maybe I need to clarify what I am asking:
It's not that the state isn't displayed, it is that only one instance will automatically connect. All the others prompt me with the "SQL Server \\ not known..." message.
I looked in BOL, but couldn't find anything helpful.

Thanks

 

[Flloyd]

It seems to me that I had this issue at one time.

Try choosing Tools/Options from the SEM menu, and on the Advanced tab, increase the value for login time-out seconds (the default is 4). It could be that there is no response from the server(s) within the 4 second limit due to misc. network factors.

Lloyd Freiday

 

[tlbroadbent]

lpmlaine,

I understood the situation as you explained it and I provided one possible explanation. If the option to "Show SQL Server state in console" is off, then EM will not poll the server and the message you get will be displayed.

Is EM displaying the message even though it shows the status as running? Is it possible that you are clicking on a server before EM has completed polling the servers?

If EM has already polled the server and knows the state, then it should not display the message you are getting. Perhaps there is a bug in EM. Which version and service pack of SQL Server are you running?

Flloyd,

If the timeout value is too short, EM displays a timeout expired message which differs from the message lpmlaine is getting. At least, this is the case with SQL Server 2000, SP3.

If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:

http://tlbroadbent.home.attbi.com/sql/sql_articles.htm