Help with mem leak when program ran through task scheduler

[Jeff Colyer]

Hi, I'm running a vendor application that uses an odbc connection to connect to a database. When I run the job from a command line it runs fine and finishes in about 4hrs. If I set the job to run in the background in runs for 12hrs. I've experienced this both on Windows Server 2000 & 2003 operating systems. The hardware is also different but I don't think that it is relevant. The vendors app. is written in VB6 and I don't have access to the source code, but could have them try something if need be.

Some observations: The command line runs the job in the foreground and the memory usage remains constant. The task scheduler runs in the background and the memory continues to grow. When ran from the command line the job is also controlled under the windows explorer tree. When ran from the task scheduler it's ran under the system tree.

Has anyone experienced anything similar before? Does anyone know if there's a registry setting that can force an app. to run under the windows explorer umbrella? It almost seems like the windows garbage collector runs different under the "windows explorer" than when ran under "system". Also I'm using "Process Explorer" software from www.sysinternals.com to monitor.

Any help/advice is appreciated.
Thanks,
Jeff

[Court Campbell]

You might find more help if you posted this in the Microsoft forum.

[Jeff Colyer]

reposted in correct forum.