SmartPosting will remain stopped for the company that caused the error
Sage 50's background posting service hit a data problem in one company file and has disabled background posting for that file.
“The service is stopping and will restart again automatically; however, SmartPosting will remain stopped for the company that caused the error.”
In plain terms, Sage 50’s SmartPosting service — the background process that posts transactions for you without making you wait — ran into a problem it could not handle inside a specific company file. Rather than crash the whole program, Sage 50 restarted the service but quarantined the file that triggered the fault. Background posting is now off for that one company. Everything else in Sage 50 should keep working normally.
What this means for your data
Your company file is still there and you can usually still open it. The issue is that SmartPosting encountered something in the data — a damaged transaction, a broken index, a corrupted header, or a record it could not write to — and it gave up on that file to protect itself. You can typically still post transactions manually from within the company; it is the automatic background posting that has been shut down.
Try posting manually first
Open the company in Sage 50 and attempt to post a transaction the normal way. If manual posting succeeds, your immediate workflow is not blocked — only SmartPosting is. You can continue working while you decide what to do about the underlying damage.
If manual posting also fails or produces errors, the file has active corruption that needs attention before it gets worse.
Check whether the problem is isolated
If you maintain multiple Sage 50 companies, open another one and see whether SmartPosting works there. If it does, the problem is confined to the one file — which is the most common scenario and the one this message describes. If SmartPosting fails everywhere, the installation itself may need attention, but the message specifically names one company, so a single-file problem is far more likely.
What not to do
Do not keep forcing transactions through a file that is throwing errors. Each failed post can compound the damage, and a file that might have been a straightforward repair can turn into a recovery job. If Sage 50 is telling you a company “caused the error,” treat that as a signal to stop and assess.
When the file needs professional attention
If manual posting fails, if the file will not open, or if SmartPosting stays disabled even after a restart of Sage 50, the company file most likely has structural damage that Sage 50’s built-in maintenance tools cannot fix. Our engineers regularly repair Sage 50 (Peachtree / Simply Accounting) databases that have been disabled by this kind of fault. We can evaluate the file at no cost and tell you exactly what is damaged and what the repair would involve — pricing and turnaround depend on the specifics of the file.
Contact us about your Sage 50 file for a free evaluation, or if you have been considering moving away from Sage 50 altogether, we also convert Sage 50 data to QuickBooks.