Skip to main content
Solved

Invalid path in Network Directory Watch, but workspaces can access it

mathiasboudreau
Contributor
Forum|alt.badge.img+4

Hi,

We have recently upgraded from FME Server 2020 to FME Flow 2024.

I have an Automation with a “Ressource or Network Directory (updated)” trigger watching a folder on the network. The automation was working before upgrading, but now it says “Invalid path to watch:”

What’s strange is that I created a workspace with a PATH reader pointing to the same network (UNC) path, and it’s able to read and log all the files in the folder I want to watch. I’ve also tried reading a file in that directory using a textfile reader, and it works.

I don’t understand why FME Flow can read the files in that directory on the network using a workspace, but the automation can’t. If you have any ideas/explanations or possible solutions.

The user account that runs the FME Flow Core service has read and write permission on that directory.

Thank you in advance

Best answer by mathiasboudreau

Thank you for your answer,

It’s now working, the problem was that the user account running the FME Flow Application Server service and the FME Flow Engines service had read/write permission on the network directory, but the user account running the FME Flow Core service didn’t have read/write permission on the network directory.

We’ve added the permission for the FME Flow Core service and now everything is working!

View original
Did this help you find an answer to your question?

2 replies

timatsafe
Safer
Forum|alt.badge.img+4
  • timatsafeSafer
  • Safer
  • May 16, 2024

Hi @mathiasboudreau,

Have you tried deleting the Resource or Network Directory trigger and creating a new one? Could you send a screenshot of your automation trigger configurations?

-Tim

mathiasboudreau
Contributor
Forum|alt.badge.img+4

Thank you for your answer,

It’s now working, the problem was that the user account running the FME Flow Application Server service and the FME Flow Engines service had read/write permission on the network directory, but the user account running the FME Flow Core service didn’t have read/write permission on the network directory.

We’ve added the permission for the FME Flow Core service and now everything is working!

timatsafe
hkingsbury
2 people upvoted this
  • timatsafe
    timatsafe
  • hkingsbury
    hkingsbury

Reply


Helpful Members This Week

Community Stats

31,241
Posts
118,446
Replies
38,833
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.