This is an old revision of the document!

Error Messages

ⓘ NOTE:
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

Two or more DATs in a directory share the same value in their header “name” tag
Remediation: Move each of the conflicting DATs into their own subdirectory or modify the name tags in the DATs so they are unique. You can also try adjusting your Directory Rules to use the DAT Description value instead of Name.

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.