sql server connect: SQL Server 2000 stops responding -- sql server connect

You're in the

sql server connect

group:

SQL Server 2000 stops responding

Cathy Boehm
3/29/2005 2:29:02 PM

sql server connect: It appears to be up and running, when you expand in Enterprise Manager on a
client side, I am getting:

A connection could not be established to "Name of the server".
Reason: General network error. Check your network documentation.
ConnectionOpen (PreLoginHandshake())..

Please verify SQL Server is running and check your SQL Server registration
properties (by right-clicking on the "Name of the server" node) and try again.
This message is getting generated by SQL Server Enterprise Manager.
The question is what makes this message to generate.
Any ideas would be greatly appreciated.

--

RE: SQL Server 2000 stops responding

garyw NO[at]SPAM online.microsoft.com
4/4/2005 3:35:51 PM

Hi Cathy,

You may be able to work around this issue by increasing the timeout setting
for Enterprise Manager. Select Tools-Options-Advance and increase the
login timeout setting. By default, it is set to 4 seconds. If you have an
issue with network latency, this might do the job for you.

Thank you.

Gary Whitley

This posting is provided "AS IS" with no warranties, and confers no rights.

RE: SQL Server 2000 stops responding

Cathy Boehm
4/5/2005 2:25:02 PM

Thanks Gary,
I need to clarify however that this SQL Server was installed on VMware,
which changed significantly from the way they used to install servers - which
was on one physical hard drive.
Now I have master is on F:, some other databases on other drives.
Please let me know if you know anything about VMWare and SQL Server
functioning on it.
Thanks

[quoted text, click to view]

RE: SQL Server 2000 stops responding

garyw NO[at]SPAM online.microsoft.com
4/6/2005 8:19:28 PM

Hi,

I have not personally tested SQL Server in a VMWare configuration.
However, the fact you have the Master database on drive 'F' and your user
databases on another drive letter should be OK. You can specify the
database file locations on any drive letter as long as they are local on
the server. In a virtual machine configuration, the drives are considered
local to the system.

You really have two separate issues at play I believe. If there is a
problem with SQL Server accessing a database file on any drive letter, SQL
will be unable to recover that database and will mark it as suspect. The
connectivity issue should have no relationship to the database drive
location.

Please let me know if this information helps.

Thanks.

Gary

This posting is provided "AS IS" with no warranties, and confers no rights.

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server connect group.

View Other Months
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007

home · blog · groups

Questions? Comments? Contact the dn