Fix 0X00000A4C Remoteboot Database Backup Failure

Cause 1: The RPL Database File Is Locked by Another Process

This is the most common reason I see for 0X00000A4C. The Remoteboot database file — usually RPLMGR.MDB or RPLSVC.MDB — gets held open by something else. It could be the Service Control Manager, an antivirus scan, or even a leftover handle from a crash.

The fix: Stop the Remoteboot service first. Then check if any process has the file open. Use handle.exe from Sysinternals to find the culprit:

handle.exe -a -p RPLMGR.MDB

If that shows a handle, kill the process with taskkill /PID [pid] /F. Then restart the service and try the backup again. If you can't find the handle, just reboot the server. It's blunt but it works.

Don't bother checking Event Viewer here — it rarely gives more detail. The locked file is the problem 80% of the time.

Cause 2: Insufficient Permissions on the Database Directory

The RPL service runs under the LocalSystem account by default (or a specific domain account if you changed it). If that account doesn't have Full Control on the folder containing the database, the backup fails with 0X00000A4C.

I've seen this happen after someone moves the database or restores permissions from a backup. The service can read the file but can't write a backup copy.

The fix: Open Explorer, find the %SystemRoot%\system32\RPL folder (or wherever your RPL database lives). Right-click > Properties > Security tab.

• Add SYSTEM with Full Control if it's missing.
• If you're using a custom service account, give that account Full Control too.
• Click Advanced and make sure the permissions are set to This folder, subfolders, and files.

After that, restart the Remoteboot service and run the backup manually:

net stop "RemoteBoot Service" && net start "RemoteBoot Service"

Then try the backup. If you're still stuck, move to cause 3.

Cause 3: Corrupted Database or Service Registration

If the database itself is corrupted or the RPL service isn't registered properly in the registry, the backup fails with this error. This is rare, but it happens after a partial uninstall or a hard crash.

The fix: First, check the database integrity. Use rpldiag.exe if you have the Resource Kit. It'll tell you if the database is corrupt.

If it's corrupt, you can rebuild it from a previous backup. Copy RPLMGR.MDB from a known-good backup into the RPL folder. Stop the service first, copy the file, then start it again.

If the database is fine, check the service registration in the registry. Open Regedit and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RplService

Ensure the ImagePath points to the correct executable — usually %SystemRoot%\system32\rplsvc.exe. If it's wrong, fix it and reboot. I've seen a sysadmin accidentally change it to a non-existent path while cleaning up old services.

Skip the registry edit unless you're sure — messing it up will break the service entirely.

Quick-Reference Summary Table

That's it. Start with the locked file — that's the fix nine times out of ten. If it's not that, permissions. And only dig into the registry if both of those fail. You'll have this error cleared in under 10 minutes.