I have a VB 6.0 SP6 application that processes order files. It is setup to run either unattended as a scheduled task with a command line parameter or via a form interface. The appl generates a report at the end of the run via a Datareport designer.
Now the bug…
When I run the appl via the form interface (or from within the VB source environment to debug) it processes normally and generates the report.
When I run the appl via a scheduled task on my machine it processes the data but doesn’t print the report. The scheduled tasks are created using my own network credentials (which are in the domain admins group by the way) as the RunAs parameters. Nothing appears in errors.log that is typically created in the installation directory when there’s a problem. I also have had the printer queue opened and don’t see anything passing through.
I’m wondering if anyone has experienced this and identified a work around. I’m thinking it’s a part of the XP Scheduled Task process but I have full control rights to my own machine.
Now the bug…
When I run the appl via the form interface (or from within the VB source environment to debug) it processes normally and generates the report.
When I run the appl via a scheduled task on my machine it processes the data but doesn’t print the report. The scheduled tasks are created using my own network credentials (which are in the domain admins group by the way) as the RunAs parameters. Nothing appears in errors.log that is typically created in the installation directory when there’s a problem. I also have had the printer queue opened and don’t see anything passing through.
I’m wondering if anyone has experienced this and identified a work around. I’m thinking it’s a part of the XP Scheduled Task process but I have full control rights to my own machine.