Could be a lot of things. Is this a new problem? Are Named Pipes actually
enabled? Do you have a client that's trying to connect via NP when they
should be connecting via TCP/IP? Check the settings in Configuration
Manager, both for the agent and for services, and check any aliases in use.

A little more info would be helpful. Good luck with this.

Carolyn J.


---------- Original Message -----------
From: "Norm Milan " <mssqldba-ezmlmshield-x59152315.[Email address protected]
To: "LazyDBA Discussion" <[Email address protected]
Sent: Tue, 27 Nov 2007 13:39:42 -0700
Subject: Agent in a pickle

> Can anyone offer advice on this?:
>
> 2007-11-27 13:27:06 - ! [298] SQLServer Error: 2, Named Pipes Provider:
> Could not open a connection to SQL Server [2]. [SQLSTATE 08001]
> 2007-11-27 13:27:06 - ! [165] ODBC Error: 0, Login timeout expired
> [SQLSTATE HYT00]
>
> 2007-11-27 13:27:06 - ! [298] SQLServer Error: 2, 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. [SQLSTATE
> 08001]
> 2007-11-27 13:27:06 - ! [000] Unable to connect to server '(local)';
> SQLServerAgent cannot start
>
> Thanks in advance....
>
> n
>
> ---------------------------------------------------------------------
> TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
> To post a dba job: http://jobs.lazydba.com
> To subscribe : http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
------- End of Original Message -------


MS Sql Server LazyDBA home page