File Trigger (Folder Monitoring) - VisualCron

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.

Welcome Guest! To enable all features please Login or Register.

kdcarlisle
No customer Topic Starter

2010-11-16T21:35:22Z

How does the server monitor a given folder path / file mask? I ask because we now have jobs that are deactivating (even when the target machine is up and running). After a little testing it appears that the issue is a network BIOS connection issue (network BIOS session limit exceeded).

-Kent

Sponsor

Forum information

Wanna join the discussion?! Login to your Forum forum account or Register a new forum account

Support
Official support

2010-11-16T21:37:42Z

VisualCron uses built in functions in Windows that raises event on file changes. If you are experiencing network problems you should increase the Reconnect attempt and Reconnect interval in the settings of the File Trigger.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

kdcarlisle
No customer Topic Starter

2010-11-16T21:45:25Z

We updated those values a while back. Visualcron is NOT at fault on this issue. When I open a DOS window and try to connect via NET USE, I get the following error: System error 69 has occurred. The network BIOS session limit was exceeded.

IT is investigating the issue, but asked me how the software was monitoring the network folder. How is the connection being made for the server to monitor?

-Kent

Support
Official support

2010-11-16T21:47:55Z

Are you using a UNC path in VisualCron? i.e. \\servername\folder or do you use a mapped drive like z:\folder?

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

kdcarlisle
No customer Topic Starter

2010-11-16T21:51:05Z

UNC path

Support
Official support

2010-11-16T21:53:37Z

You can probably fix this by editing the registry (might require a restart):

http://support.microsoft.com/kb/810886

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

Support
Official support

2010-11-16T21:54:33Z

Apparently, this was solved for another customer with same fix:

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

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

kdcarlisle
No customer Topic Starter

2010-11-16T21:56:38Z

That's what we figured. We had actually read that support document earlier today. I just figured the IT team would update the registry values and reboot the machine. Not really sure why they wanted to know how it makes the connection.

I will post back shortly once I know if that fixes it.

-Kent

kdcarlisle
No customer Topic Starter

2010-11-16T23:49:14Z

That fixed it. Now it would be nice if someone could tell me why it started happening all of a sudden 😞

Support
Official support

2010-11-17T08:13:36Z

#10

Maybe you are monitoring too many sub objects (for the previous settings). For example, if you monitor c:\ with sub folders there are a lot of folders that has to be watched by the operative system.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!

kdcarlisle
No customer Topic Starter

2010-11-17T13:13:50Z

#11

Each job monitors a specific UNC path on one of three servers. Some file masks are pure wildcard (*), while others are partial (empdata*) and some are full names (empdata.txt). The reason it's odd is because there were more file trigger jobs turned on 2 weeks ago and there was no problem.

Support
Official support

2010-11-17T20:54:31Z

#12

I have no answer to that. The limit has been exceeded some way by some application which is not releasing resources after usage.

Henrik
Support
http://www.visualcron.com
Please like VisualCron on facebook!