February 7, 2007 at 7:18 am
Hello,
I have a process which is hung in Sql Agent 2005. The first step is an SSIS package which loads our data warehouse. The final step of the SSIS package is running a DBCC CHECKDB Task. Looking through the logs I notice that this task ran, and that the package reported Success in the System logs. Sql Agent Monitor shows that it is still executing this step. Moreover, no errors have been reported in the following logs; Sql Agent, Sql Server or the System logs.
We currently have this step executing under a proxy account which has administrative rights. We ran the agent for the first time yesterday as a test and it ran through correctly.
If you need more information I would be happy to provide it.
Any advice or suggestions would be greatly appreciated!
Best regards,
Brad
February 7, 2007 at 12:37 pm
Yes please provide more information if you can.
Who is we? lol
February 7, 2007 at 2:03 pm
How do you know it is hung? Just because SQL Agent Job monitor shows it executing doesn't always mean that it is. Try doing a Refresh of the job (right click on the job, select Refresh).
Another thing you can do is run sp_who2 to see what is really running.
-SQLBill
February 8, 2007 at 7:08 am
Thanks for everyones input thus far.
Bill, I had refreshed the agent monitor as well as disconnected from the engine and reconnected numerous times. It always displayed Executing Step 1.
Here is where I am at. I manually stopped the Agent from running and here is the message that was displayed in the Agent logs.
[136] Job Data Warehouse Nightly ETL Process reported: Unable to terminate process b54 launched by step 1 of job 0x40520E5E2C7EED4DA36B997D1E164058 (reason: Access is denied)
How can I determine what it was trying to access?
Once again, thank you all for your assistance!
February 8, 2007 at 7:37 am
Do you see any other errors in Event Viewer Log under Application and system.
Prasad Bhogadi
www.inforaise.com
February 8, 2007 at 9:06 am
Open up the job and see what step 1 is. If it runs a DTS/SSIS package, just find that package and see what it does.
-SQLBill
February 8, 2007 at 4:24 pm
If all else fails, open Task Manager, find the process for DTExec.exe, and kill the process. Take note whether the process is using a high amount of CPU or memory before killing it.
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply