| Code |
Description |
Troubleshooting Tips |
| 101 |
Fixed format inquiry (FFI) segment contains an invalid segment ID. |
- Fixed format inquiry record contains an invalid segment ID element name or invalid country code, invalid country code, or the sum of the individual segment lengths is invalid.
- Refer to the TU4.0 User Guide or TU4.1 User Guide for proper segment specifications.
- Check input to ensure accurate information and retry.
|
| 102 |
Invalid input FFI message type. |
- Occurs when first segment is not TU4.0\TU4.1.
- Check input to ensure properly formatted segments and resend transaction.
|
| 105 |
Invalid version switch. |
- Occurs when first segment is not TU4.0\TU4.1.
- Check input to ensure accurate information and retry.
|
| 106 |
The number of Policy segments exceeds the maximum allowed. |
- Only one Policy segment is allowed per service.
- Check input, delete any extra segments and resend transaction.
|
| 107 |
Location information segment is not present in the FFI. |
- Occurs when the input does not contain the Location segment when requesting the service.
- Check input, ensure the location segment is present, and resend transaction.
|
| 117 |
The length of the Fixed format inquiry (FFI) is invalid. |
- Occurs when an incomplete FFI is received or when the ENDS / END1 segment is not the last segment in the FFI.
- Refer to the TU4.0 User Guide or TU4.1 User Guide for proper segment specifications.
- Check input to ensure proper format and sequence of segments and resend transaction.
|
| 130 |
Number of Address segments exceeded maximum allowed per transaction. |
- Occurs when there are more address segments provided on input than allowed.
- Check input, delete any extra segments and resend transaction.
|
| 131 |
Number of Customer Information segments exceeded maximum allowed per subject. |
- Only one Customer Information segment allowed per subject.
- Check input, delete any extra segments and resend transaction.
|
| 132 |
Number of address segments exceeds maximum allowed per subject. |
- Only one address segment per subject.
- Check input, delete extra segments, and resend transaction.
|
| 133 |
Number of Employment Address segments exceeded maximum allowed per subject. |
- Only one Address Segment per subject.
- Check input, delete any extra segments and resend transaction.
|
| 134 |
Number of Additional Information segments exceeded maximum allowed per subject. |
- Only one Additional Information segment per service.
- Check input, delete any extra segments and resend transaction.
|
| 135 |
Number of Credit Card segments exceeded maximum allowed per subject. |
- Only one Credit Card segment per subject.
- Check input, delete any extra segments and resend transaction.
|
| 136 |
Number of Employment Segments exceeded maximum allowed per subject. |
- Only one Employment segment per subject.
- Check input, delete any extra segments and resend transaction.
|
| 137 |
Number of End User segments exceeded maximum allowed. |
- Only one End Usage segment per FFI.
- Check input, delete any extra segments and resend transaction.
|
| 138 |
Number of Future Address Segments exceeded maximum allowed per subject. |
- Only one Future Address segment per subject.
- Check input, delete any extra segments and resend transaction.
|
| 139 |
Number of Identification segments exceeded maximum allowed per subject. |
- Only one Identification segment per subject.
- Check input, delete any extra segments and resend transaction.
|
| 140 |
Number of Primary Name segments exceeded maximum allowed per subject. |
- Only one Primary Name segment per subject.
- Check input, delete any extra segments and resend transaction.
|
| 142 |
Number of Alias name segments exceeded maximum allowed per subject. |
- Only three alias Name segments per subject.
- Check input, delete any extra segments and resend transaction.
|
| 143 |
Number of Output Delivery segments exceeded maximum allowed. |
- Only two Output Delivery segments per one output type.
- Check input, delete any extra segments and resend transaction.
|
| 144 |
Number of Optional Request segments exceeded maximum allowed. |
- Only one Optional Request segment per service.
- Check input, delete any extra segments and resend transaction.
|
| 145 |
Number of Personal Information segments exceeded maximum allowed per subject. |
- Only one Personal Information segment per subject.
- Check input, delete any extra segments and resend transaction.
|
| 146 |
Number of Phone Number segments exceeded maximum allowed per subject. |
- Only one Phone Number segment per subject.
- Check input, delete any extra segments and resend transaction.
|
| 147 |
Number of Employment Phone Number segments exceeded maximum allowed per employment. |
- Only one Phone Number segment per subject.
- Check input, delete any extra segments and resend transaction.
|
| 148 |
Number of Request Add-On segments exceeded maximum allowed. |
- Only twenty Request Add-on Service segments per service.
- Check input, delete any extra segments and resend transaction.
|
| 149 |
Number of Request Service segments exceeded maximum allowed. |
- Check input, delete any extra segments and resend transaction.
|
| 151 |
Number of Subject Header segments exceeded maximum allowed. |
- Only two Subject Header segments per FFI.
- Check input, delete any extra segments and resend transaction.
|
| 152 |
Number of Transaction Control segments exceeded maximum allowed. |
- Only one Transaction Control segment per FFI.
- Check input, delete any extra segments and resend transaction.
|
| 154 |
Subject information found after service information. |
- Fixed format inquiry record contains subject segments out of proper sequence.
- Check input to ensure properly formatted segments and resend transaction.
|
| 155 |
No subject data found for subject header. |
- FFI must contain at least one of these segments: Name, Personal Information, or Address. This error is returned only if none of these segments is present.
- Check input to ensure properly formatted segments and resend transaction.
|
| 157 |
Subject data found without subject header. |
- Fixed format inquiry record does not contain a Subject Header segment for subject data.
- Add at least one Subject Header segment, ensure properly formatted segments and resend transaction.
|
| 158 |
Request service header not present in FFI. |
- FFI does not contain a Request Service segment.
- Add at least one Request Service segment, ensure properly formatted segments and resend transaction.
|
| 159 |
Service Data found without request service segment. |
- FFI does not contain a Request Service Segment for service data.
- Add at least one Request Service segment, ensure properly formatted segments and resend transaction.
|
| 160 |
End user segment not in proper order. |
- EU01 segment does not immediately follow the TU4I segment.
- Add at least one Request Service segment, ensure properly formatted segments and resend transaction.
|
| 162 |
Invalid Name Type in Name Segment. |
- See Name segment description, update with proper name type and resend transaction.
|
| 170 |
Invalid segment count. |
- Only one Customer Data segment per service.
- Check input, delete extra segments, and resend transaction.
|
| 171 |
Segment out of order. |
- Occurs when the CD01 segment does not immediately precede the SH01 segment.
- Refer to the TU4.0 User Guide or TU4.1 User Guide for proper segment specifications and segment order.
- Check input to ensure proper format and sequence of segments and resend transaction.
|
| 172 |
Required segment missing or invalid. |
- Occurs when the fixed format inquiry (FFI) does not include a Customer Data segment.
- Refer to the TU4.0 User Guide or TU4.1 User Guide for proper segment specifications.
- Ensure the FFI includes the Customer Data (CD01) segment coded if you are using the TransUnion Net Access (TUNA) connectivity method.
- Check input for proper format and resend transaction.
|
| 174 |
Vendor Information segment missing. |
- Vendor Information segment is required for service.
|
| 175 |
Number of Vendor Information segments exceeded maximum allowed. |
- Only one Vendor Information segment.
- Check input, delete extra segments and resend transaction.
|
| 181 |
Number of Decisioning Request Service segments exceeded maximum allowed. |
- Only two Request Service segments allowed.
- Check input, delete extra segments and resend transaction.
|
| 182 |
Number of Decisioning Request Service segments less than minimum required. |
- Minimum of two Request Service segments required if one is present.
- Check input, add additional segment, and resend transaction.
|
