March 14, 2009 at 12:17 am
Event Type:Warning
Event Source:SQLSERVERAGENT
Event Category:Job Engine
Event ID:208
Date:13/03/2009
Time:11:00:13 AM
User:N/A
Computer:ANDH001
Description:
SQL Server Scheduled Job 'ItemStrUpdate' (0x1D632FEE4CAF2D489E3948A06154A924) - Status: Failed - Invoked on: 2009-03-13 11:00:00 - Message: The job failed. The Job was invoked by Schedule 8 (Schedule1). The last step to run was step 1 (step1).
Job history in SQL enterprize manager is also showing - job failed at 11:00 pm, but SQL logs do not reflect the entry.
what could be the reason of failure.
Regards.
March 14, 2009 at 8:21 am
Have you looked at the details of the job execution in the job history?
Have you run the code in that job step in Query Analyzer to see what the error is?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
March 16, 2009 at 1:51 am
Job history is showing follwoing details...
Executed as user: NT AUTHORITY\SYSTEM. Transaction (Process ID 220) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. [SQLSTATE 40001] (Error 1205). The step failed.
I don't think so there is problem with the query... cause if i start the job manually in the enterprize manager it runs and comes back to the original status.
what does this mean? how do i resolve this problem?
Regards.
March 16, 2009 at 5:01 am
What this means is that the job, when scheduled, is running at the same time as another process that is locking the same resources, typically in opposite order, and cannot gain access to the resources. SQL Server is detecting this problem and, because your job requires fewer resources to rollback, your job is being "killed" by SQL Server. You can get a better understanding by reading a few articles starting with this one.
Since you are on 2000 you will need to enable trace flag 1204 to output the deadlock information tp the error log, then you will be able to the process that your job is deadlocking with.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
March 16, 2009 at 6:10 am
Thank you for the replies and information....:)....i may come back after reading the article and if i cannot trace 1024.....
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply