Domino errors "Insufficient system resources..." or "This database is currently being used"
A Domino server on Windows returns the following error:
"Insufficient system resources exist to complete the requested service".
The server has several hundred GB of databases.
Additionally, the following related error is sometimes reported:
This database is currently being used by someone else. In order to share a Notes database, all users must use a Domino Server instead of a File Server.
Resolving the problem
|Check for conflicting software|
There are several possible causes for this issue; however, the most common cause is a conflict with virus scanners, backup software, or other third-party software accessing the files. These applications can hold a Domino database open and cause the error to appear when a Notes client attempts to access the file.
|Page pool limit|
Domino maintains a database cache to improve performance by keeping recently used files open for quicker access (avoiding constant disk reads and writes). As many large Domino applications (databases) are open, the size of the database cache can increase. If the database is closed by the client, it may still remain in the Notes database cache, and as a result still occupy memory in the Windows Page Pool. By opening many large files at a time, it is possible to run into the Page Pool limit and encounter the error described above.
Upon startup of the Domino server, you see an increase in the Page Pool. Domino Agent Manager does scan databases (by opening, reading agent schedule information, and closing). The address book is opened always, mail files and MAIL.BOXs might be opened as well. These would all account for Page Pool spikage. But, as the regular databases or the mail files are closed, the operating system's page pool should shrink. Also, the Db Cache will keep files opened hours after the users of that database have closed their sessions. You can control this with the INI parameter mentioned below in the "Temporary workaround" section.
To maintain the same number of databases and concurrent users on the server, the Notes database cache can be adjusted or eliminated by using the following temporary workarounds:
- To disable the cache, implement the server NOTES.INI parameter NSF_DBCACHE_DISABLE=1. NOTE: This setting will prevent Domino from taking advantage of the database cache, and will require more frequent disk access for opening databases. When using this option, monitor the server's performance as this could have a very bad affect. Also, if the server is also a Domino HTTP server, performance may suffer dramatically.
- To reduce the database cache, implement the server NOTES.INI parameter NSF_DBCACHE_MAXENTRIES=n [maximum number of databases allowed in the database cache at one time.]
To see what is currently in the database cache, and how many databases are cached, type "dbcache show" at the server console. This will display the list of databases currently in the cache, and the maximum number of entries allowed.
- Schedule the execution of the command "dbcache flush" during peak access times.
These actions listed above are considered a temporary workarounds only, intended to allow time to take the necessary measures to resolve the source of the problem.
1. Start Registry Editor (Regedt32.exe)
2. Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management
3. On the Edit menu, click Add Value, and then add the following registry value:
Value name: PoolUsageMaximum
Data type: REG_DWORD
Value data: 60
Setting the value at 60 informs the Memory Manager to start the trimming process at 60 percent of PagedPoolMax rather than the default setting of 80 percent. If a threshold of 60 percent is not enough to handle spikes in activity, reduce this setting to 50 percent or 40 percent.
Value name: PagedPoolSize
Data type: REG_DWORD
Value data: 0xFFFFFFFF
Setting PagedPoolSize to 0xFFFFFFFF allocates the maximum paged pool in lieu of other resources to the computer (~500 MB).
Caution The 0xFFFFFFFF PagedPoolSize setting is not recommended for use on 32-bit Windows Server 2003-based computers that have 64GB of RAM. This will potentially bring the Free System PTE entry down and can cause continuous reboot of the computer. For this configuration, carefully choose a value based on the requirements and available resources.
4. Quit Registry Editor.
5. Restart the server for the changes to take effect.
|Windows NT, 2000|
|You May Not Be Able to Copy Large Files on Computers That Are Running Windows NT 4.0 or Windows 2000
"With the standard kernel, 1 kilobyte (KB) of paged pool is required for each megabyte (MB) of file size that is opened for buffered I/O. Because there are two files involved in a copy procedure, 2 KB of paged pool are required for each MB in the source file. When the PAE kernel is used, the overhead is doubled and 4 KB of paged pool is required for each MB in the source file.
Service Pack 2 (SP2) for Windows 2000 contains a fix for this limitation. The kernel memory manager has been altered with respect to management of paged pool memory when files are opened for buffered I/O. This change permits buffered operations on arbitrarily large files and therefore permits arbitrarily large files to be copied by any utility that uses the CopyFileEx function. "
Memory Limits for various Windows Releases