2025 Change Log Date State Type 07/18/2025 WY Driver A user brought up an issue where sometimes not all fields would properly parse in WY DR messaged. This issue was caused by the line “DOT DOCUMENT NOT ON FILE” being present in the text of the message and “NOT ON FILE” is a not on file indicator for WY so the parser treated the messages as being not on file. The DR parser for WY was updated to account for the line “DOT DOCUMENT NOT ON FILE” and to not classify the record as not on file if it is present. 06/23/2025 MI Driver Error: Parsing framework logged the error “Message marked as fullytagged XML contains a response text element that is not an indication of record not on file. may contain unparsed Data” Cause: A new error message occurred for MI DR messages that the parser was not programed to handle. Solution: The parser was updated to handle the error message “INTERNAL SERVER ERROR”, as an expected error response. 06/23/2025 MI Registration Error: Parsing framework logged the error “Message marked as fullytagged XML contains a response text element that is not an indication of record not on file. may contain unparsed Data” Cause: A new error message occurred for MI RR messages that the parser was not programed to handle. Solution: The parser was updated to handle the error message “Internal server error”, as an expected error response. 05/29/2025 NH Registration Error: A user brought up an issue where when some states (specifically FL and NH) provide a two-character year for a date of birth it is incorrectly parsed to the wrong century. Cause: This issue is caused by the fact that when there is a two-character year, the system is essentially having to guess what the correct start for the year is. A threshold is set to the current year plus 15 for if the first two characters should be 19 or 20. The threshold cannot be changed as it would affect every single that goes through the parsing including expiration dates. Solution: The DR and RR parser for FL and NH were updated to check if the date the system guessed for the date of birth is in the future, if it is then the century is adjusted. If it is not, then the date of birth is left as is. 05/29/2025 FL Registration Error: A user brought up an issue where when some states (specifically FL and NH) provide a two-character year for a date of birth it is incorrectly parsed to the wrong century. Cause: This issue is caused by the fact that when there is a two-character year, the system is essentially having to guess what the correct start for the year is. A threshold is set to the current year plus 15 for if the first two characters should be 19 or 20. The threshold cannot be changed as it would affect every single that goes through the parsing including expiration dates. Solution: The DR and RR parser for FL and NH were updated to check if the date the system guessed for the date of birth is in the future, if it is then the century is adjusted. If it is not, then the date of birth is left as is. 05/12/2025 AR Driver Error: The parsing framework logged the error “Unexpected content found in the MedCert CERTIFICATE section” Cause: AR added an additional line to the medical certificate info section with a line that says “ACCOMPANIED BY A N - WAIVER/EXEMPTION” Solution: For the new line as the current practice for lines that contain “N -” is to skip past the line for parsing, I continued this practice in this line and skipped the line for parsing. 05/07/2025 CA Driver Error: The parsing framework logged the error “Unexpected line encountered in dynamic content” Cause: CA adjusted the commercial status line so a third line could appear after the originally anticipated two lines. Solution: Adjusted the parser to account for there potentially being a third line in the commercial status. 05/07/2025 CA Driver Error: The parsing framework logged the error “Unexpected line encountered in dynamic content” Cause: CA added or altered the commercial status line “NOT VALID FOR OPERATING FIREFIGHTING EQUIPMENT OR TOWING TRAILERS OVER 10,000 LBS GVWR/VALID HEALTH QUESTIONNAIRE REQUIRED”. Solution: Added handling to the parser to account for the new potential content in the commercial status. 4/29/2025 KS Driver Error: Parsing framework logged the error “Unhandled content in dynamic lines” Cause: KS added new lines to their DR containing emergency contact information. Solution: The parser was updated to handle the new content and add it to the additional information of the parsed DR. 4/29/2025 NV Driver Error: Parsing framework logged the error “General Error Thown: System.NullReferenceException: Object reference not set to an instance of an object.” Cause: NV added a new potential error message that could appear indicating that a record was not found. Solution: The text “No Record Found for Your Query” was added to potentially expected text in the response text element. 04/14/2025 MD Registration Error: Parsing framework logged the error “Message marked as fullytagged XML contains a response text element that is not an indication of record not on file. may contain unparsed Data” Cause: MD added a new error message string to their response text element. Solution: The text “Unexpected response from” was added to expected text in the response text element. 03/31/2025 NM Registration Error: Parsing framework logged the error “Unexpected Content encountered in dynamic lines” Cause: NM added a new line to their RRs that included the Original Inquiry information in their RR messages. Solution: Added handling to the parser to account for the original query information being present in all NM RR responses. 03/31/2025 MD Registration Error: Parsing framework logged the error “Message being handled by default parser, a new parser might be needed” Cause: A new ORI from MD was sending to the parsing framework. Solution: Added the ORI MDVIN0000 to the list of expected ORI for the Parsing service. 03/31/2025 MD Registration Error: Parsing framework logged the error “Message being handled by default parser, a new parser might be needed” Cause: A new error message from MD went through the parsing framework. Solution: Added “FAIL Communications issue” to the list of expected error messages from MDVIN0000. 03/18/2025 MT Registration Error: Parsing framework logged the error “Message marked as fullytagged XML contains a response text element that is not an indication of record not on file. may contain unparsed Data” Cause: MT added a new error message string to their response text element. Solution: The text “NO RECORDS MATCHING SEARCH CRITERIA” was added to expected text in the response text element. 03/17/2025 MT Registration Error: Parsing framework logged the error “Message marked as ResponseText payload does not contain a response text element” Cause: MT RRs now appear to be fully tagged. Solution: MT was added to the fully tagged message parser. 03/10/2025 PA Driver Error: The parsing framework logged the error “Message marked as fullytagged XML contains a response text element that is not an indication of record not on file. may contain unparsed Data” Cause: A new error message string was added to PA DRs Solution: Added “Error authorizing user” to the list of expected error message content for PA DRs. 02/28/2025 FL Registration Error: A user made a ticket for the name being parsed incorrectly in FLRRs Cause: There was a check for if the line containing the names began with “OR” or “AND” and removing those characters if it did. Because of the name in the RR that resulted in characters in the name being removed throwing off the line spacing. Solution: Adjusted the check to look for “OR “ and “AND “ to prevent names from being caught in the check for Or and And statements. 02/28/2025 AL Driver Error: Parsing framework logged the error “An item with the same key has already been added.” Cause: AL DRs have begun including multiple endorsements in their records. Solution: Adjusted the parser to be able to handle multiple lines of endorsements in a record. 02/19/2025 SD Registration Error: Parsing framework logged the error “Message being handled by default parser, a new parser might be needed” Cause: A new ORI is now sending RR messages to the parsing service from SD. Solution: Added SDDMV0000 to the list of ORIs going to the fully tagged RR parser. 02/19/2025 SD Registration Error: Parsing framework logged the error “Message being handled by default parser, a new parser might be needed” Cause: A new error message was added to SD and needed to be added to the expected output. Solution: The line “Record not found” has been added as an expected Not On File message for the SD parser. 02/10/2025 VA Registration Error: Parsing framework logged the error “System.IndexOutOfRangeException: Index was outside the bounds of the array.” Cause: The VA RR parser encountered a new potential not on file line. Solution: The line “RECORD NOT FOUND” was added to expected not on file messages for VA RRs. 02/10/2025 VA Registration Error: Parsing framework logged the error “System.IndexOutOfRangeException: Index was outside the bounds of the array.” Cause: The VA RR parser encountered a new potential not on file line. Solution: The line “NOTON REGISTRATION FILE IN VIRGINIA” was added to expected not on file messages for VA RRs. 02/10/2025 KY Driver Error: Parsing framework logged the error “General Error Thrown: System.NullReferenceException: Object reference not set to an instance of an object.” Cause: The KY DR parser encountered a new line in the DR message. Solution: The line “No Folio found for:” and the information following it has now been added as additional information in KY DRs. 02/10/2025 KY Driver Error: Parsing framework logged the error “Not enough lines in DR to Parse” Cause: The KY DR parser encountered a new potential error message from the state. Solution: Updated the parser to account for the error message “Your DLP request failed”. 01/24/2025 KY Driver Error: Parsing framework logged the error “Unexpected Section in Dynamic Lines” Cause: The KY DR parser added a new section to the DR to indicate if the Registration had a Real ID Solution: Updated the parser to account for the Real ID section of the DR. 01/24/2025 MO Driver Error: Parsing framework logged the error “Message marked as fullytagged XML contains a response text element that is not an indication of record not on file. may contain unparsed Data” Cause: The MO DR parser encountered a new error message that needed to be accounted for. Solution: The error message “FIELD IN ERROR:” was added to expected error messages for MO DRs. 01/24/2025 MO Driver Error: Parsing framework logged the error “Message marked as fullytagged XML contains a response text element that is not an indication of record not on file. may contain unparsed Data” Cause: The MO DR parser encountered a new error message that needed to be accounted for. Solution: The error message “MO DEPARTMENT OF REVENUE FILES ARE CURRENTLY OFF LINE” was added to expected error messages for MO DRs. 01/14/2025 TN Registration Error: Parsing framework logged the error “General Error Thrown: System.ArgumentException: An item with the same key has already been added.” Cause: This issue was caused by TN adding a phone number to their RR message. Solution: Added handling to add the phone number to the registration holder. 01/13/2025 CA Driver Error: Parsing framework logged the error “Unexpected line encountered in dynamic content” Cause: This issue was caused by CA adding a new potential error type to their messages. Solution: Added “DATA BASE UNAVAILABLE - RETRY 24 HRS” to the list of expected error messages from the CA DR parser. 01/13/2025 CA Driver Error: Parsing framework logged the error “Unexpected line encountered in dynamic content” Cause: This issue was caused by CA adding a new commercial drivers license status message to their messages. Solution: Adjusted the commercial drivers license status processing to account for the new message: “LICENSE NOT VALID FOR COMMERCIAL OPERATION/DACH PROHIBITED"