2024 Change Log

Date State Type 12/19/2024 NM Registration

Error: Parsing framework logged the error “System.ArgumentOutOfRangeException: Index and length must refer to a location within the string.”
Cause: The fix for the previously logged parser issue of NM adding “, ,” as a potential line that could appear, was not getting hit when it should have as the line was being grabbed by an earlier part of the parser code that was then resulting in an error.
Solution: Updated the parser change the order in which the checks are hit so this line gets caught.

12/17/2024 KY Driver

Error: Parsing framework logged the error “Unexpected Content in DRIVER_ALIAS_DLNS”
Cause: KY began potentially adding “No Folio found for” to the end of some messages.
Solution: Updated the parser to be able to handle this line being at the end of some messages and added the content to additional information if it was present.

12/17/2024 KY Driver

Error: Parsing framework logged the error “Unexpected Content in DRIVER_ALIAS_DLNS”
Cause: KY began potentially adding “DMV is currently not processing image requests” to the end of some messages.
Solution: Updated the parser to be able to handle this line being at the end of some messages and added the content to additional information if it was present.

12/17/2024 VT Driver

Error: Parsing framework logged the error “System.IndexOutOfRangeException: Index was outside the bounds of the array.”
Cause: VT began to potentially send more than one Driver Restriction.
Solution: Refactored the Driver Restriction section of the parser to be able to handle more than one entry.

12/17/2024 VT Driver

Error: Parsing framework logged the error “System.IndexOutOfRangeException: Index was outside the bounds of the array.”
Cause: VT added a new potential error message of “LICENSE FILE NOT OPEN TEMPORARILY UNAVAILABLE”.
Solution: Updated the parser to be able to handle the new error line.

12/17/2024 NM Registration

Error: Parsing framework logged the error “Unexpected Content encountered in dynamic lines”
Cause: NM began potentially sending “, ,” in some records.
Solution: Updated the parser to disregard the empty line if it was present.

12/17/2024 NM Registration

Error: New Mexico indicated that it added a comma to separate the city when sending the address for RR messages.
Cause: NM has began comma separating the city name in the sent addresses.
Solution: Updated the parser to properly separate out the city name now that there is an indicator for where to split the line.

12/9/2024 NB Driver

Parsing framework logged the error “Unable to determine end of ENDORSEMENTS section”
NB stopped consistently adding a “END OF ABSTRACT” line to their DRs, so the parser was unable to find the end of the record in the endorsements section.
A check was added to the end of the processing for endorsements to account for that being the end of the record.

12/6/2024 NM 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 notification message has been added to the NM DR parser.
Solution: Updated Parsers.xml to include the new error notification message "INVALID CREDENTIALS - DLR USER ID/PASSWORD ISSUE".

12/3/2024 KY Driver

Error: A user reported that parsed messages from KY were missing the Driver Status element.
Cause: The parser was incorrectly classifying the license information as permit information. This resulted in the status information being excluded from the final message.
Solution: Updated the parser to properly categorize the license information as being from a license and not a permit.

12/3/2024 FL Driver

Error: Parsing framework logged the error “Unexpected content at the end of the DR”
Cause: FL began including "NOT AUTHORIZED TO RECEIVE DRIVER LICENSE PHOTOGRAPHS" at the end of some records.
Solution: Updated the parser to be able to account for "NOT AUTHORIZED TO RECEIVE DRIVER LICENSE PHOTOGRAPHS" being at the end of the record.

12/3/2024 CL 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: CL added the new potential error notification "VALID DLN WITH JURISDICTION ID OR LAST NAME IS MISSING".
Solution: Updated Parsers.xml to account for "VALID DLN WITH JURISDICTION ID OR LAST NAME IS MISSING" as a valid CL error notification.

12/3/2024 LA Driver

Error: Parsing framework logged the error “the CLS/OLN/DISC line has incorrect number of fields”
Cause: LA began sending "^^^^^^^^" at the end of some messages.
Solution: Updated the parser to be able to handle "^^^^^^^^" being at the end of the message.

12/3/2024 LA Driver

Error: Parsing framework logged the error “the CLS/OLN/DISC line has incorrect number of fields”
Cause: LA began sending records that contained no actual content and only zeroed out fields
Solution: Updated the parser to consider the zeroed out records as being not on file.

12/3/2024 KS Driver

Error: Parsing framework logged the error “Not Enough Lines in DR to Parse”
Cause: KS sent multi-hit records that only had two entries in them, they got flagged as being too short to be a multi-hit record.
Solution: Updated the parser to be able to handle fewer multi-hit records being present.

12/3/2024 AR Driver

