Error with SQL Agent & SQL Server Logs

  • Hi Experts,

    I am not able to start SQL Agent.When checked i also find that when clicking on SQL Server Logs folder its throwing an error.

    A severe error occurred on the current command. The results, if any, should be discarded. (.Net SqlClient Data Provider)

    Please Help

    TIA

  • Are there any errors in the Windows Event Logs?

    What account is the SQL Server Agent running under?

    I doubt I'll have the answer, but these are some things I'd check.

  • Have you tried retrieving the error logs from the \LOG directory using a text exitor?

    What does it shows in the current error log?


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • Jack Corbett (12/15/2009)


    Are there any errors in the Windows Event Logs?

    What account is the SQL Server Agent running under?

    I doubt I'll have the answer, but these are some things I'd check.

    1.SQLServerAgent could not be started (reason: Unable to connect to server 'CY1160'; SQLServerAgent cannot start).

    2.Agent running under local system account

  • Jack Corbett (12/15/2009)


    Are there any errors in the Windows Event Logs?

    What account is the SQL Server Agent running under?

    I doubt I'll have the answer, but these are some things I'd check.

    1.SQLServerAgent could not be started (reason: Unable to connect to server 'CY1160'; SQLServerAgent cannot start).

    2.Agent running under local system account

  • Bru Medishetty (12/15/2009)


    Have you tried retrieving the error logs from the \LOG directory using a text exitor?

    What does it shows in the current error log?

    2009-12-15 19:27:19 - ! [298] SQLServer Error: 21, Encryption not supported on the client. [SQLSTATE 08001]

    2009-12-15 19:27:19 - ! [298] SQLServer Error: 21, Client unable to establish connection [SQLSTATE 08001]

    2009-12-15 19:27:19 - ! [165] ODBC Error: 0, 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]

    2009-12-15 19:27:19 - ! [000] Unable to connect to server 'CY1160'; SQLServerAgent cannot start

    2009-12-15 19:27:19 - ! [298] SQLServer Error: 21, Encryption not supported on the client. [SQLSTATE 08001]

    2009-12-15 19:27:19 - ! [298] SQLServer Error: 21, Client unable to establish connection [SQLSTATE 08001]

    2009-12-15 19:27:19 - ! [165] ODBC Error: 0, 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]

    2009-12-15 19:27:19 - ! [382] Logon to server 'CY1160' failed (DisableAgentXPs)

    2009-12-15 19:27:20 - ? [098] SQLServerAgent terminated (normally)

  • It is because the server is not able to connect properly. Check the port number and the servername (should match with My Computer --> properties --> Network Identification--> Name) in the SQL network utility. If the agent is running under Local System and the same account is removed from the logins of SQL server then make SQL Server Agent to run under some login having proper permissions.

    Thanks

  • Is the SQL Server accepting connections actively when you have this issue?


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • Is the SQL Server service running?

  • Jack Corbett (12/16/2009)


    Is the SQL Server service running?

    Good Question Jack .


    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • SQL Server is up and running ..

    No issues with connections

  • I have faced a similar issue when SQL Service was started with a different account.

    Is SQL Service running under same Local admin account. If nt start under it and try starting the agent.

  • 2009-12-15 19:27:19 - ! [165] ODBC Error: 0, 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]

    2009-12-15 19:27:19 - ! [165] ODBC Error: 0, 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]

    2 (normally)

    Is your SQL Server enables to allow remote connections under Connections? Is it a default instance? If not, have you got SQL Browser enabled for the service?

    Have you gone through surface area configuration settings and check the remote connections protocol?

    Have you gone through this article?

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277[\url]

  • I checked SQL Native Client configuration under SQL Server Configuration Manager and found that all the protocols are missing and if i right clicked and selected properties and getting nothing.

    Please find the attachment.

Viewing 14 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic. Login to reply