SQL server is not known to be running

Question

Post reply

SQL server is not known to be running

Sang Nahm

SSC-Addicted

Points: 426
More actions
August 13, 2003 at 9:52 am

#83042

Hi,
I am running SQL Server 7.00.623 on Windows NT 4.0 with Serivce Pack 6.
The MSSQLServer and SQLServerAgent services are running fine, and log files both agent and errorlogs do not indicate any malfunctions.
When I try to connect to the server in EM, I get the following message:
The SQL Server \\servername is not known to be running. Are you sure you wish to connect?
Any idea on this please?
I am gonna run sqldiag and do more trouble shooting...
Much thanks in advance.
Sang Nahm

Viewing 12 posts - 1 through 11 (of 11 total)

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

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 1

Can you ping the server? Try to access with IP address.

Sang Nahm SSC-Addicted Points: 426 More actions · Answer 2

Hi,

It turned out that the security patch we applied yesterday caused the problem. We tested it by removing the patch, and the server was running fine.

Bad thing is that we need to to apply the patch still.

Thank you so much for your reply.

quote:
Can you ping the server? Try to access with IP address.

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 3

Allen Cui-55137

SSC Guru

Points: 51650

August 13, 2003 at 1:21 pm

#469809

Which secuirty patch?

Sang Nahm SSC-Addicted Points: 426 More actions · Answer 4

It is MS03-026 security patch.

quote:
Which secuirty patch?

gbn SSCertifiable Points: 6429 More actions · Answer 5

Have you installed any Service Packs for SQL 7?

Our latest verison of SQL 7, SP4 is 7.00.1063

SP3 is 7.00.961

You'll probably have to apply the SP before the HF

Cheers

Shawn

kay SSCommitted Points: 1518 More actions · Answer 6

quote:
When I try to connect to the server in EM, I get the following message:
The SQL Server \\servername is not known to be running. Are you sure you wish to connect?

I run the same configuration and get this message frequently. However, this doesn't stop EM from connecting. Eeverything works fine. Is this the case for you, too ? Do you just get this message or do you really have trouble connecting ?

We never found out why this message pops up, but since things work fine anyway, we stopped investigating. Would be nice to get the answer in this forum....

AJ Ahrens SSC-Insane Points: 20676 More actions · Answer 7

We also get this message from EM. However, in our case I think it is easily explained:

we are still in a token-ring environment and use TCP/IP as the connection type. This doesn't return the state in a quick enough manner to the slower PC's to allow EM to know that everything is fine. Once you hit connect (sometimes several times) everything should be ok.

This is an issue ONLY with EM. QA handles this connection checking differently and only gives you connect/couldn't connect.

I think I remember reading (on this site) a script that does polling to check to see which servers are currently runnning as SQL servers. Might be something to research if you need to.

AJ Ahrens

SQL DBA

Revenue Assurance Management - AT&T

Good Hunting!

AJ Ahrens

webmaster@kritter.net

kay SSCommitted Points: 1518 More actions · Answer 8

quote:
This doesn't return the state in a quick enough manner to the slower PC's to allow EM to know that everything is fine.

Well, in my case EM and SQL Server run on the same machine, and I still get the message "The SQL Server is not known to be running". At least in this case it seems unlikely the message is linked to sime time-out problem, what do you think ?

bjkrame Mr or Mrs. 500 Points: 572 More actions · Answer 9

I would think it would be a time out issue. This has occurred to me when our SQL server was outside of our existing firewall. I was able to solve this message in one instance by increasing the amount of time in the login time-out (seconds). From EM - Tools options advanced tab.

worth a shot...

Brian

BK

Sang Nahm SSC-Addicted Points: 426 More actions · Answer 10

When we reapplied the patch, the server stopped working again; therefore, I will take Shawn's advise and apply the service pack.

Will keep you posted.

kay SSCommitted Points: 1518 More actions · Answer 11

quote:
I was able to solve this message in one instance by increasing the amount of time in the login time-out (seconds)

Hmmmm .... I tried to increase all time-out values I could find to ridiculously large values, but still the message pops up immediately when trying to connect to the Server in EM. Once the message is confirmed with "OK", the Server is immediately connected and everything is fine. Don't know why EM is complainig about it.