Until this issue is resolved, you cannot open some of your reports" (Sage 50)
Sage 50 is telling you part of your company data is damaged, so reports that depend on it will not open until it is fixed.
The message “Until this issue is resolved, you cannot open some of your reports.” sounds like a temporary lock, but it is not. Sage 50 has found a problem inside your company data, and the reports that rely on the damaged portion refuse to open rather than show you wrong numbers. It is a safety measure, not a glitch that will clear on its own.
What the message actually means
Sage 50 checks the integrity of your data as it works. When part of a file is damaged or inconsistent, the program blocks the reports that would read that part. The rest of the program may look fine. You can often keep entering transactions while certain reports stay closed, which makes the problem easy to underestimate.
The damage is usually in the data itself, not in the report. Fixing or reinstalling the software rarely changes this message.
Why it happens
Common triggers include an interruption while Sage 50 was writing to the file: a power loss, a forced shutdown, or a network drop while the file was open on a shared drive. Storing the company file somewhere it does not belong, such as a cloud-synced folder, can also corrupt it, because sync tools change the file while Sage still has it open.
Damage can also build up over years in large files, or appear after a restore from a backup that was itself incomplete.
What to try first
Restore your most recent backup, before the message appeared. This is the safest fix and the one most likely to succeed. Open the restored copy and check whether the blocked reports run. If they do, you can re-enter any transactions recorded since the backup, or compare against your bank statements.
If you have no usable backup, do not keep working in the file. Every new transaction adds data that a later repair has to account for. Make a copy of the file as it stands now and set the original aside.
Check whether the damage is real or minor
Sometimes the block follows a small inconsistency that Sage 50 can resolve itself. Close the company, reopen it, and try the report again on a machine where the file is stored locally rather than over the network. If the message persists, the data is genuinely affected and self-repair is unlikely to help.
We do not recommend third-party repair utilities on a live company file. They can make recovery harder, not easier.
When the file needs professional attention
If no backup is clean and the reports stay blocked, the file needs to be examined by people who repair Sage 50 data for a living. Our engineers open damaged Sage 50 and Simply Accounting databases, isolate the affected records, and rebuild the file so the reports open again with their history intact. This is not something a setting change will fix.
If you are also weighing a move off Sage 50, a damaged file can often be repaired and converted in one step; see our Sage 50 to QuickBooks conversion service or, for Canadian data, our Simply Accounting database repair service.
A useful next step
Send us the file for a free evaluation before you re-enter anything by hand. We will tell you what is damaged, whether the blocked reports can be recovered, and what a repair would involve, with no obligation.