getting worning( jobs are failing)

  • Hi,

    I am getting following error. I can access databases. I have no network issues. I think, some changed the user name and password of the job owner. Am I correct or not? I checked, they are not running under Administrator credentials and the jobs are not running under SQLAgent credentials. Please advice me.

    2008-10-13 08:32:24 - ! [298] SQLServer Error: 17, SQL Server does not exist or access denied. [SQLSTATE 08001]

    2008-10-13 08:32:24 - ! [298] SQLServer Error: 2, ConnectionOpen (Connect()). [SQLSTATE 01000]

    2008-10-13 08:32:24 - ! [382] Logon to server '(local)' failed (JobManager)

    2008-10-13 08:32:56 - ! [298] SQLServer Error: 17, SQL Server does not exist or access denied. [SQLSTATE 08001]

    2008-10-13 08:32:56 - ! [298] SQLServer Error: 2, ConnectionOpen (Connect()). [SQLSTATE 01000]

    2008-10-13 08:32:56 - ! [382] Logon to server '(local)' failed (ConnAttemptCachableOp)

    2008-10-13 08:33:27 - ! [298] SQLServer Error: 17, SQL Server does not exist or access denied. [SQLSTATE 08001]

    2008-10-13 08:33:27 - ! [298] SQLServer Error: 2, ConnectionOpen (Connect()). [SQLSTATE 01000]

    2008-10-13 08:33:27 - ! [382] Logon to server '(local)' failed (ConnAttemptCachableOp)

    Thanks in advance.

    BMR

  • How are the jobs running? You might check the client configuration utility for the default protocols.

  • Thanks for reply. Till yesterday all the job were running fine. Suddenly, I am getting the worning and all the jobs are failed.

    I am getting following error in EventLog

    Message

    SQL Server Scheduled Job 'XYZ_Log_bck' (0x111F9E8D42F18F4087E13E967ADCA64C) - Status: Failed - Invoked on: 2008-10-13 10:30:00 - Message: The job failed. Unable to determine if the owner (ABCDOMAIN\rem) of job XYZ_Log_bck has server access (reason: Unable to connect to server - check SQL Server and SQL Server Agent errorlogs).

  • That happened to a few of the servers I administer recently. It turned out to be a problem with DNS rather than SQL Server. Have you had a word with your network guys to see if anything's changed/broken?

Viewing 4 posts - 1 through 3 (of 3 total)

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