|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Wednesday, December 19, 2012 11:41 AM
Points: 83,
Visits: 156
|
|
I am gettening a "Unhadled excpetion" error , every time I try to start SQL server agent?? I am using remote desktop connection to server. I am not sure if this actually matter. I am connecting to the server with an admin account. The account role is set to be "sysadmin".
When I look at the "SQL server agent" error log, this is what I see:
Date,Source,Severity,Message 12/21/2010 17:45:09,,Information,[098] SQLServerAgent terminated (normally) 12/21/2010 17:45:09,,Error,[382] Logon to server 'EnergyData1' failed (DisableAgentXPs) 12/21/2010 17:45:09,,Error,[298] SQLServer Error: 5<c/> A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001] 12/21/2010 17:45:09,,Error,[165] ODBC Error: 0<c/> Login timeout expired [SQLSTATE HYT00] 12/21/2010 17:45:09,,Error,[298] SQLServer Error: 5<c/> Named Pipes Provider: Could not open a connection to SQL Server [5]. [SQLSTATE 08001] 12/21/2010 17:45:04,,Error,[000] Unable to connect to server 'EnergyData1'; SQLServerAgent cannot start 12/21/2010 17:45:04,,Error,[298] SQLServer Error: 5<c/> A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001] 12/21/2010 17:45:04,,Error,[165] ODBC Error: 0<c/> Login timeout expired [SQLSTATE HYT00] 12/21/2010 17:45:04,,Error,[298] SQLServer Error: 5<c/> Named P
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Wednesday, April 24, 2013 12:02 PM
Points: 5,854,
Visits: 4,873
|
|
Give this a go:
EXEC sp_configure 'show advanced options', 1 RECONFIGURE GO EXEC sp_configure 'Agent XPs', 1 RECONFIGURE GO CEWII
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Wednesday, December 19, 2012 11:41 AM
Points: 83,
Visits: 156
|
|
Date,Source,Severity,Message 12/22/2010 09:19:24,,Information,[098] SQLServerAgent terminated (normally) 12/22/2010 09:19:24,,Error,[382] Logon to server 'EnergyData1' failed (DisableAgentXPs) 12/22/2010 09:19:24,,Error,[298] SQLServer Error: 5<c/> A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001] 12/22/2010 09:19:24,,Error,[165] ODBC Error: 0<c/> Login timeout expired [SQLSTATE HYT00] 12/22/2010 09:19:24,,Error,[298] SQLServer Error: 5<c/> Named Pipes Provider: Could not open a connection to SQL Server [5]. [SQLSTATE 08001] 12/22/2010 09:19:19,,Error,[000] Unable to connect to server 'EnergyData1'; SQLServerAgent cannot start 12/22/2010 09:19:19,,Error,[298] SQLServer Error: 5<c/> A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. [SQLSTATE 08001] 12/22/2010 09:19:19,,Error,[165] ODBC Error: 0<c/> Login timeout expired [SQLSTATE HYT00] 12/22/2010 09:19:19,,Error,[298] SQLServer Error: 5<c/> Named Pipes Provider: Could not open a connection to SQL Server [5]. [SQLSTATE 08001]
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Yesterday @ 7:10 AM
Points: 485,
Visits: 1,568
|
|
under what service account does the Agent try to start?
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Wednesday, December 19, 2012 11:41 AM
Points: 83,
Visits: 156
|
|
I solved it.
Right click on Server Server Agent. Select "properties". Go to connection. Under "Alias local host server" I deleted whatever was there (I had server name there, which is the only instance), and left it empty!
Now SQL server agent starts fine!!
|
|
|
|