I have a ESRI Geodatabase (ArcSDE Geodb) writer which is returning:
An error occurred while attempting to start an edit session. The error number from ArcObjects is: '-2147217150'. The error message from ArcObjects is: {The current version does not support editing (base, consistent, or closed) [An open transaction was detected. All user transactions must be closed prior to StartEditing.]}
The problem is there are no locks on this feature class layer so no open transactions?
Hello @tfsrichard
This is an interesting error. Are you able to Start an Editing session in ArcMap to that versioned table, without issues?
Is the version type also set to transaction as outlined here: https://support.esri.com/en/technical-article/000009044
Hello @tfsrichard
This is an interesting error. Are you able to Start an Editing session in ArcMap to that versioned table, without issues?
Is the version type also set to transaction as outlined here: https://support.esri.com/en/technical-article/000009044
Hi @trentatsafe,
Yes I can start editing in ArcMap without issues.
It's the instance default version which is transactional.
I am getting this same error too. @tfsrichard were you able to resolve this?
Hello @tfsrichard
This is an interesting error. Are you able to Start an Editing session in ArcMap to that versioned table, without issues?
Is the version type also set to transaction as outlined here: https://support.esri.com/en/technical-article/000009044
I am successfully able to start an edit session in ArcMap to that versioned table without any issues. I also ran the workspace from the FME Desktop as well as a FME Server (both in different machines) and am getting the same error, "An error occurred while attempting to start an edit session. The error number from ArcObjects is: '-2147217150'. The error message from ArcObjects is: {The current version does not support editing (base, consistent, or closed) )An open transaction was detected. All user transactions must be closed prior to StartEditing.]}"
I resolved this error in my workspace. My workspace was using a featurewriter to open a versioned edit session to write to the default version while another writer was trying to write to a transaction table. I used a featureholder to hold the transactions until the featurewriter is done with the versioned writes and then routed the features for update to the transaction table. This successfully resolved the issue.
Here is the snip from my workspace
