I assume you checked the permissions part correctly. (See also this article.) Be sure the FME Server Engines run under a network account, not by a local system account. (local system account is default) If not, follow this guide.

"The FME Server Core and the FME Server Engines system services use the local system account by default on Windows, and the fmeserver account on Linux. You may wish to run the FME Server Engines service under a different account that can read and write data across a network, particularly in a distributed installation where this service is installed on separate machines."

Else, does the path contain special characters like é? I did read something about special characters in UNC paths the other day, will try to add.

Do you use a dynamic path, filled by an attribute? Did you check if the attribute contains what you expect with a logger?

Reading from json can change things, you need double slashes then. (c:\\data\\ needs to be c:\\\\data\\\\) See also this article.

Hiya,

no special characters (just letters and these . _ \\ ), checked the permissions, no dynamic path, nothing filled in with an attribute.

Just specifying a specific path to a folder on a shared drive.

Hi @baznewman07, possibly these links could help you.

• Workspace Fails on FME Server When Using UNC Paths
• Running the FME Server System Services Under Different Accounts (Windows)