Skip to main content
Solved

Space in the path for File Geodatabase for reader will fail and cause ArcObject error when published to FME Server 2019.1

  • July 30, 2019
  • 4 replies
  • 43 views
jhu_20
Contributor
Forum|alt.badge.img+7

I have the following FGDB as reader. It works in FME Desktop 2019.1 but will fail and get Arcobject error when published in FME server 2019.1. It looks like that FMEserver 2019 cannot handle space inside the file path.

\\\\enervest\\shared\\ArcGIS\\GIS\\Geoscience Technology\\Raw Vendor Data\\Rextag\\Temp\\Rextag_Crude_Oil\\Rextag_Crude_Oil.gdb

 

Received arcobject error when running the job on FME server:

Unable to connect to the File Geodatabase at '\\\\enervest.net\\shared\\ArcGIS\\GIS\\Geoscience'. Make sure the correct filename was specified, and that the geodatabase wasn't saved with a newer version of ArcGIS than the one installed locally. The error number from ArcObjects is: '-2147024893'. The error message from ArcObjects is: {}

 

This is not good since I have not seen this problem in FME 2018.

Best answer by laurawatsafe

We have confirmed that this is an issue with space characters when publishing workspaces from FME 2019.1 to FME Server 2019.1. We are tracking this with issue number FMESERVER-13286. We will update this post as soon as the fix for this problem has been made available.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

laurawatsafe
Safer
Forum|alt.badge.img+13
  • laurawatsafeSafer
  • Safer
  • Best Answer
  • August 2, 2019

We have confirmed that this is an issue with space characters when publishing workspaces from FME 2019.1 to FME Server 2019.1. We are tracking this with issue number FMESERVER-13286. We will update this post as soon as the fix for this problem has been made available.

jhu_20
Contributor
Forum|alt.badge.img+7
  • jhu_20Contributor
  • Author
  • Contributor
  • August 2, 2019

Laura,

Thanks.

steveatsafe
Safer
Forum|alt.badge.img+13
  • steveatsafeSafer
  • Safer
  • January 9, 2020

This has been resolved in 2019.1(b19629) and above.

SteveatSafe
jhu_20
Contributor
Forum|alt.badge.img+7
  • jhu_20Contributor
  • Author
  • Contributor
  • January 9, 2020

Laura,

Thanks.

Laura and Steve,

I tested and can confirm that the issue was resolved in FME 2019.2. Thanks.

Community Stats

32,207
Posts
122,305
Replies
39,891
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.