Error: Parsing framework logged the error “Unexpected content encountered in Dynamic Lines”
Cause: AR started potentially having the “END OF RECORD” indicator on the same line as the end of the Medical Examiner content.
Solution: Updated the parser to still be able to recognize the data and the end of a record even if they are on the same line.

12/3/2024 AR

Driver

Error: Parsing framework logged the error “Unexpected content encountered in Dynamic Lines”
Cause: AR began potentially including images within the text response.
Solution: Updated the parser to be able to process the image being present.

12/3/2024 AR Driver

Error: Parsing framework logged the error “Unexpected content encountered in Dynamic Lines”
Cause: AR formatted their “END OF RECORD” indicator with a different number of asterisks and spaces than usual.
Solution: Updated the parser to be able to handle the change to the asterisks as well as the existing versions.

11/22/2024 WA Driver

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content: HandleSTATE_DEPARTMENTDynamicLines”
Cause: WA added new content that can appear after the Medical Attestation indicator.
Solution: Updated the check for content after the Medical Attestation indicator to account for the new potential options. The potential options are “Deaf or Hard-of-Hearing”, “Developmental Disability”, and “Medical Alert”.

11/22/2024 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: MO added a new not on file text option.
Solution: Added the new “NOT ON FILE” text option to expected response text for MO DRs.

11/22/2024 NB Driver

Error: Parsing framework logged the error “Unexpected content in after end of DR”
Cause: NB changed how the message would end occasionally for DRs.
Solution: The DR message could now end with PREV OLN, the CDL Medical Certificate, the Permit section, or the Restrictions section, the code was updated to account for these new potential ends for the message.

11/22/2024 NB Driver

Error: Parsing framework logged the error “Unexpected content in after end of DR”
Cause: NB had incorrect spacing between name and DOB in a multi-hit record.
Solution: Adjusted the code to add in the additional missing space between name and DOB for multi-hit responses.

11/22/2024 NB Driver

Error: Parsing framework logged the error “Unexpected content in after end of DR”
Cause: NB added a new Permit section to their DR responses.
Solution: Parsing was created for the newly added permit section of the DR.

11/22/2024 NB Driver

Error: Parsing framework logged the error “Unexpected content in after end of DR”
Cause: PREV OLN and PREV OLN JURISDICTION values were incorrectly swapped in the parsing of NB DRs
Solution: Corrected the flipped PREV OLN and PREV OLN JURISDICTION values so they were in the correct field when parsed.

11/22/2024 IL Registration

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: IL RRs added new potential status/additional information values.
Solution: IL added the following additional information/status items as potential items that can appear in RRs "PLATES SUSPENDED DUE TO REVOKED DLN", "OWNER ONE QUALIFIES", "REGISTRATION IS FROM THE VEHICLE MASTER FILE", "VEHICLE IN STORAGE INSURANCE", "OWNER IS PARENT OF QUALIFYING CHILD", "OWNER ONE QUALIFIES", and “REVOKED”.

11/22/2024 IL Registration

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: IL RRs now have the potential to have an additional copy of the names and addresses on the record in the message
Solution: Updated the IL RR parser to account for the appearance of the extra names and addresses if they are present.

11/22/2024 IL Registration

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: IL RRs have a chance for the OLN to be shorter than expected.
Solution: Added handling for the OLN to be in “XXXX-XX-” format.

11/22/2024 IL Registration

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: IL RRs have the chance to have the LIC line formatted differently than it was previously
Solution: Added handling to account for the different potential formats for the LIC line in IL RRs.

11/2/2024 NV Registration

Error: Parsing framework logged the error “System.NullReferenceException: Object reference not set to an instance of an object.”
Cause: A new error type was added to the NV messages.
Solution: Added "PLEASE ENTER BOTH FIRST AND LAST NAMES AND RESUBMIT" to the list of expected text content for an error notification in NV DR messages.

11/2/2024 NV Registration

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: New additional registration information was added to IL RRs.
Solution: Added “PLATES REPORTED DESTROYED”, “WINDOW TINT”, and “PLATES SUSPENDED FOR SAFETY & FINANCIAL RESPONSIBILITY” to potential additional registration information.

11/2/2024 NV Registration

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: New registration status information was added to IL RRs.
Solution: Added “EXPIRED” as a potential registration status.

11/2/2024 NV Registration

Error: Parsing framework logged the error “System.ArgumentException: An item with the same key has already been added.”
Cause: And adjustment to how not on file records are sent caused and issue in TN RRs.
Solution: Adjusted the selection process for Not On File messages to account for there being the date and time of when the message was sent being inside the message content.

11/2/2024 TN Registration

