Select to view content in your preferred language

Reconstruct from seeds - User session application lock in progress error

152
3
2 weeks ago
Labels (1)
NateArnold
Frequent Contributor

User attempted reconstructing from seeds after shrinking them for line cleanup.  Pro did not complete the operation but did not error - just endless progress dialog box.  User then cancelled the operation and is now unable to try again.  The error message reads:

Screenshot 2025-06-10 at 10.52.47.png

 Edit operation failed.

Message: User session application lock in progress - operation not allowed.

 

Corresponding error messages from the service logs:

Screenshot 2025-06-10 at 10.55.46.png

 

Restarting the service does not resolve this issue and the user is not able to proceed.  Any ideas on what to try next?  

Tags (3)
0 Kudos
3 Replies
AmirBar-Maor
Esri Regular Contributor

@NateArnold 

With branch versioning a version can only be edited by one editor. The editor who is the first to start the edit will be able to edit it and anyone else will be locked out.

Did you check the locks?

Locks are explained in this help topic -administrators can 'purge' the lock (any unsaved edits will be lost) by disconnecting the user.

if this is not the issue, and/or if you can reproduce it, please contact technical support

0 Kudos
-_Ashley-B-Potter_-
Frequent Contributor

@NateArnold  @amiutami  We encounter similar issues as Nate. After investigation, I have determined that these are often caused by user errors. For example, some users only perform reconciliation without completing the R&P process, which can lead to system lock-ups. Typically, the system may resolve the issue overnight, but this is not always practical given our time constraints.

0 Kudos
NateArnold
Frequent Contributor

Thank you for the link.  I did not check the locks on the geodatabase but will if/when it occurs again.  The short term solution was to have the editor delete their version and create a new one, then they were able to create seeds and continue editing.  I will open a support incident next time.

0 Kudos