Error Messages

This page is under construction and should not be considered comprehensive. This page aims to document all “friendly” errors you may encounter along with guidance how to resolve those errors. All Stack Trace errors should be considered bugs and reported on the RomVault Discord.

Loading DATs

Invalid DAT File

The DAT file format is not supported by RomVault.
Remediation: Remove the DAT file from your DATRoot.

Error Occurred Reading DAT

The DAT file is malformed and could not be converted to valid XML.
Remediation: Remove the DAT file from your DATRoot.

Error Keyword [X] not known in dir, on line [Y]

The clrmamepro formatted DAT file contains invalid set keys (Valid: “game”, “machine”, etc.)
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

( not found after clrmamepro, on line [X]

The clrmamepro formatted DAT is missing a “(” character in the DAT header.
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [X].

Error: key word [X] not known in clrmamepro, on line [Y]

The clrmamepro formatted DAT file contains invalid keys in the header.
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

( not found after emulator, on line [X]

The clrmamepro formatted DAT is missing an opening “(” character after the emulator key
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [X].

Error: key word [X] not known in emulator, on line [Y]

The clrmamepro formatted DAT file contains invalid emulator attribute keys (Valid: “name”, “version”, etc.)
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

( not found after game, on line [X]

The clrmamepro or DOSCenter formatted DAT is missing an opening “(” character after the game key
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [X].

Name not found as first object in ( ), on line [X]

The clrmamepro or DOSCenter formatted DAT is missing a name key as the first attribute of the set or rom.
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [X].

Error: multiple names found in one game [X] will be ignored, on line [Y]

The clrmamepro formatted DAT has multiple name keys in a set.
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

Error: key word [X] not known in game, on line [Y]

The clrmamepro or DOSCenter formatted DAT file contains invalid game attribute keys (Valid: “name”, “description”, etc.)
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

( not found after rom, on line [X]

The clrmamepro formatted DAT is missing an opening “(” character after the rom key
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [X].

Error: key word [X] not known in rom, on line [Y]

The clrmamepro or DOSCenter formatted DAT file contains invalid rom attribute keys (Valid: “size”, “sha1”, etc.)
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

( not found after Archive, on line [X]

The clrmamepro formatted DAT is missing an opening “(” character after the archive key
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [X].

Error: key word [X] not known in Archive, on line [Y]

The clrmamepro formatted DAT file contains invalid archive attribute keys (Valid: “name”)
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

Unknown Line [X], [Y]

The ROMCenter formatted DAT file contains an invalid line tag (Valid: “[games]”, “[disks]”, etc.)
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

Looking for [CREDITS] but found [X], [Y]

The ROMCenter formatted DAT file is missing a [credits] line in the header.
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

Unknown Line [X] found in [CREDITS], [Y]

The ROMCenter formatted DAT file contains an invalid [credits] attribute (Valid: “author”, “email”, etc.)
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

Looking for [DAT] but found [X], [Y]

The ROMCenter formatted DAT file is missing a [dat] line in the header.
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

Unknown Line [X] found in [DAT], [Y]

The ROMCenter formatted DAT file contains an invalid [dat] attribute (Valid: “version”, “plugin”, etc.)
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

Looking for [EMULATOR] but found [X], [Y]

The ROMCenter formatted DAT file is missing a [emulator] line in the header.
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

Unknown Line [X] found in [EMULATOR], [Y]

The ROMCenter formatted DAT file contains an invalid [emulator] attribute (Valid: “exe”, “runcmd”, etc.)
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

Looking for [GAMES] but found [X], [Y]

The ROMCenter formatted DAT file is missing a [games] line in the body of the DAT.
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

Looking for [DISKS] but found [X], [Y]

The ROMCenter formatted DAT file is missing a [disks] line in the body of the DAT.
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

Error: key word [X] not known, on line [Y]

The DOSCenter formatted DAT has an invalid key.
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

( not found after DOSCenter, on line [X]

The DOSCenter formatted DAT is missing an opening “(” character after the doscenter key
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [X].

Error: key word [X] not known in DOSReader, on line [Y]

The DOSCenter formatted DAT contains an invalid key in the header (Valid: “name”, “description”, etc.)
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [Y].

( not found after file, on line [X]

The DOSCenter formatted DAT is missing an opening “(” character after the file key
Remediation: Remove the DAT file from your DATRoot or edit the DAT to fix the error on line [X].

Path: [X] Not Found

The DATRoot path could not be found.
Remediation: Check that your DATRoot path is accessible (E.g. located on a disconnected drive)

ERROR Deleting a DAT that should already be deleted

Something has gone horribly wrong and you should report this error on Discord with steps to reproduce.
Remediation: Backup your cache and DATRoot directory and report this error on Discord for further investigation. Once you have your files backed up, force refresh all DATs.

Error reading Dat [X]

The DAT is invalid and could not be read.
Remediation: Remove the DAT file from your DATRoot.

Dat Merge conflict occurred Cache contains [X] new dat [Y] is trying to use the same directory and so will be ignored

Two or more DATs are sharing the same directory and there are conflicts between them (E.g. duplicate set sames)
Remediation: Move each of the conflicting DATs into their own subdirectory or delete outdated DATs in that directory. This error is likely to occur if you have existing DATs and choose to download DATs with DATVault to the same directory.

Double Name Found

There are sets that share the same name with different character case
Remediation: Double check your filesystem case sensitivity settings and if you have multiple files/directories that have the same name but different character case. Remove any duplicates and try again.

Error is Set Missing Status in DatUpdate

Something has gone horribly wrong and you should report this error on Discord with steps to reproduce.
Remediation: Backup your cache and DATRoot directory and report this error on Discord for further investigation.

Scanning Files

File: [X] Error: [Y]. Scan Aborted.

A scanning error occurred. This is a catch all error for any scanning issue that halts the scan.
Remediation: Check that your file permissions are properly set.

Zip File Locked

The file RomVault attempted to scan was locked by another process.
Remediation: Quit any other programs that may be using the file and rescan. You can also attempt to rename the file, and if its in use then you will get a Windows error.

Zip Error Opening File

The file could not be opened.
Remediation: Check file permissions and try extracting the archive contents with another program. If you can extract with another program, please report the error on Discord.

Unsupported file type in CheckADir

Somehow RomVault attempted to scan something that wasn't a directory, zip, or 7z archive.
Remediation: Report on Discord with information about your filesystem.

Unknown Reading File Type in Dir Scanner

Somehow RomVault attempted to scan nothing.
Remediation: Report on Discord with information about your filesystem.

Error in File Scanning Code

How did you even get this error?
Remediation: Report on Discord.

Fixing Files

You Need to Find Fixes before Fixing. (Incorrect File Status's found for fixing.)

Self-explanatory. A “Fix” operation was attempted before first doing “Find Fixes”.
Remediation: Click the “Find Fixes” button. When the operation completes, then click the “Fix ROMs” button.

Your Primary ToSort directory could not be found

Your Primary ToSort directory is not accessible. This directory is required because unneeded ROMs will be moved to this directory.
Remediation: Ensure that your Primary ToSort directory is accessible.

Logic error trying to find the file we are fixing

This error should never occur, and if it does there is likely a logic error in the RomVault code.
Remediation: Backup your cache file and report the error on Discord.

Trying to fix a file that already exists [X]

This error should never occur, and if it does there is likely a logic error in the RomVault code.
Remediation: Backup your cache file and report the error on Discord.

Did not find a file logic error while fixing duplicate named file. in FixFile

This error should never occur, and if it does there is likely a logic error in the RomVault code.
Remediation: Backup your cache file and report the error on Discord.

Unknown file status in Matching File found of [X]

This error should never occur, and if it does there is likely a logic error in the RomVault code.
Remediation: Backup your cache file and report the error on Discord.

Unexpected file found in directory. Rescan needed. [X]

The file being used for the fix already exists in the destination directory. Your cache is likely out of sync with the files you have in that directory
Remediation: Rescan the problematic destination directory to ensure your cache is up-to-date. If the issue persists there may be a filename incompatibility, for example two files with the same name but different character case.

Error in Fix Rom Status [repair_status] : [dat_status] : [got_status]

This error should never occur, and if it does there is likely a logic error in the RomVault code. Basically this error means there is an invalid combination of ROM statuses and fix statuses.
Remediation: Report the error on Discord.

Deleting [X] Correct file not found. Rescan for [Y]

Before deleting an unneeded file, RomVault checked that the other copy actually exists but could not find the file.
Remediation: Rescan your files to ensure your cache is up-to-date with your filesystem.

Deleting [X] Correct file timestamp not found. Rescan for [Y]

Before deleting an unneeded file, RomVault checked that the other copy actually exists but the modified timestamp of that file didn't match what is in the cache.
Remediation: Rescan your files to ensure your cache is up-to-date with your filesystem.

Delete Check found multiple tree paths to the same file. Tree structure should be fixed: 1st Path = [X] 2nd Path = [Y]

Before deleting an unneeded file, RomVault checked that the other copy actually exists but found that the same file was referenced from more than one path. This is most likely to occur if you have misconfigured directory rules or a ToSort directory that also exists underneath your RomRoot.
Remediation: Check and correct any misconfigured directory rules ensuring they are mutually exclusive. Also check that no ToSort directories are located within your RomRoot. It is technically possible to have such a setup, but you must be careful not scan any files from that directory from the RomRoot path and only scan from the ToSort path.

Rescan needed, File Not Found : [X]

The file RomVault was attempting to use for a fix was not found. Your cache is out of sync with your filesystem. Its also possible there is a case sensitivity mismatch with the file RomVault is looking for.
Remediation: Rescan your files to ensure your cache is up-to-date. If you continue to run into issues, check your case sensitivity configuration settings for any remote shares (rclone mounts, SMB shares, etc.).

Rescan needed, File Changed : [X]

The file RomVault was attempting to use for a fix was found, but the timestamp did not match what is recorded in the cache. Your cache is out of sync with your filesystem.
Remediation: Rescan your files to ensure your cache is up-to-date. If you continue to run into issues, check your timestamp configuration settings for any remote shares. Its possible that the timestamp granularity conflicts could cause RomVault to flag a file as modified when it was not.

Other Errors

Unknown Tree settings in DisplayTree

Something has gone horribly wrong and you should report this error on Discord with steps to reproduce.
Remediation: Backup your cache and DATRoot directory and report this error on Discord for further investigation.

You cannot delete the [X] Directory Settings

Self-explanatory. This error occurs when you attempt to delete the directory settings for your RomRoot.
Remediation: Don't do that.

Unknown test status [file], [dat_status], [repair_status]

This error should not be possible. It is only triggered when executing Find Fixes and there is a ROM status that is unknown to the rest of the RomVault code.
Remediation: If you got this error, chances are you forked RomVault and broke something. Report on Discord.

Incompatible Compare type

How did you even get this error?
Remediation: Report on Discord.