Beat me to it Brian. Use the process monitor from the says internals tool set to filter out all executables except the one you want to monitor. This could either be the specific process or (I think) the task scheduler process itself and include child processes.
Once you get a failure, save the monitor status from processmonitor to freeze the state and open it as a log file. The filters will then allow you to drill down to identify events? There are some excellent books on the says internals tools on Amazon (and other book stores ;-' ) that I found very useful. Regards, JayJay On 16 Aug 2013, at 18:16, Brian Leach <br...@brianleach.co.uk> wrote: > Can you trace the process using the SysInternals tools? > > Sent from my iPhone > > On 16 Aug 2013, at 18:09, "Woodward, Bob" <bob_woodw...@k2sports.com> wrote: > >> Hi folks, >> >> >> >> I have a UNIDATA program that is being run from a Windows Task Schedule >> entry that is failing on a WRITE statement and I'm having a heck of a >> time figuring out why. Here are some key observations and discoveries >> so far: >> >> >> >> - The WRITE statement has an ON ERROR that is not being executed. >> >> - Just before the WRITE statement, FILEINFO shows the file is OPEN and >> has a permissions value of 6 (R/W). >> >> - It does not always fail but when it does fail, it will continue to >> fail on that input file every time the program is run from the Windows >> Scheduler. >> >> - If I run the program directly, from my logged in session, it works >> perfectly every time. >> >> - Every tool I have says there is nothing wrong with the file I'm >> writing into. >> >> - There are 3 indexes on this file but they are all flagged to allow >> duplicates. >> >> - There are 2 triggers on this file that monitor and report for >> specific record ID's. (Very basic/simple logic.) >> >> >> >> I've pretty much exhausted ways, and things, that I know of to check >> for. This is a very specific problem that is somehow related to the >> data that is being processed. Can anyone think of something else I can >> check for? >> >> >> >> Thanks for your thoughts, >> >> >> >> Bob W >> >> >> >> _______________________________________________ >> U2-Users mailing list >> U2-Users@listserver.u2ug.org >> http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
