Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

No able to start SQL server agent Expand / Collapse
Author
Message
Posted Tuesday, December 21, 2010 3:55 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Sunday, November 24, 2013 12:37 PM
Points: 85, Visits: 159
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
Post #1038011
Posted Tuesday, December 21, 2010 8:05 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, May 15, 2014 5:11 PM
Points: 6,067, Visits: 5,283
Give this a go:
EXEC sp_configure 'show advanced options', 1
RECONFIGURE
GO

EXEC sp_configure 'Agent XPs', 1
RECONFIGURE
GO

CEWII
Post #1038034
Posted Wednesday, December 22, 2010 7:23 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Sunday, November 24, 2013 12:37 PM
Points: 85, Visits: 159
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]
Post #1038266
Posted Wednesday, December 22, 2010 7:57 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Friday, August 22, 2014 10:18 AM
Points: 514, Visits: 1,727
under what service account does the Agent try to start?
Post #1038290
Posted Wednesday, December 22, 2010 8:25 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Sunday, November 24, 2013 12:37 PM
Points: 85, Visits: 159
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!!
Post #1038297
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse