topic Re: Error 400: Unable to perform applyEdits operation in ArcGIS JavaScript Maps SDK Questions

Error 400: Unable to perform applyEdits operation

CraigMcDade — Tue, 16 Apr 2013 14:23:21 GMT

I am doing a very simple modification to the default editor sample whereas I have simply inserted my feature service and adjusted the extent.

When I try to add a feature I am getting the following error in firebug:

{"error":{"code":400,"message":"Unable to complete operation.","details":["Unable to perform applyEdits operation."]}}

I have checked and everything is running properly through the proxy.

Any ideas why I could be getting this error? When I attempt to add a point the progress bar runs but then the point does not add and the error appears in firebug.

Re: Error 400: Unable to perform applyEdits operation

CraigMcDade — Tue, 16 Apr 2013 16:40:52 GMT

I am getting two additional errors in my ArcServer Logs:

- a database error occurred
- objects in this class cannot be edited outside an edit session

Re: Error 400: Unable to perform applyEdits operation

JoshWhitman — Thu, 30 Jan 2014 20:33:26 GMT

We had the same error show up and the problem seemed to be stemming from the feature class being m-aware without the necessary attributes.

Might not always apply to everyone having a this problem, but that was the issue for us.

Re: Error 400: Unable to perform applyEdits operation

GaneshSolai_Sambandam — Fri, 31 Jan 2014 07:32:54 GMT

We had the same error show up and the problem seemed to be stemming from the feature class being m-aware without the necessary attributes.

Might not always apply to everyone having a this problem, but that was the issue for us.

Hi
I had the same problem yesterday, and I was able to apply edits to few of my feature layers successfully and 2 of them I couldn't and I got the same message. Although my post request on the firebug status show 200 status, but the JSON response text in firebug
shows unable to apply edits. I think, I almost figured out the problem. The problem is with the particular feature class in the geodatabase and it is non-versioned. It is worth opening the featureclass in Arcmap and start editing the featureclass, if it shows the featureclass is non-versioned, then you cannot apply edits.

Please try this and let me know whether you are successful.

I will investigate from my side and let you know once successful.

Regards
Ganesh

Re: Error 400: Unable to perform applyEdits operation

GaneshSolai_Sambandam — Fri, 31 Jan 2014 11:22:42 GMT

Hi
I had the same problem yesterday, and I was able to apply edits to few of my feature layers successfully and 2 of them I couldn't and I got the same message. Although my post request on the firebug status show 200 status, but the JSON response text in firebug
shows unable to apply edits. I think, I almost figured out the problem. The problem is with the particular feature class in the geodatabase and it is non-versioned. It is worth opening the featureclass in Arcmap and start editing the featureclass, if it shows the featureclass is non-versioned, then you cannot apply edits.

Please try this and let me know whether you are successful.

I will investigate from my side and let you know once successful.

Regards
Ganesh

HI
I versioned the ARCSDE feature class and it is working fine. For some reason, the feature class within ARCSDE was corrupted even
though it was versioned before. I export feature class as xml workspace document and reimported back into the ARCSDE geodatabase and versioned the newly imported feature class and it is now working perfectly alright on web editing.

Regards
Ganesh

Re: Error 400: Unable to perform applyEdits operation

SandraMargriter — Tue, 04 Feb 2014 22:51:54 GMT

I started getting that error message after I enabled archiving for an SDE feature class. After disabling archiving and then republishing the service, I no longer get the error message "Unable to perform applyEdits operation."

Re: Error 400: Unable to perform applyEdits operation

ThomasRoussell — Wed, 18 Jun 2014 18:32:42 GMT

I had a similar problem and here are the steps I took to resolve it.

I tried exporting to XML Workspace and File Geodatabase and then re-importing but that did not work so I did this:

Export to Shapefile
Delete OBJECTID
keep Repairing Geometry until no errors remain
Import into SDE
Rename fields and aliases that were corrupted during export to shape file.
Reset Domains on Fields
Register as versioned
Create MXD
Share as service and under Pooling set "maximum number of instances per machine" = 1