How Do I Know I Have Hit a False Positive (Seed) Violation?

A False Positive (Seed) violation error message is generated by the CASS certified coding application used for DPV and/or LACSLink processing. For example, if you encounter a False Positive (Seed) violation using VeriMove internal CASS processing, the following occurs:

  1. The function (DPV or LACSLink) generating the False Positive (Seed) violation stops processing.
  2. The VeriMove job continues to run to completion.
  3. The error message shown below is written to the event log file:
    • DPV Seed Violation Message:

      20124 - DPV RUN VIOLATION…SEED RECORD HIT


      "CALL PB-DMT TECH SUPPORT CASE 4 DPV4"

    • LACS Seed Violation Message:

      PCLERR_LACSVIOLATION (20152): Occurred during LACSLink seed violation.

  4. VeriMove does not generate the USPS Form 3553 (CASS Summary Report).
  5. For Windows, Unix, and Linux environments, VeriMove creates a "seedlog.txt" file in your VeriMove directory containing the False Positive (Seed) violation.
  6. The function (DPV or LACSLink) generating the False Positive (Seed) violation cannot process subsequent jobs until a re-activation key is applied. Attempts to run VeriMove after a False Positive (Seed) violation before acquiring a new key will result in one of the following messages in the event log:
    • DPV:

      Internal CASS Engine Error: Return code = CASS System Error - 20124 DPV


      Processing Error Call PB-DMT tech support Case 4 DPV4.

    • LACSLink:

      Internal CASS Engine Error: Return code = CASS System Error - LACS Error:

      Function Name: callLacsInit Msg: LACSLinkInit() Failed.