Skip to main content
Solved

Network based resource connection issues

vn1
Contributor
Forum|alt.badge.img+4
  • vn1Contributor
  • Contributor

I am trying to utilize a file share within a workbench and establish a network based resource connection on FME Server through the web ui but receiving errors that we have been unable to diagnose. In both uses, the error states "Folder not found" and the location is being referenced by unc path (e.g. \\\\server-name\\folder). The folder in question contains a space, so I have attempted using single quotes and url encoding the unc path with no success. We currently use other file shares within FME Server, and have granted the computers credential (e.g. mango$) read/write access to those resources with success. From the system that runs FME Server, I can verify that other users can access the file share in question, so there doesn't appear to be a firewall issue or other connection related issue. Any help would be appreciated in resolving this issue.

We are currently on FME Server 2017.0.0.1

Best answer by vn1

We ended up resolving this issue. In the initial effort, access was only granted at a subfolder level. The issue was resolved by granting "list folder contents" at the root of the file share \\\\server-name\\drive$

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

6 replies

david_r
Celebrity
  • david_rCelebrity
  • March 22, 2018

Are you already running the FME Server engine as a domain user with approriate rights on the share?

If the service is running as local admin, you'll have to reconfigure to use a domain user:

https://docs.safe.com/fme/html/FME_Server_Documentation/Content/AdminGuide/Running_FME_Server_Engines_Under_Different_Account.htm

vn1
Contributor
Forum|alt.badge.img+4
  • vn1Contributor
  • Author
  • Contributor
  • March 22, 2018
david_r wrote:

Are you already running the FME Server engine as a domain user with approriate rights on the share?

If the service is running as local admin, you'll have to reconfigure to use a domain user:

https://docs.safe.com/fme/html/FME_Server_Documentation/Content/AdminGuide/Running_FME_Server_Engines_Under_Different_Account.htm

David, I have read through this and the Directory and Account Permissions and am trying to understand the how it would apply to our environment. Our implementation is Windows Server 2012 R2 and all components are installed and running on a single server. We currently connect to other unc based resources as the local system account for reading and writing data using "server$".

 

 

vn1
Contributor
Forum|alt.badge.img+4
  • vn1Contributor
  • Author
  • Contributor
  • Best Answer
  • March 22, 2018

We ended up resolving this issue. In the initial effort, access was only granted at a subfolder level. The issue was resolved by granting "list folder contents" at the root of the file share \\\\server-name\\drive$

david_r
Celebrity
  • david_rCelebrity
  • March 23, 2018
vn1 wrote:

We ended up resolving this issue. In the initial effort, access was only granted at a subfolder level. The issue was resolved by granting "list folder contents" at the root of the file share \\\\server-name\\drive$

Excellent. Thanks for sharing the solution.
krien
Contributor
Forum|alt.badge.img+10
  • krienContributor
  • Contributor
  • December 4, 2018

@vn1, @david_r

Hi,

We (Vicrea) have a customer that had a similar Network Shared Resource issue. After installing FME Server with backup from 2016, the Network Share Shared Resource came up with the error: Path / does not exist for shared resource. All the known issues (domain User, rights on share, Service accounts etc.) checked but no solution found.

I tried to reproduce the issue in our environment by following the tutorials in https://knowledge.safe.com/articles/34522/fme-server-resources-uploading-referencing-and-con-1.html but al worked fine for me.

It was obvious an access problem and I searched in all Fme Server files, both the installation and resources for the MYDATA network shared resource I created.

 

In the fmesharedresource.log there was no MYDATA, but it showed up in the Safe Software\\FME Server\\resources\\logs\\tomcat\\localhost_access_log_.txt.

After I communicated this with the customer, they found in the \\tomcat\\localhost_access_log_.txt. a 404 error on their shared resource.

Changing the Tomcat Service to run under the Domain Account solved this issue!

Kind regards,

Krien Guijt

 

 

david_r
Celebrity
  • david_rCelebrity
  • December 5, 2018
krien wrote:

@vn1, @david_r

Hi,

We (Vicrea) have a customer that had a similar Network Shared Resource issue. After installing FME Server with backup from 2016, the Network Share Shared Resource came up with the error: Path / does not exist for shared resource. All the known issues (domain User, rights on share, Service accounts etc.) checked but no solution found.

I tried to reproduce the issue in our environment by following the tutorials in https://knowledge.safe.com/articles/34522/fme-server-resources-uploading-referencing-and-con-1.html but al worked fine for me.

It was obvious an access problem and I searched in all Fme Server files, both the installation and resources for the MYDATA network shared resource I created.

 

In the fmesharedresource.log there was no MYDATA, but it showed up in the Safe Software\\FME Server\\resources\\logs\\tomcat\\localhost_access_log_.txt.

After I communicated this with the customer, they found in the \\tomcat\\localhost_access_log_.txt. a 404 error on their shared resource.

Changing the Tomcat Service to run under the Domain Account solved this issue!

Kind regards,

Krien Guijt

 

 

Hi, thanks a lot for the details, much appreciated!

Reply


Helpful Members This Week

Community Stats

31,198
Posts
118,255
Replies
38,801
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.