Troubleshooting
This section provides information about the error messages sent by CT-V Bulk Utility. It covers the following topics:
Error Codes
CT-V Bulk Utility can issue the following error codes. Use this table to translate the numeric code into helpful text.
| Number | Error Message | Description |
|---|---|---|
| 27 | Cannot write to the log file | The utility cannot write to the log file. Check the log file permissions and the name of the log file specified in the IngrianNAE.properties file. |
| 28 | Cannot connect | The utility cannot connect to the Key Manager. Check the network settings and check the IP address, port and protocol specified in the IngrianNAE.properties file. |
| 202 | NAE error: Invalid user | The supplied username/password combination is not valid. |
| 206 | Missing credentials | The password and authorization token are missing or invalid. |
| 220 | Insufficient permissions | The user does not have permission to perform the requested operation. Check the permissions in the Key Manager UI and see what operations are available. Try a different user. |
| 230 | NAE authentication required | The client must authenticate to the Key Manager with a valid username and password. |
| 1302 | Invalid operation | The attempted cryptographic operation is not permitted for this key. Check the key’s permissions on the Key Manager UI. |
| 1304 | Invalid operation-algorithm pair | The attempted cryptographic operation is not valid for this key. Check the valid operations on the Key Manager. This error also appears if the key specified for keyed hash operation is not a hash key. |
| 1320 | Invalid or missing algorithm | The correct algorithm must be specified for each used key. Check the Input Configuration File. Compare the Algorithm elements with the key’s algorithm as listed on the Key Manager. |
| 1321 | Unknown algorithm | The correct algorithm must be specified for each used key. Check the Input Configuration File. Compare the algorithm elements with the key’s algorithm as listed on the Key Manager. |
| 1323 | Invalid algorithm for key | The correct algorithm must be specified for each used key. Check the Input Configuration File. Compare the algorithm elements with the key’s algorithm as listed on the Key Manager. |
| 1340 | Invalid IV | The specified IV is not valid for this key. Check the input configuration file. Remember that IV values must be base 16 encoded. |
| 1343 | Invalid IV size | The specified IV is not the correct size for this key. |
| 1400 | NAE error: Invalid key name | The keyname specified in the Input Configuration File does not exist on the Key Manager. Review the value in the Input Configuration File and check the list of available keys on the Key Manager UI. |
| 1401 | NAE error: Unknown key | The keyname specified in the Input Configuration File does not exist on the Key Manager. Review the value in the Input Configuration File and check the list of available keys on the Key Manager UI. |
| 1423 | NAE error: Invalid or missing key data | The key information included in the Input Configuration File is incomplete or invalid. Review that file and compare the information with the key details on the Key Manager UI. |
| 1426 | NAE error: Invalid permissions | The user specified on the command line does not have permission to use one of the keys listed in the Input Configuration File. Use a different user, a different key, or change the key permissions or the user’s group membership. |
| 1602 | Missing user name | The user name was missing from the request. Check the command line parameters. Include a valid NAE user name. |
| 1603 | User does not exist | The user name specified in the command line does not exist on the Key Manager. Compare the user on the Key Manager UI with the user name passed with the -u flag on the command line. |
Error Messages
CT-V Bulk Utility can issue the following error messages. Use this table to translate the messages into troubleshooting advice.
| Error Message | Description |
|---|---|
| File Not Found | Input/output files are not present in the classpath. |
| Connections could not be acquired from the underlying database | Database username/password is not correct. |
| An attempt by a client to checkout a Connection has timed out | Database is not up and running and not reachable and DB username/password is not correct. |
| The key is not valid | AES/HmacSha256 key does not exist on the Key Manager. |
| Unknown key name or insufficient permissions | Username does not have permission on keys. |
