Rick, An error is NOT masked or dropped. It is just in today's systems many components interact with each other in order to perform even simple functions and the root cause is not always visible/available to the end component that makes the initial call. Believe me, deleting and recreating a job is not going to fix anything in this case. Job definition is just a bunch of text data. Recreating a job is virtually the same as deleting a piece of text from a text file then inserting the same text back. Indeed, the reason why it seemed to help is different; you probably restarted the scheduler, restarted the system or did something else while recreating the job and that OTHER action directly or indirectly fixed the problem, or maybe fixed it just for a while. : I ended up deleting the job and creating it again from scratch. It’s working : fine now. : I think the root issue here is that an error was occurring that was being : masked or dropped by the program. It would be great if in the next version : we could get a more robust way of discovering errors and different ways of : handling them. : Thank you for your help. : Rick
|