We have a number of jobs watching for files to be created. Most are on the same machine as VisualCron, a few are on remote servers reachable with a UNC path.

When a task fails I've been right-clicking on the job, and selecting Triggers > File Trigger > Fire.

This works for files on the local machine, but not remote machines. Is this a known limitation? Bug?

VC 8.5.1 under Windows 8.1 Pro

Do you get any error? Please send log_serverDATE.txt after doing this to support@visualcron.com

---

E-mail sent. In testing, it would eventually trigger if I selected 'fire' 3 or 4 times.

E-mail sent. In testing, it would eventually trigger if I selected 'fire' 3 or 4 times.

It sounds normal that it fires 3-4 times if there are so many files as the Fire will try to match all files in that folder. If you have files that have been processed we recommend moving them if you plan to use the Fire.

We could not reproduce the "access denied" error when firing manually. I assume you are using a Credential in the first place. Can you send some screenshots of your Trigger settings?

---

The first 3 or so times VC ignored the ‘fire’ command. The final time I selected ‘fire’ the job triggered correctly for each file present.

The task which is executed moves each file it processes to a different folder.

Will send a screenshot.

The first 3 or so times VC ignored the ‘fire’ command. The final time I selected ‘fire’ the job triggered correctly for each file present.

The task which is executed moves each file it processes to a different folder.

Will send a screenshot.

Yes, I saw there was a access denied failure i the log. It is not clear why and it makes no sense really unless the folder was temporary locked some way. Are you running the VisualCron service as the SYSTEM account?

---

The VisualCron service is using the installation default: Local System account, Allow service to interact with desktop.

The job trigger is using my AD credentials, and I'm running the GUI under my login.