I have many tasks in Task Scheduler that kick off a particular program
passing parameters to it so it knows what to do. Sometimes that program does
not end gracefully and ends up consuming 50% CPU and slows system down. I do
not find out about this until a user complains of slowness.
passing parameters to it so it knows what to do. Sometimes that program does
not end gracefully and ends up consuming 50% CPU and slows system down. I do
not find out about this until a user complains of slowness.
The tasks run various VBS scripts which in turn runs an MS Access program.
When the problem arises I look at Windows Task Manager and see that sure
enough there is an MSACCESS.EXE at 50%. How the heck do I determine what Task
initiated this process so I can see what parameter was passed to the MSACCESS
program to see what code is being executed there?
—
Regards
Tom
