DButler
asked on
How to Unlock an Inappropriately Locked Document in ND6.x.
I was editing the main configuration document in Symantec Anti-Virus for Domino (version 3.1) when my client crashed. Now, Notes is refusing to let me edit the document -- saying that the document has been locked by my ID.
The only useful documentation I've been able to find on this so far is that (being the user who locked the document) I should be to unlock it by going <Actions><Unlock Document>. That option is present on the pull-down menus, but is not selectable.
We can try a server reboot, but I'd rather find a more elegant solution.
My client is version 6.0.3. Server is running version 6.5.1.
Thanks in advance.
Doug
The only useful documentation I've been able to find on this so far is that (being the user who locked the document) I should be to unlock it by going <Actions><Unlock Document>. That option is present on the pull-down menus, but is not selectable.
We can try a server reboot, but I'd rather find a more elegant solution.
My client is version 6.0.3. Server is running version 6.5.1.
Thanks in advance.
Doug
If you are using 6.5 client then you could use this notes.ini parameter
EDIT_NO_SOFT_LOCKS=1
There was similar problem and lotus reported it is addressed in 6.5.1 .. Not sure if that would help you..http://www-1.ibm.com/support/docview.wss?rs=899&uid=swg21100606
~Hemanth
EDIT_NO_SOFT_LOCKS=1
There was similar problem and lotus reported it is addressed in 6.5.1 .. Not sure if that would help you..http://www-1.ibm.com/support/docview.wss?rs=899&uid=swg21100606
~Hemanth
ASKER
qwalatee: Interestingly, document locking was not turned on for the DB.
Hemanth: Unfortunately, the documentation referred to multiple users accessing a document (in this case, it was the same ID), or how a manager could unlock the document (which we could not). <sigh>
We eventually just rebooted the server.
My apologies to the both of you for the slow response.
Hemanth: Unfortunately, the documentation referred to multiple users accessing a document (in this case, it was the same ID), or how a manager could unlock the document (which we could not). <sigh>
We eventually just rebooted the server.
My apologies to the both of you for the slow response.
Did reboot release the locks ??
ASKER
yes.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I had an experience with one database that always thought it had locked documents, when it really didn't. The only solution was a rebuild.