Windows Scheduler has failed us for (hopefully) the last time. I'm trying VisualCron now.


After install, I started by migrating one scheduled task. All of our tasks "run as" a local windows user. In VC's credentials for the task's user I set up the password and successfully tested the user our. Impersonation, check!

At first, I was getting task failures with exit code -1073741502
I then:
1) set the service to run as a server user in the local Administrators group
2) Disabled UAC using the dialog box in VisualCron
3) Rebooted

Now I'm getting exit code 1314. NO further details. No google search or forum article mention it except one where support wanted to switch to email because "Beta".
What can I try now?

Thanks!
Larry Smith
Parapet Studios

I dropped back to the most basic command I could think to execute: "dir", in a job that's not scheduled, just run at-will.
[UPDATE] I had to wrap the dir command into a batch file, dir.bat, so that answers one question: NO, you can't run os commands directly.

Running as system with interactive desktop does not work in my install. So it's local admin for now.
I managed to get VC to run my dir.bat, but ONLY if the server is running as local admin, and only if the execute task is not trying to use any credentials.

When I try to use user credentials, then I get the -1073741502 exit code again, which is something I really need to resolve as many of my tasks rely on trusted connections to databases etc.

-LS

Please check this:

Make sure that the serviceuser account is a local administrator and member of the group BUILTIN/Administrators.

---

I ensured the service is running as a new user which is a member of the local machines Administrators group. Still cannot use credentials for any other user on the box, even though they test successfully.

There may be one nuance here: our servers are hosted, and we do not control the domain. Therefore whatever user I create cannot be part of builtin\administrators. But I have assured that the user is a member of the local machines Administrators group.

I ensured the service is running as a new user which is a member of the local machines Administrators group. Still cannot use credentials for any other user on the box, even though they test successfully.

There may be one nuance here: our servers are hosted, and we do not control the domain. Therefore whatever user I create cannot be part of builtin\administrators. But I have assured that the user is a member of the local machines Administrators group.

Unfortunately that is a Windows requirement to allow another service user start processes. Maybe you did not turn off UAC fullly. What happens if you go into Server settings->Is UAC enabled there? If yes, please disable it and reboot again.

---