I agree. See if Microsoft OneCare Defender is chewing up all of your
processor time... ;)
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
-----------------------------------------------------------------------------------------------------------------------
"Rick Byham, (MSFT)" <rickbyh@REDMOND.CORP.MICROSOFT.COM> wrote in message
news:70B1ACC0-026C-46AF-B85F-E8CCECC56041@microsoft.com...
> 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.
>
> "CRush" <CRush@discussions.microsoft.com> wrote in message
> news:DDB7A36A-3B49-49D4-81DF-4C1FEF24ED21@microsoft.com...
>> 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.
>>
>> "Rick Byham, (MSFT)" wrote:
>>
>>> 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.
>>>
>>> "CRush" <CRush@discussions.microsoft.com> wrote in message
>>> news:90D37EAC-DBE0-449D-A9C0-D39033A7CB91@microsoft.com...
>>> >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?
>>> >
>>>
>