Skip to main content
  • EN

I am running an FME-routine in FME Desktop (2022.2) where I want to modify data from an ESRI Geodatabase and write them back to another ESRI Geodatabase. This routine has always worked fine for months until recently, where it suddenly gets the following error messages in the log-file:

2023-11-28 20:05:40|6109.0|  0.0|ERROR |An error occurred while attempting to insert a row into the table 'UPDATE_TABLE' using a cursor. The error number from ArcObjects is: '-2147155558'. The error message from ArcObjects is: {Overflow or value larger then maximum 32bit integer gUPDATE_TABLE]}
2023-11-28 20:05:40|6109.0|  0.0|STATS |Storing feature(s) to FME feature store file `D:\LOGS\Matrikkeloppdatering_log.ffs'
2023-11-28 20:05:40|6109.0|  0.0|ERROR 

Any tips on how I should resolve this issue? Is it related to version compatibility? I am currently using ArcGIS Pro 3.1.2. 

Can you check that .ffs file that's being written, that should contain the feature(s) that trigger this error so if you inspect them you may find what's wrong.

 

The error message refers to an overflow error in a 32-bit integer value, they can range from -2,147,483,648 to 2,147,483,647 (or 0 to twice that last value if it's unsigned). Is it possible you have an attribute value that falls outside of that range?

Can you check that .ffs file that's being written, that should contain the feature(s) that trigger this error so if you inspect them you may find what's wrong.

 

The error message refers to an overflow error in a 32-bit integer value, they can range from -2,147,483,648 to 2,147,483,647 (or 0 to twice that last value if it's unsigned). Is it possible you have an attribute value that falls outside of that range?

I have checked the .ffs file and it seems like that's the case. Is there any way to change the data type to a 64-bit integer instead?

I have checked the .ffs file and it seems like that's the case. Is there any way to change the data type to a 64-bit integer instead?

You should be able to set that on the writer feature type. However, it looks like you're updating an existing table, in which case I'm not sure changing data types is allowed (or advisable)

Reply


Community Stats

30,363
Posts
115,370
Replies
38,145
Members
Terms & ConditionsCookie 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.