You cannot open the company without SmartPosting running" in Sage 50
Sage 50 refuses to open your company because its SmartPosting background service is not running, not because the file is corrupt.
The message “You cannot open the company without SmartPosting running.” sounds like a hard block on your company file. In practice it almost never means the file is damaged. It means Sage 50 expects a background posting service to be active, cannot find it, and is refusing to start until it does.
What SmartPosting actually is
SmartPosting is a Sage 50 feature that moves the posting of transactions into a background process. Instead of writing every entry to the database the moment you save it, Sage 50 queues the work and lets the service apply it while you keep working. When the feature is enabled for a company, the software treats the service as mandatory. If it is not running when you open the file, you get this message rather than a partially updated set of books.
Why the service is not running
The usual causes are mundane. The service was stopped or failed to start after a Windows update or a reboot. Antivirus or security software blocked it. The machine was shut down uncleanly, perhaps after a power cut, and the service never restarted. On a network install, the service runs on the computer hosting the data, so a workstation can see this message even when its own Sage installation is fine.
What to try first
Restart the computer that holds the company data, not just your workstation. In most cases the service starts with Windows and the message clears on its own. If it does not, check whether the service is present and set to start automatically in the Windows services list. Its exact name depends on your Sage 50 version and edition, so look for a Sage-branded posting service rather than guessing at a generic name. If security software quarantined or blocked it, restore it and add an exclusion.
If the message keeps coming back
A service that starts and then stops again, or a file that complains even with the service running, points to a deeper problem. The queue the service processes may be damaged, or the company database itself may have inconsistencies that stop posting from completing. That is not something to fix by repeatedly reopening the file. Each failed attempt risks leaving the posting queue in a worse state, so stop retrying and work from your most recent backup in the meantime.
When the file needs professional attention
If the service runs normally but the company still refuses to open, the file itself is the likely culprit. Our engineers repair damaged Sage 50 and Simply Accounting databases, including files that fail to open or fail to post, and we can tell you quickly whether yours is recoverable. See our Sage 50 database repair service for what that involves, or contact us about your file for a free evaluation and a no-obligation quote. If you have been considering a move instead, we also handle Sage 50 to QuickBooks conversions, and a damaged file can often be recovered straight into that process.