Event Codes Table

The table below lists issues detected by the RunScore Runtime Validator (RV) and how to resolve them.

Event Code	Event Section	Event Details
100001	General Events	Includes general information.
100002	Printer driver not found	The printing feature will be disabled. Check the printer configuration to resolve this issue.
100003	Printer setup failure	RunScore was unable to set up the printer. Check the logs for the error code. It will be one of the printer errors listed in event 100002.
100004	Printer output not found	RunScore could not set up the printer output, so printing is disabled. Check the printer configuration and the logs.
100005	License validating	Informational. RunScore is validating your license with the licensing service on startup.
100006	License validated	Informational. Your license was successfully validated online.
100007	License accepted offline	Informational. The licensing service could not be reached, but a previously validated license was accepted within its offline grace period.
100008	License rejected	The licensing service rejected your license. Verify your registration and subscription status.
100009	Auto-update failed	New version is available but automatic update cannot start. Click Download in the dialog to open the installer URL in your default browser, then download and run the installer manually.
100010	TCP Port In Use	A TCP listener could not bind its port because another RunScore instance or device is already using it. This is expected when you intentionally run two RunScore instances (for example, to copy listings between races): both share the single TCP server port set in Preferences, so the second instance's listener stays disabled while the rest of the application keeps working. The same applies to an external-timer listen thread on a device port. Close the other instance (or change the port), then reopen the race to re-enable the listener. The logs include the port and the error code (WSAEADDRINUSE / 10048).
101001	Entries Age Processing	The RACE DATE command is missing from Entries.ini. As a result, the Age field will not be automatically updated based on the Birth Date field. Set RACE DATE in Entries.ini — that is the correct place for this command. See Race Date and Age Processing.
101002	Entries Control Section	RunScore RV detected a misconfiguration in the [control] / [data] section. Refer to the Entries Configuration guide for detailed steps to resolve this.
101003	Entries Race Date Format	RunScore detected that the argument for the Race Date command does not match the Race Date format. See Race Date.
101004	Entries Color Setup	RunScore RV detected an unsupported color for ENTER BG COLOR, ENTER FONT COLOR, RESULTS BG COLOR, or RESULTS FONT COLOR commands. Check the Colors reference and Enter Options.
101005	Entries Birthdate is missing	The BIRTH DATE FIELD command is missing from Entries.ini. As a result, the Age field will not be automatically updated based on the Birth Date field. See Field Mapping and Age Processing.
101006	Entries year, month, day is missing	The Entries.ini file is missing the YEAR FIELD, MONTH FIELD, or DAY FIELD commands. As a result, the Age field will not be automatically updated based on those fields. See Age Processing. This is an older format — we recommend using BIRTH DATE FIELD instead.
101007	Entries Invalid Tokens	RunScore RV detected invalid input in the [data] section. Check the logs for the offending input string and the specific error. Refer to the Entries Configuration guide.
101008	Entries Custom Variable Error	A custom variable in Entries.ini is invalid — the name is empty or it creates ambiguity for RSM parameter replacement. Check the logs for the variable name.
101009	Entries Custom Variable Empty	A custom variable defined in Entries.ini has an empty value. Check the logs for the variable name.
101010	Entries Custom Variable Not Found	A custom variable referenced in Entries.ini is not defined. Check the logs for the variable name.
101011	Entries Invalid Birth Date	RunScore could not parse the birth date for one or more records, so the Age field cannot be computed. The logs include the record index and the offending value. See Age Processing.
101012	Entries Birth Date After Race Date	A parsed birth date is later than the age reference (race) date, so age cannot be computed. The logs include the record index and both dates. See Age Processing.
101013	Entries Age As Of Date Format	RunScore detected that the argument for the AGE AS OF DATE command does not match the configured DATE FORMAT, or the date is invalid. See Age As Of Date.
102001	Results Bib Mismatch	This error occurs during CSV import when the number of participants exceeds the configured space. The online download will automatically allocate enough space for the event. See How to Allocate Space.
102002	Results Time Mismatch	Similar to event 102001, this error occurs during CSV import when the number of participants exceeds the configured space. The online download will automatically allocate sufficient space. See How to Allocate Space.
102003	Results Processing	This event is triggered when no times are found or there is a mismatch between the number of times and the participant count.
102004	Results Header Missing	This event occurs during results posting or exporting if the application cannot find the header mapping. The header mapping is created during participant downloads.
102005	Results Minus Event Unavailable	On a Live Results minus column, the snapshot or fetch of the second event failed, so the minus column cannot be computed. Check the logs and the second event's configuration.
102006	Results Count Mismatch	After loading an event's result files, RunScore detected that the bib count and time count are inconsistent — for example, bibs exist but no times (or vice versa). For lap events, this fires only when times are fewer than bibs. .FN2 (bibs) and .TM4 (times) come from an external timer or from a results backup copy. If the counts disagree, the results are untrustworthy; do not score until the files (or the timer/backup source) are consistent.
103001	Listing Memory Corruption	This event is triggered if a listing file generates data corruption. The issue may occur due to invalid command arguments or incorrect command order. Review the listing file and check the Commands reference for usage.
103002	Listing Parameter Count Mismatch	This event occurs when a listing file calls an RSM (RunScore Macro) with fewer parameters than expected. See How to Resolve Parameter Count Mismatch.
103003	Invalid Command Usage	RunScore RV has detected improper command usage. For instance, the command requires a numerical argument, but none was provided, or the argument given is not a number. Check the logs for more details and consult the Commands reference.
103004	Listing Empty Field Name	RunScore RV detected an empty field name while resolving a placeholder in a listing (for example, a header mapping). Review the field references in the listing file and consult the Commands reference.
103005	Listing Missing Race Date	Raised only by the AGE listing command, which was removed after 9.1.0. In 9.1.0, set RACE DATE in Entries.ini to clear it. Ages are now computed by Age Processing from the Entries.ini RACE DATE; see Race Date.
104001	Records Memory Corruption	This event is triggered when RunScore detects an invalid configuration or invalid data on the Enter screen while adding a new record.
104002	Records Truncated Data	This event happens when RunScore finds that the imported data is cut off. The incoming data is larger than the allowed field size. The event will include the record index, the original data, the truncated data, and their corresponding lengths.
104003	Records Padding Error	RunScore could not fit a field's data into the database record layout, usually because the incoming data is larger than the field length. The logs include the field name. Increase the field length from the Design screen.
104004	Records Unicode Detected	RunScore detected Unicode (non-ANSI) characters in record data during a download or import. The logs include the record index. Non-ANSI characters may not display or export correctly.
105001	Team Position	This issue occurs when RunScore detects that the Team Position command was used without the Team Place command. Team Place is necessary for Team Position to work correctly.
105002	Team Advance	This issue occurs when RunScore detects that an Advance Teams or other advancement command was used without the Team Place command. Team Place is necessary for team advancement commands to work correctly.
105003	Team Total	This issue occurs when RunScore detects that the Team Total command was used without the Team Place command. Team Place is necessary for Team Total to work correctly.
105004	Team Score Zero	Raised on a cross-country team listing (Team Score CC, with or without Allow Ties) that uses Team Score 0. TEAM SCORE 0 is only valid with Team Slowest. Set TEAM SCORE to 1 or more. The listing stops.
106001	Alt Keys Missing Field Name	RunScore RV detected a key file line that is missing its field name. The logs include the file path and line number.
106002	Alt Keys Duplicate Key (All)	A key file defines the same general (all-fields) key more than once. The logs include the file path, line number, and the duplicated key.
106003	Alt Keys Duplicate Key (Field)	A key file defines the same key for a field more than once. The logs include the file path, line number, and the duplicated key.
107001	Field Mapping Field Not Found	An online (RaceRoster) field is mapped to a RunScore field that does not exist in the database. Review the mapping. See Field Mapping.
108001	DB Bib Field Invalid	The Bib must be the first searchable field with a length of 15 or less. Adjust the field order and length from the Design screen.
109001	Email Broadcast Started	Informational. An email broadcast has started.
109002	Email Broadcast Complete	Informational. The email broadcast finished. The logs include the number of emails sent.
109003	SMS Broadcast Started	Informational. An SMS broadcast has started.
109004	SMS Broadcast Complete	Informational. The SMS broadcast finished. The logs include a summary.
109005	SMS Broadcast Failure	Sending an SMS to a recipient failed. The logs include the recipient address.