I'm attempting to set up a trigger for a task so that the task will run whenever a particular file is created in a certain location on a network path. I'm am referencing the location using a UNC path.

The Trigger type is "File", and I am using credentials on the trigger which DO have access to the location of this file. Under the File tab for the trigger, I'm specifying the UNC path to the folder in the 'Folder Path:' and the exact name of the file in the 'File mask:' field. Watch type is only on Created, and Notify filters is only on File Name. 'Use polling (Samba compatible)' is checked, and 'Include subfolders' and 'Trigger when file has been released' is NOT checked.

When I save the task, I get the error message "A trigger was inactvated due to an error: Access to the path '\\my\folder\path' is denied. The trigger was connected to the job: MyJob". What am I doing wrong? Like I said, the credentials I selected on the trigger have access to the location (I've verified this), but it's almost as if VisualCron isn't attempting to use those credentials when validating the path.

Is your VisualCron service running as 'Local System' like it does by default or are you running it under another ID, such as a service account?

I seem to recall something about if you are using 'Local System' you may need to switch it to use a domain account. We use UNC file triggers all the time, but our VisualCron service runs as DOMAIN\VisualCron which is a local administrator on the VC server and have no issues. however, this DOMAIN\VisualCron user has access to the share and we do not specify individual credentials for triggers. The VC Server is limited to a few people on our team so as to avoid security concerns. 'Users' don't get to manage anything.

Brian

Hi Charles,

first, do not use Samba alternative unless it really is a Samba share. Second, use a Credential in the File Trigger that matches a user that have access to that remote system.

---

Is your VisualCron service running as 'Local System' like it does by default or are you running it under another ID, such as a service account?

I seem to recall something about if you are using 'Local System' you may need to switch it to use a domain account. We use UNC file triggers all the time, but our VisualCron service runs as DOMAIN\VisualCron which is a local administrator on the VC server and have no issues. however, this DOMAIN\VisualCron user has access to the share and we do not specify individual credentials for triggers. The VC Server is limited to a few people on our team so as to avoid security concerns. 'Users' don't get to manage anything.

Brian

Yes, we run VisualCron under the default 'Local System' user. Our intent was to use the appropriate credentials to access this share rather than to have the service run under a certain domain user (via the Credentials drop-down in the trigger settings). We have several dozen VisualCron tasks that we'll be setting up requiring a variety of privileges to different network resources, so we didn't want to throw all the eggs in one basket.

Hi Charles,

first, do not use Samba alternative unless it really is a Samba share. Second, use a Credential in the File Trigger that matches a user that have access to that remote system.

It really is a Samba share, and the credentials I'm attempting to use does have access to it.

Charles,

Did you ever resolve this? I am running into the same problem.

I was running into the same problem. What i did was create my UNC path under the Network Drives in Visual Cron and then just browsed to the file using the newly created Network Drive. Has worked perfect.

Since I don't think it was ever mentioned...

Is it possible you have multiple credentials for tasks, file triggers, etc... that all access the same server via UNC? Even if the share name is different, if you connect to ServerA with CredentialA, and then try to connect to ServerA with CredentialB, you will sometimes have problems. i'm not talking about VisualCron problems, i'm just saying that in general this is the case with Windows.

So if you were logged into your computer as DOMAIN\User1 and mapped a network drive to \\Server1\Share1

If you try to map another drive to \\Server1\Share2 as a different ID (while still logged in as User1, using the 'connect as' option), it'll likely fail.

Might not be your issue, but if you do use multiple credentials to access the same server (regardles of which share), it could very well be your cause.

Brian

'Use polling (Samba compatible)' is checked

If the server your UNC path points to is a Windows server you should NOT use Samba compatible polling. Only use it if your server is actually running the samba.org software.

Samba has some quirks that need to be worked around, however the same workarounds cause authentication against Windows servers to fail.