No persistence adapter loaded" PEP Upload Service error in Sage 50
The payroll upload service cannot read your Sage 50 payroll records because the component that loads the data failed, often a damaged file.
The message “PEP Upload Service - Cannot retrieve PEP records: No persistence adapter loaded.” looks like a low-level failure, and in a sense it is. In plain terms, the payroll upload service that Sage 50 uses could not open the part of your company data that holds your payroll records. The “persistence adapter” is the internal component that reads and writes those records. If none is loaded, the service has nothing to work with, so the upload stops before it starts.
The important thing to understand is that this message rarely tells you the real cause. It says the adapter is missing, but what usually happened is that the adapter tried to load your data, hit damage or a bad connection, and gave up. The message is the symptom, not the diagnosis.
Does this mean my data is gone?
Usually not. Your payroll records are most likely still in the company file. The service simply cannot reach them in its current state. In our experience this message appears in two situations: a temporary failure in the service or its connection, or genuine damage inside the company database that stops the payroll tables from loading.
Treat it as a warning light, not a verdict. Do not keep retrying the upload repeatedly, because if the underlying data is damaged, repeated attempts accomplish nothing and can add confusion about what state the file is in.
What should you try first?
Restart the Sage 50 workstation and, if the company data is hosted, the machine hosting it. This clears the service if it failed to start cleanly. Open the company file directly and confirm you can view employee and payroll data on screen. If you can, the data itself is probably fine and the fault is in the upload service layer.
If the message returns after a restart, restore your most recent backup to a separate location and test it there. Never restore over your working file. If the backup uploads without the error, you know the working file is the problem, and you have a clean fallback.
When does the file need professional attention?
If the error follows the file rather than the machine, meaning a backup restored elsewhere shows the same fault, or if you see other oddities such as payroll totals that do not match, employees missing from lists, or the file failing verification, the database itself is damaged. That is not something a reinstall or a service restart will fix, and we do not recommend attempting manual repair on a live payroll database.
Our engineers repair damaged Sage 50 (and Simply Accounting and Peachtree) databases, including payroll table damage of exactly this kind. Whether the fault is in the payroll records or in how the service reads them depends on the file, so we start with a free evaluation and a no-obligation quote before any work is done. If you would rather leave Sage 50 behind entirely, we also convert Sage 50 payroll and history to QuickBooks, which sidesteps the upload service altogether.
The useful next step: make a safe copy of the company file now, before anything else touches it, then send it for a free evaluation so someone can tell you which of the two situations you are in.