Skip to main content
Question

Hello, I have using FME server 2019.X and my workbenches were working fine with no issue. yesterday I was trying run a WB then I got the error in the attached image. anyone can help me in this


The WB reading fgdb from UNC path , I tried to read from local machine same error, read different data same error .

4 replies

jovitaatsafe
Safer
Forum|alt.badge.img+11

Hi @gisuser​,

Are you reading from a zip file by chance? Would you be able to try enabling long file path names on Windows and see if that improves anything? Off the top of my head I am thinking about this article which provides some more information on errors reading zip files but I'm not too clear if that may be your case.


  • Author
  • October 3, 2020
jovitaatsafe wrote:

Hi @gisuser​,

Are you reading from a zip file by chance? Would you be able to try enabling long file path names on Windows and see if that improves anything? Off the top of my head I am thinking about this article which provides some more information on errors reading zip files but I'm not too clear if that may be your case.

Thank u for your reply @jovitaatsafe​ ,

Actually I am facing the issue with the zip files and unzipped files .

I have tried to read data from my local system regarding the number of characters the same error .

my concern is the WB was working fine with no issue and we are reading the data from the same path , suddenly we start facing this issue from 2 days ago.


david_r
Evangelist
  • October 5, 2020

Concerning reading from a UNC path: is the FME Server service acount already configured for network access?

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


  • Author
  • October 5, 2020
david_r wrote:

Concerning reading from a UNC path: is the FME Server service acount already configured for network access?

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

Hi @david_r​ 

 

Yes it is configured to read for network access, and it was working the day before with no issues.

 

Actually I checked the shared folder also it shared for everyone and there are no limitations to access it .

 

I ran one from the sample workbenches, it run successfully.

 

the issue is with the our Workbenches.


Reply


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