Strange locking error when using REST api through ArcServer

KevinGooss — Mon, 12 May 2014 13:59:13 GMT

I keep getting this message:

 "error": {
  "code": 400,
  "message": "Unable to complete operation.",
  "details": [
   "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.]"
  ]
 }
}

when i try to create feature via the REST endpoint on a Feature Service using the addFeatures method.
It appears to be related to some kind of ArcSDE locking.
This is a 10.1 arc server install using Oracle
I can get the edits to work once in a while, and some times for an hour or two on end. but then it breaks again.
i confirm in catalog that there are no locks on the sde connection used in the mxd for the feature service.

I thought edits through the REST api would handle the opening and closing of the edit session.
I never explicitly call "StartEditing" i just craft a string request in C# to send to the rest endpoint.

What is going on here?

Re: Strange locking error when using REST api through ArcServer

AaronHeyman — Tue, 13 May 2014 18:19:46 GMT

I had some locking issues with MS SQL. Try setting the service pooling

"Maximum number of instances per machine:" to 1.

If that fixes your problem the issue might be related. There was a patch available.

Re: Strange locking error when using REST api through ArcServer

jonathanrobinson — Wed, 14 Jun 2017 23:44:13 GMT

Hello, did you find a fix for this issue?

topic Strange locking error when using REST api through ArcServer in ArcGIS Enterprise Questions

Strange locking error when using REST api through ArcServer

Re: Strange locking error when using REST api through ArcServer

Re: Strange locking error when using REST api through ArcServer