Thanks Henrik
For clarity (and I apologise for my ambiguity) I am running the process as a 'Remote Execute' task.
If I change to an "Execute Process" task the process executes locally without issue. It is only when I attempt to run the process on another network server that I get the error.
I have set up my VCron service on my designated server and then will be using 'Remote Execute' tasks with appropriate account authenication to run several tasks on other servers. The control and development of the Jobs/Tasks will be done by Data Operations staff using the client to connect to the VCron server. There is no HTTP client access required
All of our servers (200+) are running Win2003 R2 on VMWare using the ESX platform. There may be up to 500 scheduled jobs per day with any thing from 10 to 30 tasks each.
Chris Hyett
Development Team Leader
Datamail New Zealand Limited