Skip to content

Error codes

Letalys edited this page Sep 20, 2026 · 1 revision

Français · English

Error codes

Since version 1.3.0, every RSRebase error message ends with a code in brackets:

Not enough disk space on the target device. [RSR-3004]
An error message and its code

The code shows in the Error column of the rebase window, in dialogs and in the rebase log. A code keeps the same meaning from one version to the next. Quoting it in an issue is enough to locate the problem.

The first digit gives the family:

Family Area
1xxx Startup, RomStation and its database
2xxx Checks made before starting a rebase
3xxx Copy and extraction of a game
4xxx Conversion by external tool
5xxx Metadata and covers
6xxx Presets
7xxx Target architectures and external tools
9xxx Unexpected errors

1xxx: startup

Code Meaning What to do
RSR-1001 RomStation was not found on the machine Click Browse… and pick the folder that contains RomStation.cfg
RSR-1002 The RomStation database is not initialized Launch RomStation once, let it start, then restart RSRebase
RSR-1003 The RomStation database is incomplete or corrupted Launch RomStation to check it works. If it starts normally, restart RSRebase
RSR-1004 The database is locked by another program Close RomStation and any tool reading its database (DBeaver…), then restart
RSR-1005 app-state.json cannot be read Click Continue: RSRebase recreates the file
RSR-1006 user-preferences.json cannot be read Click Reset: preferences return to their default values
RSR-1007 Startup failed for another reason Note the message shown and open an issue
RSR-1008 The library could not be loaded Close RomStation, restart RSRebase. If the error comes back, open an issue
RSR-1009 The database sync failed Close RomStation and any tool reading its database, then run Sync RomStation DB again

2xxx: before the rebase

Code Meaning What to do
RSR-2001 No destination is set Pick a folder with Browse…
RSR-2002 The destination path is not complete Type an absolute path, for example E:\ or D:\Roms
RSR-2003 The drive letter does not exist Plug the media in, or pick another drive
RSR-2004 The destination folder could not be created Check write permissions and that the media is not write-protected
RSR-2005 No target architecture is selected Pick an architecture. If none is left: Restore default architectures in the editor
RSR-2006 No game is selected Check games in the library
RSR-2007 The destination does not have enough room Free some space, reduce the selection, or choose Never extract if the target reads archives
RSR-2008 The conversion work folder does not have enough room Free some space on the local disk: a conversion needs the size of the largest game, extracted
RSR-2009 Metadata could not be read from the database Run Sync RomStation DB, then try again
RSR-2010 The destination folder does not exist Check that the media is plugged in, or create the folder again

3xxx: copy and extraction

These codes show in the Error column, game by game. The other games carry on.

Code Meaning What to do
RSR-3001 The file of the game cannot be found in RomStation Run Sync RomStation DB: the game was moved or deleted. Otherwise, download it again in RomStation
RSR-3002 The destination can no longer be reached Check that the media is still plugged in
RSR-3003 Access denied Check write permissions, the lock switch of the SD card, and that an antivirus does not block writing
RSR-3004 Disk full Free some space on the destination
RSR-3005 Invalid or unreadable archive The RomStation zip is damaged: download the game again in RomStation
RSR-3006 Archive refused: an entry points outside the target folder The archive is not safe, it is not extracted. Report the game in an issue
RSR-3007 Copy interrupted by an input/output error Unstable or removed media. Check the card, try again with fewer concurrent copies
RSR-3008 The destination drive disappeared Plug the media back in
RSR-3099 Copy error not listed Look at the rebase log, which keeps the full message, and open an issue

4xxx: conversion

Code Meaning What to do
RSR-4001 The tool planned for this game is not available Open Manage external tools… and set its executable
RSR-4002 The executable of the tool cannot be found at the given location Do Browse… again. RomStation may have updated the emulator that contains it
RSR-4003 The tool could not be started Check that the file is a Windows program, and that an antivirus does not block it
RSR-4004 The tool ended with an error Read what the tool printed, in the rebase log. Common causes: incomplete archive, version too old
RSR-4005 The tool ended without producing a file Same approach as for RSR-4004
RSR-4006 The tool stopped responding: it was stopped Try again. If it happens again on the same game, report it
RSR-4007 The file to convert was not found in the archive The RomStation archive does not contain what RSRebase expected. Report the game
RSR-4008 Tool version too old Update MAME or Dolphin, or the emulator in RomStation
RSR-4009 The tool did not answer the Test button Check that the executable is the right program

5xxx: metadata and covers

Code Meaning What to do
RSR-5001 The metadata file of a system could not be written Check that the file is not open elsewhere or read-only. The games are copied
RSR-5002 A cover could not be copied The game is copied. Check room and permissions, then run the rebase again: only the cover will be written

6xxx: presets

Code Meaning What to do
RSR-6001 The preset file cannot be read Check that it still exists and that the media is plugged in
RSR-6002 The file is not valid JSON It was edited by hand: fix the syntax, or start again from a preset saved by RSRebase
RSR-6003 This file is not an RSRebase preset Pick a .rsrgp file
RSR-6004 No game of the preset exists in the library The preset comes from another RomStation library, or its games were deleted
RSR-6005 The preset could not be saved Check write permissions on the chosen folder
RSR-6006 The .rsrgp file association could not be created or removed Run RSRebase normally, not as administrator, and check that no security tool blocks writes to the account's registry

7xxx: architectures and tools

Code Meaning What to do
RSR-7001 The list of architectures could not be read architectures\index.json is damaged: Restore default architectures
RSR-7002 The systems table of an architecture could not be read The file of that architecture is damaged: fix it, or delete the architecture and create it again
RSR-7003 An architecture could not be saved Check write permissions on the RSRebase data folder
RSR-7004 An external tool could not be saved Same approach as for RSR-7003

9xxx: unexpected errors

Code Meaning What to do
RSR-9001 Unexpected error in the interface The application closes. The detail is in a RSR_crash_….txt file of the logs folder: attach it to an issue
RSR-9002 Unexpected error in a background task Note the message and open an issue
RSR-9003 Fatal error Same approach as for RSR-9001

Reporting an error

Open an issue with the Bug report template, giving the code and attaching the rebase log (%LOCALAPPDATA%\RomStationRebase\logs).

Clone this wiki locally