Reason Behind Various Cass Error Codes We Face!

Reason Behind Various Cass Error Codes We Face!

• Error no. 1.1: State not found.  The input record state is not a valid two-character abbreviation.

• Error no. 2.1: City not found.  The input record city is not in AccuZIP6’s list of cities for the input record state.

• Error no. 3.1: Street not found.  The input record street is not in AccuZIP6’s list of streets for the input record city; usually caused by misspelled street names that AccuZIP6 can’t determine how to correctly spell.

• Error no. 4.1: Address not found.  The input record has an address not found in AccuZIP6’s list of addresses for the input record street.  Caused by an out-of-range (including even/odd mismatched) house or apartment no.

• Error no. 5.1: Incomputable +4 range.  AccuZIP6 can’t compute the ZIP+4 code for the address because of non-numeric characters in the input record house no. or in the LOW to HIGH or LO+4 to HI+4 fields of the database as shown in the address window.  AccuZIP6 will output the correct five-digit ZIP code.

• Error no. 5.2: +4 unavailable.  As shown in the addresses window, a complete LO+4 add-on code is unavailable; usually because the database thinks this address is still an undeveloped lot.  AccuZIP6 will output the correct five-digit ZIP code.

• Error no. 6.1: Multiple streets match.  The input record is ambiguous, because more than one street name in the database matches the input address, and there is not enough information to let AccuZIP6 choose between the multiple choices.  For example, if the database lists only and E MAIN ST and a W MAIN ST, then the input MAIN ST causes multiple matches.

• Error no. 6.2: Multiple addresses match.  The ZIP+4 database is ambiguous, because more than one ZIP+4 database record matches the input address. For example, if a street has an address record for houses no. that from 100 to 500, and another record for houses no. that from 300 to 600, then the address 400 is a multiple match to both records.

• Error no. 6.3:  Cardinal Rule Multiple Match.  The input record had a street name that was also the suffix.  For example, 100 Road Street would have the wrong suffix, and in that case, the address matching engine is not allowed to add the correct suffix.

• Error no. 7.1: Time ran out.  The optional maximum time limit for processing this address was set too low.

• Error no. 7.2: Output too long.  An output record (the length of all fields and field delimiters) exceeds 2000 characters.  Fields at the end of the record will be lost.