Mobile Error Codes
User Assistance (UA) error codes inform users about issues that come up while using the mobile application. Errors are divided into groups according to their type, with a suggested message for each group. Additionally, each error code includes a technical description of the error and actions that your help desk team may find useful.
If you want to modify any message, inform the changes to your admin before the application is generated, as error messages are implemented while the application is built.
Refer to the table below to see each error in detail. If the error you are looking for is not on this list, contact your admin for assistance.
Error Code | Group | Message | Technical Description | Actions |
|---|---|---|---|---|
ua211 | ERR0005 | The operation could not be processed. Communication is not available, please check your settings and try again later. If the problem continues, contact our Call Center. | The mobile application cannot establish communication to execute a transaction. This problem generally occurs because the GPRS network is unavailable, either due to a lack of signal or of data services provided by the operator. If this happens in isolated cases, it indicates that it is caused by a signal problem or, to a lesser extent, that the user does not have data services enabled, either in their phone settings or by their operator. If this occurs in phones of a particular operator, and sometimes in those of a particular operator and phone brand, it indicates that the problem comes from that operator’s GPRS services. If it is a general problem, it may occur because the central processing system is unavailable. | Review the Communication Server Apache logs. Check for permission errors in either the VT-Gateway or the VT-UAS. Verify the availability of the central processing system. |
ua233 | ERR0005 | The operation could not be processed. Communication is not available, please check your settings and try again later. If the problem continues, contact our Call Center. | The mobile application cannot establish communication to execute a transaction. This problem generally occurs because the GPRS network is unavailable, either due to a lack of signal or of data services provided by the operator. If this happens in isolated cases, it indicates that it is caused by a signal problem or, to a lesser extent, that the user does not have the data services enabled, either in their phone settings or by their operator. If this occurs in phones of a particular operator, and sometimes in those of a particular operator and phone brand, it indicates that the problem comes from that operator’s GPRS services. If it is a general problem, it may occur because the central processing system is unavailable. | Verify the device settings (Date, time). Try to open the URL from a browser to verify that it can be accessed. Verify the availability of the central processing system. |
ua241 | ERR0005 | The operation could not be processed. Communication is not available, please check your settings and try again later. If the problem continues, contact our Call Center. | The Communication Server’s response is inconsistent (not a valid MSTM). If this happens in isolated cases, it indicates that it is caused by a signal problem. If this occurs in phones of a particular operator, and sometimes in those of a particular operator and phone brand, it indicates that the problem comes from that operator’s GPRS services. If it is a general problem, it may occur because the central processing system is unavailable. | Verify the availability of the central processing system. Check the VT-Gateway log. The VT-Gateway parameters for the configuration of the Device Handler may be wrong or the Device Handler may be down. |
ua257 | ERR0003 | The operation could not be processed. Please try again. If the problem continues, contact our Call Center. | The Communication Server’s response is inconsistent, as its format is not supported (MSTM format instead of MST2). The phone receives a message that cannot be interpreted, generally due to communication problems. If it is a general problem, it may be caused by issues in the central processing system. | Verify the device settings (date, time). Try to open the URL from a browser to verify that it can be accessed. Verify the availability of the central processing system. |
ua263 | ERR0003 | The operation could not be processed. Please try again. If the problem continues, contact our Call Center. | The Communication Server’s response is inconsistent, as it does not correspond to a valid product. The phone receives a message that cannot be interpreted, generally due to communication problems. If it is a general problem, it may be caused by issues in the central processing system. | Verify the availability of the central processing system. Check the VT-Gateway log. The VT-Gateway parameters for the configuration of the Device Handler may be wrong or the Device Handler may be down. |
ua269 | ERR0005 | The operation could not be processed. Communication is not available, please check your settings and try again later. If the problem continues, contact our Call Center. | The phone does not receive a response after a certain waiting time, generally due to communication problems. It may be caused by poor connectivity or because the Device Handler has discarded the message. If it is a general problem, it may be caused by issues in the central processing system. | Ask the user to try again. Test from other locations or with other networks. Verify the availability of the central processing system. Check the VT-Gateway log and the VT-NET log, if necessary, to see if the timeout values are consistent. |
ua271 | ERR0003 | The operation could not be processed. Please try again. If the problem continues, contact our Call Center. | If it is a general problem, it may be caused by issues in the central processing system. If no general problem is detected, it might be an internal error within the platform. | Verify the availability of the central processing system. Check the VT-NET log. If no general problem is detected, contact the Veritran Support team. |
ua281 ua283 ua337 ua347 | ERR0004 | The operation could not be processed. The application parameters will be updated, please try again later. If the problem continues, contact our Call Center. | If it is a general problem, it may be caused by issues in the central processing system. If no general problem is detected, it might be an internal error within the platform. | Verify the availability of the central processing system. Check the VT-NET log. If no general problem is detected, contact the Veritran Support team. |
ua379 | ERR0004 | The operation could not be processed. The application parameters will be updated, please try again later. If the problem continues, contact our Call Center. | The application cannot read or interpret information stored in its repository. If it is a general problem, it may be caused by issues in the central processing system. If no general problem is detected, it might be an internal error within the platform. | Verify the availability of the central processing system. Check the VT-NET log and the VT-Getaway log. If no general problem is detected, ask the user to try again and, if the problem continues, contact the Veritran Support team. |
ua457 | ERR0010 | There was an error. Please try again. If the problem continues, contact our Call Center. | The application unexpectedly cannot continue operating, generally while initializing. | Ask the user to exit the application and try performing the operation again. If the problem continues, contact the Veritran Support team. |
ua463 | ERR0004 | The operation could not be processed. The application parameters will be updated, please try again later. If the problem continues, contact our Call Center. | The application detects illegal data while reading or interpreting messaging information. If it is a general problem, it may be caused by issues in the central processing system. | Verify the availability of the central processing system. Check if any changes were made in the mobile application's configuration. Check the VT-NET log. |
ua523 | ERR0001 | The operation could not be processed. Please try again. | There was an error while downloading the mobile configuration, generally due to connection problems. | Verify the device's connectivity. Try to get a better connection. Get the URL of the VT-UAS to which the application is trying to connect. Validate that the URL is correct and operational. Check the VT-UAS log for more information. |
ua541 | ERR0001 | The operation could not be processed. Please try again. | The mobile configuration downloaded is inconsistent. | Ask the user to start the application again. Check if there are any problems with the Communication Servers. |
ua547 | ERR0005 | The operation could not be processed. Communication is not available, please check your settings and try again later. If the problem continues, contact our Call Center. | The mobile application successfully established a connection, but the VT-Gateway is having trouble to respond, generally because its parameters were wrongly set. | Check the VT-Gateway log. |
ua569 | ERR0001 | The operation could not be processed. Please try again. | There was a problem while negotiating the Transport Key used for Diffie Hellman End-To-End Encryption. | Identify if the error occurs in more than one mobile platform and contact the Veritran Support team. |
ua571 | ERR0001 | The operation could not be processed. Please try again. | There was a problem while validating the Certificate Pinning. | Identify if the error occurs in more than one mobile platform and contact the Veritran Support team. |
ua577 | ERR0001 | The operation could not be processed. Please try again. | There was a problem with the SSL Certificate. For example, the certificate is invalid or has expired. | Verify the device settings (Date, time). Try to open the URL from a browser to verify that it can be accessed. Verify that the VT-Gateway certificates are valid, that they have been installed correctly and that they work normally. |
ua587 | ERR0001 | The operation could not be processed. Please try again. | There was a problem with the X.509 Certificate used for PKI End-to-End Encryption. | Identify if the error occurs in more than one mobile platform and contact the Veritran Support team. |
ua593 | ERR0001 | The operation could not be processed. Please try again. | An exception message was received. The response code of the message might need to be analyzed by the Veritran Support team to understand the error. If it is a general problem, it may be caused by issues in the central processing system. If no general problem is detected, it might be an internal error within the platform. | Verify the availability of the central processing system. Check the VT-NET log. If no general problem is detected, ask the user to try again and, if the problem continues, contact the Veritran Support team. |
ua599 | ERR0015 | A security risk has been detected on the device. | The application detected a security risk on the device. This may happen because the device has been rooted or because the application is being debugged or run in an emulator. | If you can confirm that the device has been rooted, ask the user if any unofficial update was recently downloaded (an operating system update, for example). If nothing is out of the ordinary, retrieve the device information (brand, model, operating system version) and contact the Veritran Support team. |
ua607 | ERR0010 | There was an error. Please try again. If the problem continues, contact our Call Center. | A problem has been detected while executing the Application Parameters Call API. | Ask the user to try again. If the error persists the application may need to be uninstalled. Identify if the error occurs in more than one mobile platform and contact the Veritran Support team. |
ua613 | ERR0010 | There was an error. Please try again. If the problem continues, contact our Call Center. | A data integrity problem in the mobile configuration has been detected. | Ask the user to start the application again. The application deletes the mobile configuration and downloads a new one when restarted. Verify that the mobile configuration file published in the VT-UAS is not corrupted. |
ua617 | ERR0017 | Invalid configuration detected. Please try again. If the problem continues, contact our Call Center. | An invalid configuration in the screens or the processes has been detected. | Use the information shown on the device screen to identify the process or screen that is causing the error and verify that it exists in the mobile configuration. |