Tay Posted December 17, 2012 Report post Posted December 17, 2012 My console crashes on a regular basis and then I am not able to open an object that I was modifying. Does anyone know how I can kill the object in question so I can edit it? Even after a reboot it is still in use and I need to get this package out asap. Thanks! Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted December 17, 2012 Report post Posted December 17, 2012 I had this problem only once after a console crash, but this is what helped me. Look in the comments section how te edit the SQL table. Quote Share this post Link to post Share on other sites More sharing options...
Tay Posted December 17, 2012 Report post Posted December 17, 2012 Thanks Peter but I already tried that. Says Select * from SEDO_LockState is invalid or something. Quote Share this post Link to post Share on other sites More sharing options...
Peter33 Posted December 17, 2012 Report post Posted December 17, 2012 Did you select the SCCM databse in the object explorer before creating the query? Otherwise you will get the error you described because the table can't be found. Quote Share this post Link to post Share on other sites More sharing options...
Tay Posted December 17, 2012 Report post Posted December 17, 2012 Thanks! Quote Share this post Link to post Share on other sites More sharing options...
hollisorama Posted May 9, 2013 Report post Posted May 9, 2013 This worked for me as the link in the article states You can manually unlock these if the application crashed and you just don’t want to wait.All you have to do is open sql server management studio and run Select * from SEDO_LockState Find the id and place it into the below sql statement and run. delete from SEDO_LockState where id=’PLACE ID FROM ABOVE HERE’ Quote Share this post Link to post Share on other sites More sharing options...