While attempting to update design steps the user is receiving: The object is locked by: . This is the same user so it should not be locked. I have turned off the Lock_Timeout in the Site Admin but it still is not releasing the lock. Has anyone seen this before and how do you resolve this.
Items get locked in this way for various reasons. The most common reasons are: - User session timed out while the item was open, - User failed to logoff the project correctly (closed the browser using the X), - User's browser session was interrupted due to clicking a link in an email (for example), - Browser encountered an error and had to shut down.
Removing the lock from the locks table is the best method. Also, the lock may drop on its own when the Lock_Timeout is reached. Restarting the services would also remove the lock.
Great, thanks for the feedback. We have been having LDAP errors where the user is getting kicked out. As you mentioned the item gets locked and I have followed your suggestions and that has solved the problem. Thanks!
One note: Please keep in mind to return the Lock_Timeout back to the default value or some reasonable value. This value should not be small because then you can get the trouble with editing of records with a lot of users.
When i tried to set Status from Work in Progress to Fixed under Defects, The Error displaying The Object is Locked by: The same user logged In. Solution: Go to Attachments -> Take a Test Snap Shot of other window -> Now try to change status. It should work.
removing the lock is a good method. If you have version control on, and the particular item s checkout, you can undo-checkout (right click - versions - undo checkout) Thsi way you can release the object but the changes made by the previous person (who had teh lock) will be lost
I am also facing the same problem. Only thing i would like to confirm here is that when locks table is flushed, does it flush only idle users or all the users from that QC Instance. Is there any way to kick out all the idle users after a specific time.
The Locks table is project specific. So a complete "delete from locks" command will only release the locks from that single project and not all projects. You can also qualify the command like 'delet from locks where user_name = 'abc'' in order to delete a specific lock without releaseing other locks.
The Idle Users issue is a different issue. The Site Config parameter Wait_Before_Disconnect handles this. When a user session is idle past the amount of time specified in this parameter, the user's session will be automatically disconnected. It is not recommended to set this value less than 10 min. You can also cancel user sessions using the Site Connects tab within Site Administration.