Hello,

we have a problem since the last UPDATE the trigger on the file on the network don't working anymore we have to give right "EVERYONE" on the file for it's work but before the update all is working perfectly it is a bug ?

Sorry for my bad english i'm French.

I do not think this is a general problem. You are probably using no or the wrong Credential.

---

why only the trigger don't work ? we use several macros Excel on the network and all is working only the trigger don't work the credentials are good because before the update it's working.

What settings do you use in the File Trigger? Please attach screenshot(s).

---

Screenshot :  

 

We have found another problem when you change a settings on the thask (exemple : background to forground ) the last execution goes to "Never" i think it's not normal because this task are executed in the past

 

 

Do you want to watch for changes to a file (what kind of changes) or newly created files?

---

We just watching when the files text changes and when he change it's launch a cmd task it's work perfectly before this last update.

Log File : 15/06/2012 11:43:54 Err Error in Watcher_Changed->ModifyLock: L'accès au chemin d'accès '\\Mf004\fst\Export\test.txt' est refusé.

but the users can read and write this file...

So, we noticed a problem with the a File Trigger in previous version. The problem was that it triggered twice. So, we made a change where we query the last modified date. Maybe you have some restrictions on this check?

Could you please test the same with the beta 6.1.2. as we made some additional minor changes.

---

where i can find this beta version ?

http://www.visualcron.co....aspx?g=posts&t=2505 

---

same with beta version 😢

log : 15/06/2012 15:11:36 Debug Entering Watcher_Changed: \\Mf004\fst\Export\test.txt(Changed)
15/06/2012 15:11:36 Err Error in Watcher_Changed->ModifyLock: L'accès au chemin d'accès '\\Mf004\fst\Export\test.txt' est refusé.

Which operative system is the VisualCron server and what operative system is the file share located on?

---

Windows 7 for VisualCron and and the file share is a NetAPP

We did some minor changes here:

http://www.visualcron.co....aspx?g=posts&t=2505 

1. we used a new method to detect last write time (should not matter)
2. we ignore and fall back if the above fails so it should work as before

We could not reproduce this on any machine yet.

---

i think the problem is the trigger don't use the credentials same with the last beta :

18/06/2012 16:15:58 Debug Entering Watcher_Changed: \\Mf004\fst\Export\test2.txt(Changed)
18/06/2012 16:15:58 Err Error in Watcher_Changed->ModifyLock: L'accès au chemin d'accès '\\Mf004\fst\Export\test2.txt' est refusé.


He can't read the file

If the Trigger is not using the Credential the folder would not be able to be monitored at all.

We would never be able to see \\Mf004\fst\Export\ without a Credential. You can try this for yourself by deselecting the Credential - you will not even be able to start monitor without error.

In your case the Credential might not be inherited in the Watcher_changed event or that your user requires some specific permissions.

If this was a general problem we would have received a lot of feedback as a lot of our users are using the File Trigger for watching changes.

It would be interesting to know if this is related to:

1. the user that you use
2. the operative system (local)
3. the remote operative system or particular instance
4. the particular machine

We would really appreciate if you could do the following tests to pinpoint this:

1. from the same VisualCron server monitor another remote folder on another machine

2. If this does not work (same error) - then install VisualCron temporary on another machine and test on instance 1 and 2.

---