Sage 100 Advanced v5.10.3, running on Win 2008 R2 SP1, as a service.

I have a batch file to trigger a VI Job, and that works, but for some reason it fails whenever I am logged in to the server with the Sage client running (even at the login prompt... or logged in fully to a session).

The scheduled task is set to run using the same windows admin login as I use to connect to the server (remote desktop).  I tried to set the MAS user to spawn tasks from the server, hoping that might clear it up, but nothing changed.  The scheduled task does spawn a pvxwin32 process, but the VI job never starts, and the Task Scheduler just shows the job as "running"...

Basically this means I can't support this customer using the Sage client running on the server without the risk of interrupting an automated process I just set up.

Batch file commands:

Service set up (according to the instructions in the Knowledge Base).

Has anyone else had problems with scheduled VI jobs failing when the Sage workstation is logged in (on the server)? 

Will using a different windows login for the scheduled task vs. my remote windows RDC make any difference?

Thanks in advance for any insights into this problem.