We are running VisualCron version 5.7.3.

We are trying to set up a task to search for strings in a file using the c:\windows\system32\find.exe command.

Running the following at the command line works and produces a list of matching strings:
c:\windows\system32\find.exe "error" c:\applogs\dailyrun.log

We set up a task with the following settings:
command c:\windows\system32\find.exe
arguments "error" c:\applogs\dailyrun.log

When we try to run it, it fails with a result code of -1073741502. There is no output in stdout or stderr.

Any idea what is up with this?

Try running with a Credential - that worked for us.

---

We are running with a credential when we are getting the error.

I have tried with no credential, active directory user, active directory domain admin user and local admin user. All produce the same error.

It seems like this exe throws some exit codes even though it works. I would use another "find" applicaiotn. You just want to find files with a certain content right?

---

Try the free "grep" port:

http://www.gnu.org/software/grep/grep.html 

---

Update:

We discovered that other pre-existing tasks (which had been working) were producing the same result when we tried running them. We rebooted the server and that cleared the problem.

The problem has re-occured since. Unfortunately I don't have any firm details of when or how often this problem arises as I only ever get to hear about it days later (I've tried to get people to keep proper logs but so far without success!)

We also seem to have a similar issue where jobs and tasks all appear to run successfully but only take one or two seconds. When we check further it is apparent that the tasks have actually not run at all. Again rebooting seems to fix the problem.

I believe our Operations staff have tried restarting the VC service rather than rebooting but it usually goes into a 'stopping' state and stays there - hence they do a reboot.

Perhaps you are able to use the "grep" command instead as "find" throws some strange errors even though it works.

---

The problem isn't anything to do with find or grep.

The problem originally came to light when we tried testing a new task that used 'find'. However it was subsequently discovered that all execute tasks were failing in the same way. VisualCron couldn't initiate any new processes.

A reboot resolved the problem. But the problem has occured again since.

A similar but slightly different problem has been seen. This results in all execute tasks seeming to work (i.e. they say they ran and were successful) but not actually running the script/executable. This is actually more serious as a casual glance at VC suggests everything ran OK. Only on closer inspection do you realise nothing actually got run.

I did wonder whether it was a problem with the O/S but stopping and restarting the VisualCron service seems to fix the problem. This suggests that the VC service is failing for some reason.

We did some research about exit code -1073741502 and we found 2 possible solutions:

1. Go to administrative tools->Local security policy. Set SYSTEM user with Logon as batch Job. Reboot. Try Task again.
2. Disable UAC. Reboot computer. Try Task again.

---