This database is currently in use by another person or process and cannot be accessed at this time. In order to share a Notes database it must be accessed via a Domino Server by all users of the database.

< Back

Document Subject: This database is currently in use by another person or process and cannot be accessed at this time. In order to share a Notes database it must be accessed via a Domino Server by all users of the database.
Hint Short Cut: Add this to your code & documentation to help you find this page.
http://#InUseByAnotherPerson or http://A555F9/nn.nsf/ByAlias/InUseByAnotherPerson
This error can come up for a variety of reasons - here are the details and the fix.

This error can come up in the client or in the web browser.

Error 500 This database is currently in use by another person or process, and cannot be accessed at this time. In order to share a Notes database, it must be accessed via a Domino Server by all users of the database.

This means that a database is being accessed by somebody or some other process already and cannot be accessed by the user or the server.

If the database is on a file server or file share as opposed to an actual IBM Lotus Notes Domino Server then the fix is that the database needs to be hosted on a server.
If you need help with this, I can help.
Notes databases need to be hosted on a server if more than one user will access it.

The more common way that this error crops up is when a user or a process such as a backup process or fix up process is interrupted by a network event or hardware fault, and a lock file is created and not cancelled correctly.

The lock file is ~notes.lck and lives in the domino data directory. eg C:\Program Files\IBM\Lotus\Domino\data
To fix this close down the notes server and any backup tasks.

The ~notes.lck file should be deleted automatically. If not delete it, then restart the server.

This can also be caused by virus checkers.
HCL suggest excluding notes directories from virus checking. https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0093046

Another possible remedy from https://entwicklercamp.de/customer/notesini.nsf/9fa909b7805d6afdc1256c530048a08b/9987e0e861e0d4a3c125814f0030bc6b?OpenDocument
add OSFDG_FILELOCKING_METHODTWO=1 to the server notes.ini.