Dear Support,

after having updated to VC 8.2.3 we have massive problems with event trigger.

1. Event trigger via UNC are not fireing !!!
Trigger Settings in VC

On Main Page : Credential Domain\user


Folder Path : \\S-CDirect1PROD\JobDaten\ConnectDirect\Download
Filemask: JURPARTNER_MAHNDATEN.TXT

File Folder Watch Options checked
Created
Changed

Notify Filter:
FILENAME

Use Polling (Samba Compatibility)
Trigger when File has been released
On Erreor reconnect 28
On Error reconnect intervall 500
Dublicate File delay 300


Event Log Entry :

SearchingForFiles->Path: \\S-CDirect1PROD\JobDaten\ConnectDirect\Download, filemask: JURPARTNER_MAHNDATEN.TXT, Trigger: Mahndaten from CD, current user: NT AUTHORITY\SYSTEM, InstanceId: 14, hashcode: 33520542


2. Failure in Event Log

Error watching directory (1/60), trigger: Bestandsdatren from Partnerschaften bereitgestellt, folder: \\S-SHARE1PROD\prod_AWD\dlva2awd, filter: *, err: System.ArgumentNullException: Value cannot be null.
Parameter name: searchPattern
at System.IO.Directory.GetFiles(String path, String searchPattern)
at VisualCronService.DirectoryInformation.IMHMKAJKIPGADHBBBAJLDOHMNAJDKKPPAMAN(String , Boolean ) in C:\sourcefiles\code\VisualCronService\Triggers\Events\File\FileSystemWatcher2\ObjectInfo.vb:line 444, InstanceId: 8, hashcode: 61669314


Cause seems to be the filemask is without extensions. What will be the behaivour of VC when a File without extension has to trigger.

3. Servicesettings after update have been removed.

Due to the fact that we have to assure 24 hour operation of VC we have set the Service Recovery Option to reboot the server in case of unexpected service shutdown. This settings have been removed to "TAKE NO ACTION".

Item one is of urgent matter !!!

Please send to support@visualcron.com
1. log_serverDATE.txt
2. the time of the crash

---

Dear Support,

I found the Problem of the not fireing the event.

The event triggering File has a length of Null and event is not fired.

Having entered content to the file trigger fires.

We need urgent solutions for all three problems!!!

Regards,

Thomas Gross-Albenhausen

Dear Support,

I found the Problem of the not fireing the event.

The event triggering File has a length of Null and event is not fired.

Having entered content to the file trigger fires.

We need urgent solutions for all three problems!!!

Regards,

Thomas Gross-Albenhausen

Event length of null? The problem in this case is that the file filter is null. Not sure how it has been reset but we have added more debugging to a build that we will send to you soon.

---