Sage 50: "Use a new filename or close the file in use by another program
Sage 50 is blocked because the file it wants to write to is already open or locked by another program, so it asks for a new name or a released lock.
If Sage 50 has just told you to “Use a new filename or close the file in use by another program.” the program was in the middle of creating or overwriting a file, usually a backup, a restored copy, or an export, and Windows refused because something else already has that file open. Despite how it reads, this message is almost never a sign that your data is damaged. It is a safety stop: Sage will not risk writing over a file that another program may be changing, so it asks you to either pick a different name or make the other program let go.
What the message actually means
Sage requested permission to write to a specific filename, and the operating system answered that the file is in use. Rather than overwrite a file that might be mid-change somewhere else, Sage halts and offers the two ways out stated in the message. Treat it as a traffic light, not a diagnosis.
Why it happens
The usual culprits, in rough order of frequency:
- Another Sage window, or another workstation in a multi-user setup, still has the file open.
- A previous Sage session crashed and left the lock behind even though nothing looks open.
- A cloud sync client such as OneDrive, Dropbox, or Google Drive is syncing the folder at that moment.
- Antivirus software or a scheduled backup tool is scanning or holding the file.
- Another program, for example a spreadsheet app or a file preview pane, has the file open.
- The name you typed simply matches an existing file that happens to be locked.
Close whatever has the file open
Check your own desktop first. Close other Sage windows, close any program that might be displaying the file, and shut the preview pane in your file browser if you use one. If the company is shared, ask other users to close Sage on their machines before trying again.
Clear a stale lock with a restart
If nothing appears to be open, a crashed session may have left a lock behind with no visible window. Close Sage completely, check the task manager for any Sage processes still running and end them, then restart the machine. A restart releases locks held by programs that no longer exist, and it is the safest first fix because it changes none of your data.
Check sync and antivirus tools
Company data stored in a synced folder gets locked briefly and repeatedly by the sync client, which can make this message appear at random. Antivirus scans do the same. Pausing sync, or moving your working folder somewhere that is not synced, often makes the problem disappear entirely.
Use a different filename
The message’s first suggestion is also the fastest safe fix: save to a new name. For backups, a name that includes the date avoids collisions with earlier backups. Do not delete the existing file to force your chosen name through. If something has it locked, you want to find out why, and an older backup may be your only good copy.
When to suspect the file itself
If the message appears while opening the company rather than saving, or if it keeps returning after a clean restart with nothing else running, the lock may be a symptom of an interrupted write or a damaged data set. Stop retrying at that point. Repeated failed writes can leave company data in a worse state than it is now. Our engineers can examine a damaged Sage 50 database and tell you what is recoverable before you attempt anything else, and we provide a free evaluation of the specific file.
The practical next step: restart the machine, open Sage with nothing else running, and try once using a fresh filename. If the message comes back under those conditions, have the file looked at rather than continuing to experiment.