job report success even though failed..
-
I have a SQL 7 that has DTS packages that check for a flag and if the flag doesn't exist it suppose to fail. When I ran the DTS package, it failed but when I scheduled it as a job it report success. Does anyone know what causing this? thanks in advance..
-
is the job-step set to "quit with failure" when the step fails ?
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
Yes, the job has 2 steps. The first step is the DTS Package, if it fail then the job suppose to stop. However, since the first step never report a failed, the second step get kick off.
I didn't mentioned this earlier but this works before but after I installed SQL2K on the the this machine it start causing this problem.
-
When you run the package, is that at your client or are you at the server-console ?
Don't modify dts-packages from your client, but always perform this stuff at the server, because it can give nasty reactions when there are different versions of e.g. mdac, ...
Johan
Learn to play, play to learn !Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:- How to post Performance Problems
- How to post data/code to get the best help[/url]- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
-
This might sound weird but, does the package actually execute in the scheduler?
Do you know the job is failing where you expect it to fail? On my more complicated scheduled dts packages I routinely set the option on the job step (advanced tab) to write to an output file. Dunno if you've tried it, but it would help you to figure out exactly what's happening (wether the package is actually running, succeeding, or failing.)
The other thing would be to make sure the "Process exit code of a successful command" equals zero. This wouldn't change on its own, so it's probably not the problem here.
Gah. Sorry for the runon diareah of my post
Another possibility could be that your new service profile doesn't have access to run DTSRUN? Or maybe just that particular package?
-Ken -
The DTS package is suppose to find a flag in a file. If the flag exist, it execute other steps in the package. I tested the package, it worked when there's a flag and failed when a flag does not exist. BUT when I scheduled it as a job, it execute w/ and w/o the flag as Success. This is what I'm really confused about.
Also, the job report failed before. But after an installation instance of SQL2K on it, the job is not failure as before. I think SQL2K might have something to do with this. thanks..
-
Could it be that you have it set up so that the task the job step performs is kicking off the DTS package? If so as long as the package starts the step will succeed.
How are you executing the DTS package? TSQL? Command Exec?
"I met Larry Niven at ConClave 27...AND I fixed his computer. How cool is that?"
(Memoirs of a geek) -
The job is scheduled category is Load Process. The DTS package run type is CmdExec.
Another possibility could be that your new service profile doesn't have access to run DTSRUN? Or maybe just that particular package?Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply