Jobs failing with event 208

Question

Jobs failing with event 208

philcart

SSC-Forever

Points: 47796
More actions
February 1, 2005 at 4:49 pm

#152341

For the past week we've been having some intermittant problems with one of our SQL servers. The box is running SQL 2000 SP3 on Windows Server 2003. The errors generally occur after-hours and there doesn't seem to be a pattern in the timing or server activity.
This was logged in the SQL Server Log,
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Also, the following error messages were logged in the SQL Agent Log,
SQLServer Error: 11, General network error. Check your network documentation. SQLSTATE 08001
SQLServer Error: 258, ConnectionOpen (PreLoginHandshake()). SQLSTATE 01000
Logon to server '(local)' failed (JobManager)
And multiple Event Log entries like this,
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/02/2005
Time: 9:08:38 PM
User: N/A
Computer: MELSQL1
Description:
SQL Server Scheduled Job 'WebSec2 - Retire Website Sessions' (0xA0B72F47E1E4FE42B683BF17566FDBEB) - Status: Failed - Invoked on: 2005-02-01 21:04:08 - Message: The job failed. Unable to determine if the owner (sa) of job WebSec2 - Retire Website Sessions has server access (reason: Unable to connect to server - check SQL Server and SQL Server Agent errorlogs).
Anyone come across this before? Any ideas on tracking down the cause?

--------------------
Colt 45 - the original point and click interface
February 4, 2005 at 8:00 am

This was removed by the editor as SPAM

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

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

magasvs SSCertifiable Points: 7660 More actions · Answer 1

What are SQLSEREVER and SQLSERVERAGENT services startup accounts? Local user, system or Domain account? And does this account has access to that web server? Can you give some information about what the job does?

philcart SSC-Forever Points: 47796 More actions · Answer 2

Both services startup using a domain user account.

Problem hasn't re-appeared for the last couple of days. We could have isolated the problem to a dodgy WINS entry that was preventing the server from authenticating the SQLSERVERAGENT account.

--------------------
Colt 45 - the original point and click interface

L_avital Ten Centuries Points: 1379 More actions · Answer 3

I encountered the same problem and cannot get a solution for it. We have SQL 2000, SP3 on windows 2003. Would appreciate any help in this matter.