SQL Server Performance Forum – Threads Archive

Job status not updated in sysjobshistory…

I have a Job which calls a DTS package. This DTS packages just extracts data from a text file into tables. I have permission to execute the jobs (which calls the DTS Package) but not to execute the DTS packages separately (which is perfectly fine). Till last week i didnt face any problem running this job. Now, this week, When i run this job, it says its running the job, but there is no sign of job running and it when it stops running, there is no entry in job history. And even if i output the results of the job to a log file, there is no entry in the log file. Can you tell me what could be the actual problem? Thanks,
Ram "It is easy to write code for a spec and walk in water, provided, both are freezed…"

Please let me know if you have the solutions… Thanks,
Ram "It is easy to write code for a spec and walk in water, provided, both are freezed…"

is there anything interesting in agent’s errorlog file? SqlSpec – a fast, cheap, and comprehensive data dictionary generator
for SQL Server 2000 and 2005 and Analysis Server 2005 – www.elsasoft.org

Did you mean errorlog file which we explicitly mention in the job? If you mentioned that, No. i didnt find anything. Thanks,
Ram "It is easy to write code for a spec and walk in water, provided, both are freezed…"

i meant the log file that sqlagent writes. it’s called SQLAGENT.OUT and is usually located somewhere like this: C

rogram FilesMicrosoft SQL ServerMSSQL.1MSSQLLOG each time you restart agent, a new one gets created and the old one is renamed to SQLAGENT.1 – so if you have restarted agent you’ll need to look in those. SqlSpec – a fast, cheap, and comprehensive data dictionary generator
for SQL Server 2000 and 2005 and Analysis Server 2005 – www.elsasoft.org

Enable the DTS package log to know what is happening when the job is scheduled and also ensure the SQLagent has required permission to perform the process in DTS package. Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing.

Oh! Thats bad… i re-installed SQL Server.

quote:Originally posted by jezemine i meant the log file that sqlagent writes. it’s called SQLAGENT.OUT and is usually located somewhere like this: C

Thanks,
Ram "It is easy to write code for a spec and walk in water, provided, both are freezed…"

Most of the time this type of problem is related to security…
Check SQL agent service what login it is using and make sure it has sufficient rights to process involved in dts package. You can add ouput file in the job and see what it is writing it. Mohammed. Mohammed U.

So this means it is not a production server to worry, as you have resintalled quickely. Satya SKJ
Microsoft SQL Server MVP
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided AS IS with no rights for the sake of knowledge sharing.

Its on my server actually. But i thought i would keep myself loaded when the same problem attacks production server… in future [<img src=’/community/emoticons/emotion-1.gif’ alt=’

‘ />] Thanks, Ram "It is easy to write code for a spec and walk in water, provided, both are freezed…"

]]>