SQL Agent crash with Red X Mark, and then NM down

From DocWiki

Jump to: navigation, search

SQL Agent crash with Red X Mark, and then NM down

Problem Summary SQL Agent crash with Red X Mark, and then NM down

From the SQL Server log:

2009-10-21 09:38:11 - ! [298] SQLServer Error: 6, Specified SQL server not found. [SQLSTATE 08001] 2009-10-21 09:38:11 - ! [298] SQLServer Error: 11004, ConnectionOpen (Connect()..[SQLSTATE 01000] 2009-10-21 09:38:11 - ! [000] Unable to connect to server '<hostname>\CRSSQL'; SQLServerAgent cannot start 2009-10-21 09:38:12 - ? [098] SQLServerAgent terminated (normally)

It is trying to connect to SQL Server instance on the local server and the server is in the workgroup. It is using windows authentication to connect to SQL Server and getting the following error. Error: SQLServer Error: 18452, Login failed for user '(null)'. Root cause: Not associated with a trusted SQL Server connection Not able to start SQL Server agent.

Error Message Error: 18452, Login failed for user '(null)'. Root cause: Not associated

with a trusted SQL Server connection

Possible Cause Client network library was choosing TCP/IP provider.

Detail here: http://blogs.msdn.com/sql_protocols/archive/2005/10/19/482782.aspx

Recommended Action Open start->MS SQL Server->Client Network Utility

OR

Start > Run > cliconfg.exe [On the machines where sql server is not installed, so for MSDE setup you can use this.]

Run the command cliconfg.exe, it will launch SQL Server Client Network Utility click on Aliases tab if there is an alias with IP address modify it to use host name and ensure it is using TCP/IP. If you see authentication issues in the SQL Agent log instead of connection issue try using Named Pipes, go to General tab add Named pipes and move it up the order and modify the alias to use Named Pipes.

Release Release 7.0, Release 5.0
Associated CDETS # None

Rating: 0.0/5 (0 votes cast)

Personal tools