Skip to main content
Question

FME Server is trying to get to a zipped file geodatabase

  • April 4, 2020
  • 6 replies
  • 37 views
felipeverdu
Enthusiast
Forum|alt.badge.img+11

Hi

I keep getting this error while my workbench in FME Server is trying to get to a zipped file geodatabase.

748Unable to connect to the File Geodatabase at 'C:/ProgramData/Safe Software/FME Server///resources/data//_Automatiseringar/DATA_GEOPIPE_GEOPARK.gdb.zip'. 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: {}747Installed ArcGIS version is '10.7.1'746An ArcGIS license is already checked out. The product checked out is 'Advanced'745Opening the Geodatabase reader744Notice - Performing envelope query on the `GEODATABASE_FILE' reader, post-filtering spatial predicate in FME743Performing query against GEODATABASE_FILE dataset `C:/ProgramData/Safe Software/FME Server///resources/data//_Automatiseringar/DATA_GEOPIPE_GEOPARK.gdb.zip'

 

I am not sure how to handle this. Even though I point to the right zipped file in the proper resource folder is still complaining.

Help!!!

Br,

Felipe Verdú

 

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.

6 replies

itay
Supporter
Forum|alt.badge.img+18
  • itaySupporter
  • Supporter
  • April 5, 2020

Hi,

Could it be that the user running the workspace doent have the right permissions to access the gdb?

felipeverdu
Enthusiast
Forum|alt.badge.img+11
  • felipeverduEnthusiast
  • Author
  • Enthusiast
  • April 7, 2020

Hi,

Could it be that the user running the workspace doent have the right permissions to access the gdb?

Hi @itay

That could be the reason, but I have tried to give the right permission to access the gdb but it doesn't work quite well...

Thx anyway for your words!

Br,

Felipe Verdú

 

itay
Supporter
Forum|alt.badge.img+18
  • itaySupporter
  • Supporter
  • April 7, 2020

Hi @itay

That could be the reason, but I have tried to give the right permission to access the gdb but it doesn't work quite well...

Thx anyway for your words!

Br,

Felipe Verdú

 

Hi @felipeverdu1,

Can you specify why it is not working? and what permissions are set ?

felipeverdu
Enthusiast
Forum|alt.badge.img+11
  • felipeverduEnthusiast
  • Author
  • Enthusiast
  • April 7, 2020

Hi @felipeverdu1,

Can you specify why it is not working? and what permissions are set ?

Hi again @itay

I think I finally solved it throught restart of services (FME Server). I needed to this several times and this is weird...but I think it is working now.

Br,

Felipe Verdú

jordimonk
  • jordimonk
  • August 7, 2020

Hi @felipeverdu​ 

I had been getting the exact same error message. The workbench worked fine in Desktop, but then failed with that message in Server. I was pulling my hair until I accidentally looked at this line (Desktop log):

 

'0.2|INFORM|Connected to the File Geodatabase at 'C:\\Users\\<myUserID>\\AppData\\Local\\Temp\\FME_TempFileStore_1596819757681_29032\\dsGEODATABASE_FILE_4_1596819757682_29032\\MB_Facilities_HighPressurePipeli_1596819757682_29032\\MB_ENHHPL_GDB_LL83.gdb', which somehow looked to me as a quite long string.

 

The name of the zipped geoDB I was providing was 'MB_Facilities_HighPressurePipelines_IHS.zip'. The name of the workbench, FWIW, was also quite long: 'HS_FacilitiesHPPipesLPPipesGasFranchiseAreas_BCABSKMB_2_FileProcessor.fmw'.

 

In my case, simply shortening the name of the ZIP geoDB to 'MB.zip' made it finally work in FME Server.

 

As I see it, in my particular case at least, it was simply a matter of FME Server enforcing some max. string length rules and truncating the resulting file location string. Once I shorten some of the strings used internally by Server to build the file location, everything works.

felipeverdu
Enthusiast
Forum|alt.badge.img+11
  • felipeverduEnthusiast
  • Author
  • Enthusiast
  • August 21, 2020

Hi @jordimonk​ 

Thanks for your comment. I believe we solved the problem enabling long file path support. See the link below.

https://community.safe.com/s/article/windows-enable-long-file-path-support

Br,

Felipe Verdú

Community Stats

32,120
Posts
121,954
Replies
39,772
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.