Issue with default doc locking feature of a standalone database

When I try editing a document (standalone database) I get the message ‘This document is already being edited by , Please try later.’

However I have not got it in edit mode anywhere, and am not able to get rid of it, as there is no way to track/release (as far as I know) the document.

Any ideas around this would be grateful.

Subject: Issue with default doc locking feature of a standalone database

What happens when you remove the document locking option temporarly?

Subject: RE: Issue with default doc locking feature of a standalone database

As I said it is just the default locking functionality (Application is standalone & does not have any replicas) which does not need the option ‘Document locking’ to be enabled.

The document locking for standalone copy, is available by default, but the problem is there is no info/. to track if it is locked (no fields having the info about the locking)

So I would like to know, how to release this document from locking…

Thanks for your response in advance…

Subject: RE: Issue with default doc locking feature of a standalone database

What I was trying to tell you is this: I think that document locking is only applied to a db when this option is set. So when you complain about a doucment that cannot be released, I suggested to remove the locking option and see what happens. But when you already do not have locking set in your db, this trick will not help you at all.

You might try to make a copy of the database and see what happens then. And did you try fixup, compact, etc?