Error: Parsing framework logged the error “System.NullReferenceException: Object reference not set to an instance of an object.”
Cause: A new error type was added to the NV messages.
Solution: Added "PLEASE ENTER BOTH FIRST AND LAST NAMES AND RESUBMIT" to the list of expected text content for an error notification in NV DR messages.

11/2/2024 TN Registration

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: New additional registration information was added to IL RRs.
Solution: Added “PLATES REPORTED DESTROYED”, “WINDOW TINT”, and “PLATES SUSPENDED FOR SAFETY & FINANCIAL RESPONSIBILITY” to potential additional registration information.

11/2/2024 TN Registration

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: New registration status information was added to IL RRs.
Solution: Added “EXPIRED” as a potential registration status.

11/2/2024 TN Registration

Error: Parsing framework logged the error “System.ArgumentException: An item with the same key has already been added.”
Cause: And adjustment to how not on file records are sent caused and issue in TN RRs.
Solution: Adjusted the selection process for Not On File messages to account for there being the date and time of when the message was sent being inside the message content.

11/1/2024 IL Registration

Error: Parsing framework logged the error “System.NullReferenceException: Object reference not set to an instance of an object.”
Cause: A new error type was added to the NV messages.
Solution: Added "PLEASE ENTER BOTH FIRST AND LAST NAMES AND RESUBMIT" to the list of expected text content for an error notification in NV DR messages.

11/1/2024 IL Registration

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: New additional registration information was added to IL RRs.
Solution: Added “PLATES REPORTED DESTROYED”, “WINDOW TINT”, and “PLATES SUSPENDED FOR SAFETY & FINANCIAL RESPONSIBILITY” to potential additional registration information.

11/1/2024 IL Registration

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: New registration status information was added to IL RRs.
Solution: Added “EXPIRED” as a potential registration status.

11/1/2024 IL Registration

Error: Parsing framework logged the error “System.ArgumentException: An item with the same key has already been added.”
Cause: And adjustment to how not on file records are sent caused and issue in TN RRs.
Solution: Adjusted the selection process for Not On File messages to account for there being the date and time of when the message was sent being inside the message content.

10/28/2024 IL Registration

Error: Parsing framework logged the error “Issue Encountered: Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: Additional information was added to the message for IL RRs.
Solution: An additional OLN has the potential to be added when there is an address change pending for a Multi Owner vehicle. The parser has been updated to account for this.

10/28/2024 IL Registration

Error: Parsing framework logged the error “Issue Encountered: Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: Information output was adjusted for IL RRs.
Solution: Messages came in where the OLN came in missing all values other than the first value and two dashes (ex. A-- or A-- A--) the parser has been updated to account for this possibility.

10/28/2024 IL Registration

Error: Parsing framework logged the error “Issue Encountered: Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: Additional information was added to the message for IL RRs.
Solution: The line “EXPIRED - HAS ADDITIONAL REASONS” has the potential to appear at the end of the record. Sometimes there is an additional reason included and sometimes there is not. The parser has been updated to account for both scenarios.

10/28/2024 IL Registration

Error: Parsing framework logged the error “Issue Encountered: Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: Additional information was added to the message for IL RRs.
Solution: The line “INDICATES THAT A NEW REGISTRATION IS PENDING OR FINALIZED” has the potential to appear at the end of the record. The parser has been updated to account for this.

10/28/2024 IL Registration

Error: Parsing framework logged the error “Issue Encountered: Unexpected line encountered in dynamic content - HandleStandardResponse”
Cause: Additional information was added to the message for IL RRs.
Solution: The line “PLATES SUSPENDED FOR MANDATORY INSURANCE VIOLATION” has the potential to appear at the end of the record. The parser has been updated to account for this.

10/28/2024 MA 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 response text element was added to MA DRs.
Solution: An element containing the information “Duplicate record(s) found” was added to MA DRs. The parser has been updated to account for this.

10/21/2024 CL 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: CL had new “Not on File” response text that had not been accounted for.
Solution: Updated Parsers.xml to include the new not on file notification messages "REQUESTED RECORD NOT FOUND", "NOT ON FILE", and "DRIVER RECORD NOT FOUND".

10/11/2024 NV Registration

Error: The parsing framework logged the error “General Error Thown: System.NullReferenceException: Object reference not set to an instance of an object.”
Cause: NV sent a message with a stack trace error from their end.
Solution: Updated Parsers.xml to include the new error notification message “Unable to Send input to NLETS.DESCRIPTION”.

10/2/2024 MA Registration

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 notification message has been added to the MA RR parser.
Solution: Updated Parsers.xml to include the new error notification message “A data source connection error has occurred while processing this transaction”.

10/2/2024 MA 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 notification message has been added to the MA DR parser.
Solution: Updated Parsers.xml to include the new error notification message “A data source connection error has occurred while processing this transaction”.

9/23/2024 CL Driver

Error: The parsing framework logged the error “Message being handled by default parser, a new parser might be needed”
Cause: The CL ORI has never been hit by an ORI needing the parsing service before, and the ORI needed to be added to the list of fully tagged ORIs to parse.
Solution: Updated Parsers.xml to consider the CL ORI, CLOLN0000, to be a fully tagged ORI.

9/23/2024 PA Registration

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 notification message has been added to the PA RR parser.
Solution: Updated Parsers.xml to include the new error notification message “Error authorizing user”.

9/16/2024 FL Registration

Error: User noticed that the year that was contained in the original RR was not being transformed properly.
Cause: The line that year was contained in was not being parsed fully.
Solution: The parser was adjusted to account for the year field so it will be properly parsed from the line it is listed in.

7/23/2024 TN Registration

Error: Parsing framework logged the error “Unexpected Content encountered in dynamic content”
Cause: The line “TENNESSEE DOR IS UNABLE TO PROCESS THIS RQ MESSAGE FOR THE FOLLOWING REASON.” was added as a potential error message for TN RRs with information on what caused the query error after this.
Solution: The parser was adjusted to account for the presence of the line “TENNESSEE DOR IS UNABLE TO PROCESS THIS RQ MESSAGE FOR THE FOLLOWING REASON.” and to separate the information for the plate that cause the parsing error to include it in the body of the resulting message.

7/23/2024 NY 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: The line “TEMPORARILY UNAVAILABLE” with no semi colon was added as a potential error message for NY RRs
Solution: “TEMPORARILY UNAVAILABLE” was added to Parsers.xml to account for the new potential content.

6/7/2024 NM Registration

Error: Parsing framework logged the error “Unexpected Content encountered in dynamic lines”
Cause: The line “OCCUPANT INTERACTION:” was added to the NM RRs with no additional information after it.
Solution: The parser was adjusted to account for the presence of the line “OCCUPANT INTERACTION:” and to store any information that may appear after that message on the same line in the additional information of the RR.

6/5/2024 ID 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 response text element appeared in the body of ID DRs seemingly when their system has connection issues.
Solution: Added "com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl" to potential error messages that can appear for the DR response text.

6/5/2024 OK Registration

Error: The parsing framework logged the error “Unexpected line encountered in dynamic content_TribalResponse”
Cause: In OK RRs line containing the information for the make, model, body, and VIN of the vehicle began with a different word than expected.
Solution: Adjusted the parser to account for the line potentially starting with “BODY” and with “MODEL”.

6/5/2024 OK Registration

Error: The parsing framework logged the error “Unexpected line encountered in dynamic content_TribalResponse”
Cause: In OK RRs an additional ZIP code was added to the end of the RR record.
Solution: Accounted for there being an additional ZIP code in the DR record by adding it to additional information.

6/5/2024 AR Driver

Error: The parsing framework logged the error “Unexpected content found in the MedCert CERTIFICATE section”
Cause: AR DRs added a new potential date line to their medical certificates.
Solution: Added handling for the line “SPE EFFECTIVE DATE:” appearing in the medical certificate portion of the DR.

6/5/2024 AR Driver

Error: The parsing framework logged the error “Unexpected content encountered in Dynamic Lines”
Cause: AR DRs appear to have multi hit responses for the first time.
Solution: Adjusted the parser to account for multiple records being contained in the DR.

5/8/2024 CO Registration

Error: The parsing framework logged the error “Message marked as ResponseText payload does not contain a response text element”
Cause: The CO RR parser has been changed from text parsing to fully tagged XML.
Solution: Updated Parsers.xml to send CO RRs through the fully tagged parser instead of the text parser.

4/19/2024 GA Driver

Error: The parsing framework logged the error “Issue Encountered: Message being handled by default parser, a new parser might be needed”
Cause: GA DRs are now being sent from a new ORI.
Solution: The parsers.xml has been updated to account for the GADDS0000 ORI. And all pre-existing associated rules have been applied to the new ORI.

4/19/2024 GA Registration

Error: The parsing framework logged the error “Issue Encountered: Message being handled by default parser, a new parser might be needed”
Cause: GA RRs are now being sent from a new ORI.
Solution: The parsers.xml has been updated to account for the GADOR0000 ORI. And all pre-existing associated rules have been applied to the new ORI.

4/19/2024 VT Registration

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 text element has been added to the VT RRs.
Solution: The parsers.xml has been updated to account for the text "LICENSE PLATE TYPE NOT SUPPORTED".

