Hmm is the Flow running the services as local, or via a service account https://docs.safe.com/fme/html/FME-Flow/AdminGuide/Running_System_Services_Under_Different_Accounts.htm you need to grant the service account full permissions to the flow share

Thanks j.botterill, the Flow running the service via different windows account, such as fmeflow rather than as local.

I had tested that login to the windows server via the fmeflow account, and create a file, update the file and delete the file in the FSx shared resource folder successfully. So I beleive I had the full permissions to the flow share.

BTW, could you please guide me to grant privilege on FSx mounted share for the windows account? As I couldn’t see where I could do it in the shared folder’s properites window. Do I need to tick the “W” boxex in Group and Other? 

Check that the service account also has the following granted 

Hi ​@fei2000,

Just checking in to see if you’ve had any luck resolving this issue yet?

Do you have a different SDE file you can try? At least then we will be able to see if Flow can read any SDE files from your shared location, or if only this file causes the problem. It might also be worth testing if you can use the shared file in a different workspace, just to eliminate the workspace as a possibility as well.

Another thing you could try is adding the SDE connection file using the full file path rather than using the Browse Resources button. This is related to this known issue, however since you already have the file uploaded to the Flow data folder, this may or may not help.

If you have confirmed that the service account has all the required permissions and nothing else seems to help, I would suggest submitting a support ticket referencing this post. If you could also include a job log from when this workspace was successful (SDE stored locally) and a job log from when it failed (SDE stored in shared folder) that would be very helpful!

Thanks,

Aaron H.

Thanks aaron.hillier,

I had tried multiple SDE files and none of them worked in the shared Resources folder. And I also tested to use UNC path directly as you suggested, it’s still no luck, same error messages. But when I copied them to the Windows local drive, like “C:\FME\data\”, then all working fine.

Regarding to the account privilege, I created a separate administrator account to install FME Flow and run FME Flow service. I used the same account to mount the AWS FSx shared folder as FME Flow shared storage. And I could create and delete a file in the AWS FSx shared folder directly from Windows File Explorer. And I could upload and delete file from FME Flow web UI in the Resources folder. And I could execute System Caller to run script in the shared Resources folder as well. So I believe I have R/W privilege in the shared Resources folder.

I will raise a support ticket regarding to this issue. Thanks for your help.