Skip to main content
Question

Error to geodatabase writing...but only on certain datasets

  • September 7, 2020
  • 7 replies
  • 43 views

jacklonsdale
Contributor
Forum|alt.badge.img+5

 

Hi all,

 

I am getting Geodatabase Error (-2147024893): The system cannot find the path specified, when trying to fanout a dataset and writers are drop and create. It works for some areas but not others. Could be path length issues? Any ideas?

 

Directory: "$(FME_MF_DIR)..\\_FME Outputs"

 

Fanout Expression: "@Value(Area_Ref) @Value(Area_Name)\\@Value(Area_Ref) @Value(Area_Name) Outputs.gdb"

 

(as per clients request i cannot change this folder structure)

 

Thanks!

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.

7 replies

david_r
Celebrity
  • September 7, 2020

How long (number of characters) are the longest path names?


jacklonsdale
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • September 7, 2020

How long (number of characters) are the longest path names?

Around 240 including the table name


david_r
Celebrity
  • September 7, 2020

Around 240 including the table name

Should be OK as long as you don't go above 260 characters, where you may hit some limitations depending on your OS etc.

Do you have a fanout on the feature class name as well? If yes, what is the max length there?


jacklonsdale
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • September 7, 2020

Around 240 including the table name

No fanout on feature class name they are set...but are as long as 33 characters so it seems this could be the issue perhaps?


david_r
Celebrity
  • September 7, 2020

Around 240 including the table name

Feature class names can be up to 160 characters: https://desktop.arcgis.com/en/arcmap/latest/manage-data/administer-file-gdbs/file-geodatabase-size-and-name-limits.htm

But do look out for invalid names in the feature classes.


ebygomm
Influencer
Forum|alt.badge.img+46
  • Influencer
  • September 7, 2020

In my experience, if the filepath plus featureclass names are too long, the featureclasses get created but then error when trying to populate them. Is this what you are seeing?


jacklonsdale
Contributor
Forum|alt.badge.img+5
  • Author
  • Contributor
  • September 7, 2020

Around 240 including the table name

Its strange as it does write the feature classes fine for some of the 'Areas' run in the fanout - only seems to error on some seemingly randomly, and writes successfully when changing the path directory to local.