04/09/2024 CA Registration

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content”.
Cause: Multiple pieces of additional information were added to the message. Or were input into the message in a different format.
Solution 1: An invalid date would be present in the field containing “PREV LIC”, adjusted the CARRParser.dll to handle this.
Solution 2: Occasionally the value “L/O: NO” would be input for lien owner information, adjusted the CARRParser.dll to handle this.
Solution 3: In an address the label “CITY:” was missing, adjusted the CARRParser.dll to handle this.
Solution 4: Additional field “POWR:” was added, adjusted the CARRParser.dll to handle this.

04/01/2024 SC Registration

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: New response text elements have been added to the RR for SC.
Solution: Added "3320 - Driver Record PDF generation error" to expected strings for the RR response text for SC.

04/01/2024 MT 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: New response text elements have been added to the DR for MT.
Solution: Added "IGNITION INTERLOCK REQUIRED" and "NSF CHECK" to expected strings for the DR response text for MT.

04/01/2024 NY Registration

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: New response text elements have been added to the RR for NY.
Solution: Added "SERVICE NOT FOUND" to expected strings for the RR response text for NY.

03/25/2024 NY 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: New response text elements have been added to DRs as part of the change to fully tagged XML.
Solution: Added "UNDEFINED EXCEPTION OCCURRED WHILE CALLING SERVICE" to expected strings for the DR response text.

03/15/2024 KY Registration

Error: The parsing framework logged the error “Message marked as fully tagged XML contains a response text element that is not an indication of record not on file. may contain unparsed Data”
Cause: New response text elements have been added to RRs as part of the change to fully tagged XML.
Solution: Added "No Vehicle Found with that Plate Number" and "Multiple Results with that Plate Number. Please Search by VIN." to expected strings for the RR response text.

02/23/2024 MD Registration

Error: The parsing framework logged the error “Message marked as fully tagged XML contains a response text element that is not an indication of record not on file. may contain unparsed Data”
Cause: A response text elements has been changed to include an additional space for RRs as part of the change to fully tagged XML.
Solution: Added "In Inventory - Unissued for Plate" to expected strings for the RR response text.

02/23/2024 MT Registration

Error: Parsing framework logged the error “Unexpected line encountered in dynamic content”
Cause: Multiple pieces of additional information were added to the message.
Solution: Refactored MTRRParser.dll to handle the newly added fields. Those fields include: “Primary Driver”, “Registration County”, “Drivers License”, “State” in association with Drivers License, “Telephone”, “Insurance Company”, “Policy”, “Sex”, and “Hull Type”.

02/20/2024 KY Registration

Error: The parsing framework logged the error “Message marked as fully tagged XML contains a response text element that is not an indication of record not on file. may contain unparsed Data”.
Cause: New response text elements have been added to RRs as part of the change to fully tagged XML.
Solution: Added "Error: LIC can't be more than 7 characters" to expected strings for the RR response text.

02/01/2024 OK Registration

Error: Parsing framework logged the error "Unexpected content encountered on the second line"
Cause: A new header message had been added to the Oklahoma RR.
Solution: Refactored OKRRParser.dll to allow for the new header string “OKLAHOMA MOTOR VEHICLE REGISTRATION RESPONSE”.

01/22/2024 TX Driver

Error: Parsing framework logged the error "MAILING ADD line 2 contains incorrect number of fields"
Cause: Almost fully empty DR messages were being sent by TX, appearing to be not on file records without the line “not on file” included in the message.
Solution: Refactored TXDRParser.dll to classify these empty DRs as not on file messages, the full content of the message will still be sent in the original text of the parsed message.

01/16/2024 KY Registration

Error: The parsing framework logged the error “Message marked as fully tagged XML contains a response text element that is not an indication of record not on file. may contain unparsed Data”
Cause: New response text elements have been added to RRs as part of the change to fully tagged XML.
Solution: Added "Error: Timeout expired" and "Results Based on" to expected strings for the RR response text.

01/12/2024 KY Registration

Error: The parsing framework logged the error “Message being handled by default parser, a new parser might be needed”
Cause: KY has changed to fully tagged xml for their RRs and the parser code needed to be adjusted to account for the change.
Solution: Adjusted Parsers.xml to process KY RRs as fully tagged XML.

01/08/2024 WY Driver

Error: Parsing framework logged the error “Unexpected Content Encountered in DynamicLines”
Cause: Additional text was added to the bottom of the DR (“KR.WYO”) that appeared to be irrelevant to the actual DR contents.
Solution: Refactored WYDRParser.dll to acknowledge the added text but not do anything with it.