19.3 Troubleshoot the Deployed Application
After the deployed application has been successfully installed or updated, if you encounter issues when attempting to run the application, refer to the x_err.log as you would with any other Visual LANSA application. Specifically check for warning or fatal errors.
The x_err.log file is automatically generated and updated when an error occurs, both in the development environment or when running a LANSA application.
Some useful information about the x_err.log
- All Visual LANSA applications will produce an x_err.log when an error occurs.
- The x_err.log generally exists in the user's temp directory. However, depending on a user's PC configuration, it may reside elsewhere. The best method of finding the x_err.log is to search your hard drive.
- New entries get appended to the end of the x_err.log file. Over a long period, this can cause the x_err.log file to become quite extensive. It is recommended to periodically delete the x_err.log file to remove old entries.
- When using the Deployment Tool, the x_err.log file will only be found if a LANSA application error occurs during Package creation. Messages pertaining to the Package creation are logged in a separate file lpcreate.log. Refer to Package Build Log for more information.
- In a Client/Server environment, if the application is being run on the client when an error occurs, any associated information will appear in a Fatal Error dialog box. If however, the X_RUN is running on a server (via a CONNECT_SERVER), the server cannot initiate a dialog on the client. In this case the details will be logged into the x_err.log file.
Refer to Troubleshooting in the Visual LANSA Administrator's Guide for more information.