![]() |
|
![]() |
AutoMate Discussion | ![]() |
Topic Title: Issue with File watcher trigger in BPA 7 Topic Summary: File watcher trigger Created On: 01/20/2011 12:51 PM Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
||||
Hi I have a task set to trigger based on file (added) to a network shared folder. The server on which the shared folder exists does NOT have a BPA agent running. The trigger does not seem to be working. However, triggers on shared folders on servers with agents installed are working fine. Does this mean that for a file trigger to work, every server with shared folders (whenever we have a file trigger for a specific shared folder) need a BPA agent. Please advise.
|
||||
|
||||
![]() |
||||
Hi Annie,
Does the user that you specified in the File Condition have sufficient permissions to the shared folder that you are trying to trigger from? It is not a requirement that an Agent is installed on the file server machine.
------------------------- - Rick Johnson Network Automation |
||||
|
||||
![]() |
||||
Yes I have specified a user for the file trigger to access the shared folder. and the assigned user has access to the shared folder. After setting up the task for the first time, when i was still logged on to BPA 7, the task did trigger once. and then it would just not trigger at all.
|
||||
|
||||
![]() |
||||
Hi Annie,
Is the machine running the agent logged in at all times, or doe that station get logged out or locked?
------------------------- - Rick Johnson Network Automation |
||||
|
||||
![]() |
||||
The machine gets locked and logged off at times But i have set the user and pwd to run the tasks in background I tried if it would trigger when the machine was logged into with the appropriate credentials and still the trigger would n't work.
|
||||
|
||||
![]() |
||||
Hi Annie,
What are all of the settings for your File System condition? Would you be able to back up your workflow and attach it to a reply?
------------------------- - Rick Johnson Network Automation |
||||
|
||||
![]() |
||||
Hello Currently having issues working with file watcher in automate 8, over our network. I cant seem to get the task to trigger if the file watcher is placed on a network drive. I have tried to full path including server name but no luck. Any ideas? Thanks James
|
||||
|
||||
![]() |
||||
Hi James,
Sometimes using \\servername\DriveLetter$\FolderPath\ is required versus \\servername\sharename notation. What is the value in the path for your trigger?
------------------------- - Rick Johnson Network Automation |
||||
|
||||
![]() |
||||
I'm having trouble separately and wondering if this is still the case in later versions?
|
||||
|
||||
![]() |
||||
This is a Windows and user access issue when it comes to how a UNC path should be referenced. If you are having problems triggering from a network share, make sure you have provided the appropriate user credentials to access that location.
------------------------- ![]() Leonard Amabile | Director, Cross Platform Support AutoMate | InterMapper | Skybot | Divisions of HelpSystems T: +1.213.738.1700 | F: +1.213.738.7665 |
||||
|
||||
![]() |
||||
Have you tried using the server IP address instead of server name?
Had same issue migrating from a VM file server to NetApp. All watchers stopped until IP address replaced server name in the path.
|
||||
|
FuseTalk Enterprise Edition v4.0 - © 1999-2021 FuseTalk Inc. All rights reserved.