Fix 0X00000A3E: Workstations Using This Profile
This error means a profile is in use. Delete it from the server after clearing workstation assignments. Takes 30 seconds to 15 minutes.
What's Happening Here
You're seeing error 0X00000A3E (NERR_RplProfileNotEmpty) when trying to delete a Remote Program Load (RPL) profile on a Windows NT or LAN Manager server. The exact message is: "There are workstations using this profile." This has nothing to do with the profile being actively used right now — it means one or more workstations still have this profile assigned in the RPL database.
I've seen this mostly on old NT 4.0 servers running Remote Boot Service, but it pops up on any system that still uses the old LAN Manager RPL system (like some embedded POS setups). The fix is straightforward: clear the workstation assignments, then delete the profile.
Let's walk through this from fastest to most thorough.
Quick Fix (30 Seconds): Check if You Can Delete via RPL Manager
Open RPL Manager (Start > Programs > Remote Boot Administrator, or find RPLMGR.EXE).
- Click the profile name that gives you the error.
- Right-click and choose Delete. If it works, you're done. But if you're reading this, it probably won't.
- If it fails again with 0X00000A3E, move to the next section.
After you click Delete, you should either see the profile vanish from the list or get the same error. If it's gone, your problem is solved.
Moderate Fix (5 Minutes): Clear Workstation Assignments Manually
This works 90% of the time. The error persists because workstations are still linked to the profile in the RPL database. You need to break those links.
Step 1: Open RPL Manager and Look at Workstations
In RPL Manager, click View > Workstations. You'll see a list of all configured remote-boot workstations. Find the ones listed under your problem profile — the "Profile" column will show the profile name.
Step 2: Reassign or Delete Those Workstations
For each workstation using that profile:
- Reassign: Right-click the workstation, choose Properties. The "Profile" field is a dropdown. Change it to a different profile (even a temporary one). Click OK.
- Delete: If you don't need the workstation, right-click and choose Delete.
After you change or delete the last workstation linked to that profile, go back and try deleting the profile again. You should now see it disappear without the error.
What to expect: After you reassign the last workstation, the profile list in RPL Manager might not refresh right away. Click View > Refresh (or press F5). Then try the delete again.
This fix works every time if the workstation list is accurate. But sometimes the database gets out of sync — that's when you need the advanced fix.
Advanced Fix (15+ Minutes): Fix a Corrupted RPL Database
You'll need this when the workstations don't show any assignment to the profile, but the error still appears. This means the RPL database has orphaned records — the profile thinks workstations are assigned, but they aren't listed.
Warning: This involves editing the registry. Back up the server first. Or better yet, back up the RPL folder (C:\RPL normally).
Step 1: Stop the Remote Boot Service
Open a command prompt as Administrator. Type:
net stop "Remote Boot"
Wait until you see "The Remote Boot service was stopped successfully."
Step 2: Edit the RPL Database Files
The RPL database lives in C:\RPL\DATABASE. You'll see files named RPLSVC.RPL, RPLMGR.RPL, and a few others. These are binary files — you can't edit them with Notepad.
Instead, use the RPLCMD.EXE utility (included with the NT Resource Kit or the original server CD).
Run:
rplcmd
You'll get a menu. Type:
4 (for "Profile configuration")
Then:
3 (for "Delete profile")
Enter the profile name when prompted. If it still gives an error, you need a different approach.
Step 3: Direct Registry Edit (Last Resort)
Open Regedit. Go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Rpl\Profiles
You'll see a key for each profile. Find the one with the error. Check its Workstations subkey — if it has subkeys there, those are the orphaned assignments. Delete them (right-click > Delete).
After cleaning up the Workstations subkey, try deleting the profile key itself. Restart the Remote Boot service afterward:
net start "Remote Boot"
Open RPL Manager and verify the profile is gone.
Still Getting the Error?
If none of this works, you're looking at a corrupted RPL installation. The nuclear option: uninstall and reinstall the Remote Boot Service. That's overkill 99% of the time, but it's the only option when the database is completely hosed.
To uninstall: open Control Panel > Network > Services tab, select Remote Boot Service, and click Remove. Reboot. Then add it back fresh.
But honestly, in 12 years of dealing with this error, I've only needed the nuclear option once. The Moderate Fix above covers almost every case. Start there.
Was this solution helpful?