Hello --

We have VisualCron running on a number of servers. Various scripts are executed on a regular basis, using credentials.

On our Windows Server 2003 servers with VisualCron 6.X we have no issues.

However we have upgraded a number of servers to Windows Server 2012R2 with VisualCron 8 and are running into serious issues (We are rebuilding all the jobs/tasks from scratch, so it's not an import error.)

Credentials are mostly broken, we had to disable UAC and apply some other workarounds on this forum to get any task that uses credentials to not return an error with an exit code of -1073741502.

Some scripts work now, but many return an exit code of 77777. However looking at the logs and standard output of all these scripts, they all say they ran successfully and exited with code 0. So the scripts are running properly, but the error code is messing up control flows and timeouts.

I have been pulling my hair out about this and trying every possible combination of options (load profile, log in to desktop, UAC on/off, etc. etc.) and we cannot get these scripts to not return either a -1073741502 or 77777. They are all very basic python scripts, too. If we cannot find a solution that doesn't rely on weird workarounds (disabling UAC is already pushing our luck) we will have to find alternative software.

Thanks for the help -
Thomas

We are investigating this. Currently we have only found the broad permission change by turning off UAC. We would like to find the exact permission needed.

What happens if you reboot the server - same problem?

---

Henrik --

Yes, the problem persists after a reboot.

Thanks, we are investigating this. We were able to temporary reproduce this in Windows 2012R2. But then, days later it started working again. So, it is not clear what is causing it and what made it work. Maybe an update?

Have you performed all updates on the server?

---

Interesting... Yes, all updates are installed.

I'm adding and testing more scripts on a regular basis, so in some time I will be able to tell you which scripts are failing and which ones aren't (there are a few that do not get the 77777 exit code) and if there is possibly a pattern there. But basically these scripts are 100% unchanged from the VisualCron 6/Windows Server 2003 versions which exit with code 0.

Thanks

Hello --

I think I tracked down the problem, the scripts that usually caused this error had some interesting methods of exiting the program. Apparently some functionality has changed in VC versions or Windows versions where these exits now trip a 77777 error (as said above, these scripts have never had issues until being moved to the new servers). I rewrote the problematic scripts to always exit cleanly and this problem has gone away. Weird stuff, but a more benign problem than believed.

Thank you for the support!

Glad it was resolved but we have not changed the Execute Task in a long while. Perhaps you can send sample code which reproduces the error and which not to support@visualcron.com?

---

We have modified this Task for 8.1.2. So if you encounter this again please test this beta or official when released: http://www.visualcron.co....aspx?g=posts&t=6721 

---

Hi
i am just calling a simple sql proc , which waits for a couple of seconds ; i do send the param as an int;
when i run the proc in sql, all is fine
but when i run it from vc, i get an error 77777
any help?
vrsn 8.1.2

Can you post the proc code?

ALTER PROCEDURE p_testwait


(@sec int)
AS

WAITFOR DELAY @sec

Don't mind, i realized what was the problem; Thanks