topic Re: Lock request conflicts with an established lock after updating to 10.1 in ArcGIS API for Silverlight Questions

Lock request conflicts with an established lock after updating to 10.1

tandrews — Fri, 12 Apr 2013 15:09:24 GMT

Hi all,
I'm in the process of cutting over from 10.0 to 10.1. In the new 10.1 environment I'm finding that when performing more than one update to a feature via my Silverlight application I'm receiving this error:

{Error code '400': 'Unable to complete operation.'
Lock request conflicts with an established lock [dbo.DEFAULT]}

After some yet to be determined timespan the lock will release and I'll be able to perform the subsequent edit. I never experienced this behavior in 10.0, I understand that this could be a configuration issue with the feature services that have been deployed but I'm on the development side of the equation and have little to no knowledge regarding configuration and publishing of those services. Anyone have any idea why this may be occurring or how I may be able to best correct or troubleshoot this issue?

Thanks

Re: Lock request conflicts with an established lock after updating to 10.1

arethasamuel — Tue, 30 Apr 2013 23:40:42 GMT

I also have this same problem, can someone help please?

Re: Lock request conflicts with an established lock after updating to 10.1

KathleenBrenkert — Mon, 06 May 2013 18:49:09 GMT

Same issues here. I have a flex site where my users can attach files to a table. It's been working until today, as of today when they go to attach they get a fault code 400, lock request conflicts . I can't find answers anywhere, we have service pack 1 installed. It seems to only happen when we attach a file, they can update attributes and even add records. It seems to take longer than an hour for the 'lock' to get released.

Re: Lock request conflicts with an established lock after updating to 10.1

achrafamine — Mon, 16 Sep 2013 11:31:50 GMT

i have the same issue, i m flex viewer application, any help please

Re: Lock request conflicts with an established lock after updating to 10.1

ChrisSeabrooke — Fri, 20 Sep 2013 15:18:49 GMT

Has anyone figured this out? I'm using API 3.0 for Silverlight with Silverlight 5. The server is ArcGIS 10.1. I'm getting this error when editing -- deleting or creating records. We thought ArcGIS for Server supported concurrent editing?

Re: Lock request conflicts with an established lock after updating to 10.1

JamesGraham — Wed, 23 Oct 2013 12:24:17 GMT

A similar message occurred for me this morning. Because I had an ArcGIS Server service pointing to this feature class (with update, delete privileges), I couldn't get an exclusive lock on it and got this message.

The solution for me was to log in to ArcGIS Server and stop the feature service, edit/modify the SDE featureclass as necessary, save then go back to ArcGIS Server and restart the feature service.

Hope this helps!
James

Re: Lock request conflicts with an established lock after updating to 10.1

Devi_NoorOktarina — Mon, 11 Nov 2013 23:54:46 GMT

Hi All, I also have the same problem.

Regarding save edits, I found error messages from ArcGIS Server as follows:

"Error code 400: Unable to complete operation.
Lock request conflicts with an established lock [X.Do1][STATE_ID = 64638]"

or

Error code 400: Unable to complete operation.
State in use -- definition being modified [X.Do1][STATE_ID = 64744]

These errors occured randomly. If this error happens, another user session must wait over hours to continue edited by other users.

Can anybody help please?

Re: Lock request conflicts with an established lock after updating to 10.1

KhairulAmri1 — Tue, 19 Nov 2013 04:39:21 GMT

I got same problem, and the solution is deleting inactive session in geodatabase

Re: Lock request conflicts with an established lock after updating to 10.1

AamirSuleman — Wed, 30 Apr 2014 18:41:05 GMT

Anyone knows why this may be happening?

Re: Lock request conflicts with an established lock after updating to 10.1

JonBeets1 — Tue, 10 Jun 2014 12:55:51 GMT

I am also having this issue. The Schema lock setting does not fit it.

Re: Lock request conflicts with an established lock after updating to 10.1

BrianBorg1 — Tue, 11 Nov 2014 15:02:02 GMT

We are facing the same issue. Any one managed to find the cause of this issue and the solution please?

Re: Lock request conflicts with an established lock after updating to 10.1

JenniferNery — Wed, 26 Nov 2014 18:57:32 GMT

This seems to be a question for ArcGIS Server Team (FeatureServices). Upon forwarding your question to them, these were their follow-up questions.

I assume that the data is versioned.
If multiple people are editing the same data at the same time then this error can happen. The code should re-attempt several times before getting the error.
For this one user, can they repro this issue easily? If so, can you send is the logs?
Have they versioned the data between 10.0 and 10.1? Or have they increased the load on the server between 10.0 and 10.1?

Thanks.

Jennifer

Re: Lock request conflicts with an established lock after updating to 10.1

JonBeets1 — Mon, 05 Jan 2015 01:34:36 GMT

After trying several things I was able to resolve this issue for myself. Turns out the feature attribute fields were not formatted correctly when I created them and when the web server was accessing them is assumed correctly formatted fields thus locking up the database when it tried to write to the database. I deleted the feature datasets then recreated them in the database and the problem disappeared.

Re: Lock request conflicts with an established lock after updating to 10.1

deleted-user-pKf68H-QZnoZ — Mon, 24 Jul 2017 13:39:21 GMT

I know this is an older post, but it is still a relevant issue.

The solution is to login to the ArcGIS server manager, edit the map service you're experiencing issues with, click on parameters, and uncheck " Lock Database Schema". Then press Save and Restart.

Re: Lock request conflicts with an established lock after updating to 10.1

JoanKeene — Fri, 04 Aug 2017 16:03:24 GMT

Exactly what I needed! Thanks.