Good morning,

I'm not sure if anyone has found a workaround for this issue, I tried to look for similar threads but found nothing.
My issue is that I have a File Event Trigger that looks at a UNC path and checks if a file is created, then fires.
However, whenever the server (where the UNC is pointing to) restarts or looses connection temperately, the trigger disables. Then I'm forced to enable it manually.

Any thoughts?
Thanks,

This is actually a common question. The reason the File Trigger disables because it gives up retrying to connect to the remote server. Fortunately, the number of times and retry interval can be set in the File Trigger. See image below:

---

We have it set up as well, still deactivates even if the server is up and responding.

I suggest looking at log_serverDATE.txt. You will see after how long time it gave up.

---

I have a huge file on the log, any specifics I should be looking for?

Like whats the event like when the File Trigger can't see the file on the UNC?

Well, I found the the issue but does not tell me why the Trigger stays disabled.

4/14/2015 1:08:01 PM Err Error watching directory (0/60), trigger: If TEST file is created/changed in TEST, fire, folder: \\TEST\, filter: TEST.txt, err: System.ComponentModel.Win32Exception (0x80004005): The specified network name is no longer available
4/14/2015 1:08:02 PM Debug Reconnecting in file trigger: , InstanceId: 41, hashcode: 61964805
4/14/2015 1:08:02 PM Debug File trigger event (RemoveHandlers), InstanceId: 41, hashcode: 61964805
4/14/2015 1:08:11 PM Debug Reconnecting in file trigger: If TEST file is created/changed in TEST, fire, InstanceId: 36, hashcode: 47051292
4/14/2015 1:08:11 PM Debug File trigger event (RemoveHandlers), InstanceId: 36, hashcode: 47051292
4/14/2015 1:08:11 PM Debug File trigger event (AddHandlers), InstanceId: 36, hashcode: 47051292
4/14/2015 1:08:11 PM Debug Reconnected file trigger 'If TEST file is created/changed in TEST, fire' . Directory: \\TEST\, filter: TEST.txt that belonged to Job 'Test Job'

Hi,

Looks like this error is the 1st of the 60 tries. ( Error watching directory (0/60) )
In your settings it looks every 2 minutes, 60 times (2 hours total). So around 3:08PM you should see a message that the trigger is disabled.
Is that correct?

The log you provided doesn't say the tigger is disabled, it only tells you the UNC path is not found.

Regards,
Erik

---

I looked around that time-frame and I can't see anything that says the trigger was disabled.

Anything in specific I should be looking for?