Failure UPDATING existing versioned ArcPro sde table with Esri Geodatabase (ArcSDE Geodb) writer.

A couple of things to check:

1. Do you have 64 bit background geoprocessing installed (if using arcmap)
2. Are your FME and Esri versions compatible? - https://community.safe.com/s/article/notes-on-fme-and-esri-versions-and-compatibility

There's a discussion about the same issue here:

https://community.safe.com/s/question/0D54Q000083BMHUSA4/how-to-solve-this-error-message-the-error-number-from-arcobjects-is-2147024893

Hi hkingsbury,

1. I have ArcDesktop 10.8.1 installed on my computer which appears to have 64-bit background geoprocessing out of the box. That being said, the workbench I am running is utilizing ArcPro (Installed ArcGIS version is '2.9.5').
2. I am using: Current FME version: FME 2022.2.0.0 (20221103 - Build 22765 - WIN64) which appears to be compatible with the ESRI version I am using (ArcPro 2.9.5) and ArcSDE 10.0.

Let me know if this answers your checks.

Redownloaded 64-bit background geoprocessing to test this theory and this did not appear to affect the result.

From what I can tell, FME and Esri versions are compatible as well (FME 2022.2.0.0) + (ArcPro 2.9.5).

Any other thoughts?

A couple of checks you could do is:

1. check that you can make the edits in ArcMap
2. check that you can make edits to other versioned tables in FME
3. disabled versioning, check edits work, then enable versioning again and check if edits still work

Hi hkingsbury,

1. The table is ArcPro online as it is configured for use with Attribute Rules. The following is the message I receive when I attempt to open in ArcMap:
2. I received the same error (Error while updating feature in the table/feature class 'GISADM.RD_ROADNAME'. The error number from ArcObjects is: '-2147207389'. The error message from ArcObjects is: {}) when trying to edit another versioned table in FME
3. I am beginning to think the issue revolves more around the ArcPro Attribute Rule error opposed to the table being a versioned dataset. As I will have to involve other departments to toggle the versioned status, I will explore this route before testing the versioning (turn off).

Thanks!