Reached the maximum number of locks" Sage 50 error explained
Sage 50 is telling you it has run out of internal locks on the database, usually because the company file is too large or busy.
The message reads:
The program cannot complete this transaction because it has reached the maximum number of locks that it can place on the database.
Despite the wording, this is rarely about locks in any sense you can fix by hand. Sage 50 keeps a fixed pool of internal locks it places on records while it works. When a posting, a large save, or a year-end close touches too many records at once, that pool runs dry and the program stops rather than risk writing half a transaction. In plain terms: the operation you asked for is bigger than the program can safely hold open at one time.
Why it happens
The usual cause is size. A company file that has grown over many years holds more records per account, per period, and per list than the lock pool can cover in a single pass. Large batch postings, long-running reports that post, and year-end processing are the classic triggers.
Contention makes it worse. If several users share the file over a network, locks from their open sessions add to yours. A damaged or badly fragmented database can also inflate lock usage, because the program retries and re-locks records it would normally touch once.
Close other sessions and retry
Have every other user exit Sage 50, then restart your own workstation and try the operation again. On a single-user file this alone often clears it, because the pool resets when the program starts fresh. If it recurs on the same step each time, size or damage is the likely reason.
Break the work into smaller pieces
If the failure happens during a large posting or a batch, split it. Post a month at a time instead of a quarter, or save a long entry in smaller transactions. This keeps each operation inside the lock budget. It is a workaround, not a repair, but it can keep you working while you decide what to do about the file itself.
Back up before anything else
Before running maintenance, verification, or any third-party tool, take a full backup of the company file and keep it somewhere safe. Lock errors can be an early sign of structural trouble, and you want a clean restore point made while the file still opens.
When the file needs professional attention
If the message appears on ordinary day-to-day entries, or returns immediately after a restart, the database itself is the problem. Our engineers see this in files that have grown past what the installed edition handles comfortably, and in files with internal damage that inflates lock usage. That is not something a setting fixes. We can evaluate the file, determine whether it needs repair, condensing, or both, and give you a free quote before any work starts. See our Sage 50 database repair service for what that involves.
A useful next step
Make the backup now, while the file still opens normally. Then send it for a free evaluation so you know whether this is a size problem, a damage problem, or both, rather than guessing. If you have also been considering a move to QuickBooks, a conversion can be a natural exit from an oversized file, and we can assess both options from the same backup.