all groups > sql server connect > march 2007 >
You're in the

sql server connect

group:

Cannot connect to SQL Server 2005


Cannot connect to SQL Server 2005 CRush
3/21/2007 7:50:05 AM
sql server connect: I am receiving this error while trying to connect to a SQL Server 2005
instance.

"An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance
Specified) (Microsoft SQL Server, Error: -1)"

The SQL Server does allow remote connections - why would this error be
coming up?
Re: Cannot connect to SQL Server 2005 Rick Byham, (MSFT)
3/21/2007 9:30:13 AM
This is a very general error meaning the tool can't find a server instance
of that name. Other possible reasons are that the SQL Server Browser Service
is not running, or a firewall is blocking you.
Try running through the short connectivity tutorial at
http://msdn2.microsoft.com/en-us/library/ms345318.aspx
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

[quoted text, click to view]
Re: Cannot connect to SQL Server 2005 CRush
3/21/2007 11:17:08 AM
Rick,

This is a problem that occurs sporadically during the day. SQL Server
Browser is running. I am running SQL Server on a Virtural Server. I have
noticed today that when the problem occurs the cpu for the Virtual Server and
the Stand alone Server are both running at 100%. We currently have 4 Virtual
Servers running with 3 of them running SQL Server 2005 on the same Stand
alone Server.

[quoted text, click to view]
Re: Cannot connect to SQL Server 2005 Rick Byham, (MSFT)
3/22/2007 9:02:38 AM
Your error is probably a symptom of the 100% CPU. The "An error has occurred
while establishing a connection ..." error is very general and indicates
that the client tools can't find the SQL Server that you are asking for. In
this case, it could be that the network isn't responding because of the 100%
CPU, or the SQL Server Browser Service can't respond because of the 100%
CPU. Of course this just moves the question to why do you have 100% CPU
usage. Solve the 100% CPU, and I bet the connectivity problem will go away.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

[quoted text, click to view]
Re: Cannot connect to SQL Server 2005 William (Bill) Vaughn
3/22/2007 11:07:46 AM
I agree. See if Microsoft OneCare Defender is chewing up all of your
processor time... ;)

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

[quoted text, click to view]

AddThis Social Bookmark Button