Dear Support

We just had a strange issue with a file trigger:

The file trigger is checking the folder of another server "S1". The server was down over the night and was restarted in the morning. After restart one of our triggers opened a session at the "S1" but did not close it accordingly. From our VC-Server everything looked fine, but no more connections could be opened, the "S1" refuses it.

Do you have an idea how this could happen? There are about 7 jobs that do a file triggering on this server. The job that caused the issue checks the connection every second and the others every 60 seconds. Was this the issue? Or maybe I did something wrong in the job/trigger?

As this job doesn't need to check each second (I have no idea where this number comes from), I'd like to change it. But the field for changing is greyed out. Can you please tell me how to change the number of seconds when the job has to check for new files?

Thanks a lot for your help in advance

Cheers

Susanna

There is no 1 second check unless you use the polling option (which you should not use). Default behavior is using the non polling method which means that any change is instant (no delay).

When you write about this I am not sure if you have enabled polling or not? It should be disabled.

You do not write it explicitly but do you get problems when enabling the Trigger again and what is the exact error?

---

Hi Henrik

Thanks, polling is not active, so it's not using this field then? It is disabled. 😉 Our Helpdesk wants to know how it is working that VC recognizes the change. Can you please explain?

Yes, I did get any problems when I enabled the trigger again. But the trigger was just deactivated without any error. I received an error when I tried to connect via UNC path to the server:
"The network BIOS session limit was exceeded."

On the "S1" we saw hundreds of sessions opened and a long list listing the directory the specific trigger is checking with status "Read". Hope you understand what I mean - I don't have any PrintScreens unfortunately, as we had to solve the issue immediately.

Thanks

Susanna

The file trigger is using a .NET API (FileSystemWatcher) which in turns uses a Windows API (ReadDirectoryChangesW).

Whenever an application subscribes for changes it will be notified when a change has occurred.

Normally, when a Trigger is disconnected/can't connect we unsubscribe for changes.

Which tool did you use to see the open sessions?

---

Henrik

Thanks for Info. :)

The support used the "Computer Management" to list the sessions and the open files. If you need to know: he opened it locally and connected to the server.

Susanna