I have done all sorts of testing to figure out what is causing this error randomly in my application without success. What I have found though is that by making a copy of the document in question results in the lock being cleared.
I copied/pasted all the documents that were locked and deleted the locked versions leaving only unlocked editable documents.
If anyone can give me a good reason why random documents are being locked and how to clear them some other way I would sure like to hear it.
Oh yeah, the Allow Document Locking option was always unchecked which I am assuming means that it should not have locked anything in the first place.
I sure hope IBM/Lotus figures out that this is a huge problem and fixes it in 6.5.3 as I have the issue in 6.5.1 and 6.5.2 is already released.
Subject: RE: Document is already locked by … (solution)
I would have created a button to do the unlock process but the database is not set to allow document locking. According to the documentation that function only works if the database allows locking.
Maybe the reason I can copy/paste is because it is not set to be able to lock.
I still see no reason why the lock is enabled if the flag has never been set. To me this is a bug.
Subject: [IBM Technote] Document is already locked by … (solution)
The bug is well investigated in the technote IBM 1100606.
Title :
“Opening document or composing memo based on stationery results in error: 'The document is already locked…”
This issue is relative to the use of Soft Locking. Soft Locking goes into effect when a document is opened in Edit mode. In cases where a document is closed while still in Edit mode the document is not unlocked.
An additional scenario also exists. The second scenario is related to the fact that new documents created in the back-end (including User Interface triggered LotusScript code) are assigned a NoteID of 0. When two or more users create such documents, each document they create has a NoteID of 0. The soft locking feature locks documents based on the NoteID; so, even though there are two (or more) different documents, the soft locking feature recognizes only that NoteID 0 is already locked.
The issue relative to soft locking and new back-end documents was reported to Quality Engineering as SPR# KHAN5U4NVZ and was fixed in Domino 6.0.4/6.5.2 and 7.0. The fix resolves a number of scenarios where soft locking errors were encountered, including the one involving the use of Stationery in a mail file.
Subject: RE: [IBM Technote] Document is already locked by … (solution)
Still happening in 7.0.2. We constantly at work get documents locked when no one is in them. The last person to edit them is the name that comes up that says has it locked. This is really a pain in the pumpkin. Not everyone has rights to unlock but a button with code to force it unlocked and the people that do have rights are not here all of the time and it really interferes with our work. Its definatly a soft lock issue and frequently does not let go of the document. We need the locking in our business (tech support) but we need it to work properly. Any help is greatly appreciated.
After many months of relative peace, IT’s started happening again with us too. We moved the servers form 6.5.4 to 7.0.2 in Nov 07. We’ve had other problems too, with this version, like a bug in the MIME to CD conversion serverside.Clients are still running 6.5.1 for the most part.
Anyone know reliably if it’s resolved in 7.0.3 ? Mind you, how do you know, until it happens ? I rephrase : anyone come across it in 7.0.3 ?
And Bill Malchisky posted in February that it’s made it into ND8.
That is NOT good news.
I must say it’s not easy, tracking a bug through the Domino versions. Maybe each should come with a NOTFIXED List or even a REINTRODUCED List.
Looks to me like the only solutions, at the moment, if you want to be sure (is that still a word ?) of steering clear of this bug, are either to fully implement locking (a lot of work) or else disabling on the clients. I don’t specially want to do either.
@DocLock([UNLOCK]) has done nothing at all to help in my case, the doc remains obstinately locked. Even when the locker opens and recloses, still locked…
Also, our scenario is not related to new documents, it’s affecting docs already saved.