Doc locked but we don't use locking (with addendum)

HCL Domino Domino Forum
1

We’re getting the following Notes error on one doc in a db:‘This document is already locked by ’.

The db locking property is not set.

There is no code in the form that uses @DocLock.

When I turn on the debugger, I’m not seeing any code that seems to reference locking and the error is from Notes, not my code.

I’ve searched on the error and have only seen one hit and it was back in '03 for Notes 6.0.

??

Not sure where to look next - any assistance is greatly appreciated.

Doug

addendum:

I switched to the owner of the lock, did an edit/save, switched back to my id and the lock still exits.

2

Subject: Doc locked but we don’t use locking (with addendum)

Try removing the fields “$Writers” and “$WritersDate” if it existsCall doc.RemoveItem( “$Writers” )

Call doc.RemoveItem( “$WritersDate” )

or use the savetodiskproperty on these items to false.

3

Subject: <duplicate - sorry>

4

Subject: Doc locked but we don’t use locking (with addendum)

There is a poorly documented “feature” called “soft locking” which can only be disabled on a client-by-client basis:

http://www-1.ibm.com/support/docview.wss?uid=swg21174820

There are also some Technotes that address documents that are locked incorrectly and, in some cases, what to do about it.

5

Subject: Response to all

No $KeepPrivate or $Writers.Db is not and has never been configured to allow hard locking.

I’m dead confused about soft locking - we’re at 6.5.4 so this is something that should ‘just happen’ and, I’d think, prevent the creation of rep/save docs. We get rep/save docs. This is the first occurrance of an apparently locked doc in this way. Opening and resaving as the lock owner did not release the lock. I’d think if this was a ‘feature’ of the soft lock, we’d either not have rep/save errors or I’d have more folks complaining about locked docs…

Since we no longer use Notes for mail, doing the ‘send a button’ thing isn’t gonna work to update the ini file. I’ll probably build a db with a post open event that does the deed and ask folks to just open the db.

Weird.

Thank you all for your replies.

Doug

6

Subject: Follow on about the tech note

Is this an ‘email db’ feature or an ‘any db’ feature? The tech note seems to be related to ‘messaging applications’ so I can’t tell if this only affects user mail dbs or any db.

Anybody know for sure?

Thanks.

Doug

7

Subject: RE: Follow on about the tech note

Hi Doug,

From my experience, it is email and db related.

For email db, you will have the behavior in a mail-in db accessed by many users at the same time.

For mail-in db my experience was:

Opening document or composing memo based on stationery results in error: ‘The document is already locked…’

http://www-1.ibm.com/support/docview.wss?rs=0&q1=1100606&uid=swg21100606&loc=en_US&cs=utf-8&cc=us&lang=en

For application db, you will have the same behavior.

The behavior will occurs when the document is in edit mode, access on the same replica, on the same server.

It will not prevent replication conflicts, if 2 users access the same documents in edit mode in the same replica on 2 different servers.

JYR

8

Subject: RE: Follow on about the tech note

All dbs are on a single server in a single building. We have a cluster server but users don’t access the cluster server (it’s configured to bounce them back to the main server if they try).

So we probably shouldn’t be seeing rep/save errors but we do.

The docs in question are created via a LS agent, but the agent does not open the UI doc so the tech notes don’t seem to fit; that and the error was fixed in 6.5.2 and we’re at 6.5.4.

I don’t think most users know about using to open docs in edit mode but who knows…

It’ll be interesting to see if this happens again.

Thanks for the reply. Still confused.

Doug

9

Subject: This worked for me…

For the user that appeared in the message (for a stationery item in a mailin database), I had them hit F5 to lock Notes. This cleared the message.

10

Subject: Doc locked but we don’t use locking (with addendum)

Doug,

Was the document created when document locking WAS on?

Is there a field on the document (similar to $KeepPrivate for example - I’m not that familiar with doc locking and what field Notes uses to lock the document) that needs to be removed?

Mike