March 12, 2010 at 3:24 am
Hi,
There is a job with 2 steps, each executing a SSIS package. The job
runs everyday at 1.00 am, 4.00 am and at 01.00 pm. This job usually
takes 15 minutes to run.
Issue: It hangs up indefinitely until someone notices. This happens
with any of the schedules randomly. (The job does not fail, but just
hangs up). It runs fine when it is cancelled and re-run.
The SSIS packages are stored in MSDB.
Observations: There is output file configured for each step with
append option. But, when I open the output file when the job is stuck,
I have noticed that there is nothing logged in there. ( Not even that
Job started:...). So I believe, the job hangs up even before it calls
the SSIS.
Questions: An ideas on this issue??? and actually, when does an agent
starts logging information in the configured output file? In this
scenario, as the job hangs up even before it starts logging
information, is the issue with the agent itself? But none of other jobs have
issues on this server.
Thank you
R__
[font="Verdana"]Renuka__[/font]
March 12, 2010 at 4:12 am
What is the package? What does it do? Did you try taking out the second step in the job (how does that effect it).
I have a package that does a robocopy of backups once they complete and then moves them over to our scf. It then uses a WMI wait command to watch for the creation of a file (created by robocopy to signify completeion).
We used to run it as a 'pull' (scf pulled the backups) and we had the same issue as you, sometimes it would just stop, the package worked but the WMI didnt see the file (hence no log or completion). We reversed the logic and did it as a 'push' from the sql server. Since then, all rosey.
So let us know what your are trying to do. It may be a simple as the need for a wait. 😀
Adam Zacks-------------------------------------------Be Nice, Or Leave
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply