Showing posts with label SEDO_LockState table. Show all posts
Showing posts with label SEDO_LockState table. Show all posts

Wednesday, September 23, 2015

Cannot edit the object, which is in use by User at Site XYZ

During Edit Membership on Software Updates I get the following error message: Cannot edit the object, which is in use by User at Site XYZ. This because the ConfigMgr console was crashing while editing the object.

The following must be done to free the object again. The query for this is: select * from SEDO_LockState where LockStateID <> 0 (where SEDO stands for Serialized Editing of Data Objects)

Use the appropriate information to remove the record related to the object. The query for this is: DELETE from SEDO_LockState where LockID = ‘<LockID of the record identified in the previous query>’

Once the record is removed, you should be able to modify the object again. Hope it helps!

Wednesday, September 25, 2013

Unlocking ConfigMgr 2012 Objects

When removing objects in ConfigMgr the following message is displayed: "Cannot edit the object which is in use by <?>". This happened as the result of the ConfigMgr console crashing while someone had the object open.

ConfigMgr 2012 handles editing of objects through something called “SEDO” or “Serialized Editing of Data Objects.” Object locks can be found in the SEDO_LockState table in the ConfigMgr database.  You can locate the record in question by searching for LockStateID that’s not zero, or by the user ID that ConfigMgr says is editing the object (‘AssignedUser’).  An example query would be: select * from SEDO_LockState where LockStateID <> 0

Simply use the appropriate information to remove the record related to the object*. For example: DELETE from SEDO_LockState where LockID = ‘<LockID of the record identified in the previous query>’ Once the record is removed, you should be able to modify the object again. Hope it helps!