Hello,

A recent migration of application server (Win2k3x64 > Win2k8x64) also required us to migrate the VisualCron server. This change was successful and the de- & activation of the license on the new server went smoothly. We kept using the same VisualCron version, 6.2.1. We imported all the settings from the old server and made the necessary adjustments for the new server in various tasks & jobs.

A number of jobs kick off batch processes and report generating task for our business application. After the migration we receive an error message for a range of tasks in jobs that before the migration ran without problems.

Error: "Unable to start process: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it"

On another Win2k8 server that hosts another instance of the same applications, including VisualCron, doesn't show this error. The batch & report tasks we kick of there end up in the 'Interactive Services' are aka console session '0'. On the server with the above error the batches don't make it that far.

Before I forget:

We have tested setting a working directory (no effect). Also we enabled 'Use shell execute' & ran it with no credentials. Although this appears to work, the process is no longer visible on the application server, not even in the Interactive Services view or console '0'.

We also tested by enabling 'Use shell execute' again & ran it with the original credentials, but now 'run with managed code'. Here too the batch runs fine, but is not visible on the server at all anymore.

Try unchecking "Local login" and "Load profile" on the actual Credential being used.

---

I'm getting the same error whenever I try to run a task that runs a batch job using credentials. - checking/unchecking local and loadprofile doesn't make a difference. The credentials are for users in Active Directory.We are using version 7.2.

I'm getting the same error whenever I try to run a task that runs a batch job using credentials. - checking/unchecking local and loadprofile doesn't make a difference. The credentials are for users in Active Directory.We are using version 7.2.

Try to find out which row in your batch file is causing the problem and tell us about it here.

---

I've gone and reduce the batch file (test2.bat) to one line

rem yada yada yada

and it fails with the above error if I use credentials.

I've gone and reduce the batch file (test2.bat) to one line

rem yada yada yada

and it fails with the above error if I use credentials.

Ok, so it is something about the Credential. Do other Credentials work with yada yada 🙂

---