RC	Error Message	Explanation	Possible Reasons	What should I do?
5005	ERROR SOCKET	Error communicating with ApplinX server	May occur as a result of incompatible client and server version.	Check the Applinx server version (see server log) and the client version (see client log) and make sure they are of the same version and build number.
		If the host decides to close the connection with the ApplinX server, the session in the server will be disconnected and the client will receive a 5005 error, indicating that the ApplinX session is no longer active.	Host failure or network issue that made it offline. Probably more details in the host logs.	Catch this error in the client web application and act accordingly. Look into the host logs for more details.
5002	ERROR CANNOT CONNECT TO HOST	When opening a Web application page we get the following error:	Missing or insufficient permissions The host is offline. Password expired (Natural under UNIX).	Check user credentials.
n/a	Error evaluating the expression	In earlier versions, NULL and empty string were almost the same. From version 9.8 they are not, and you should actively use options like isNull() or put in a default value to avoid these errors.	Usually these errors appear after migrating procedures, see the error message in the log for more details.	Look for "If" block with the empty string or look for inputs without the default value. The error log message should help you figure out where this is coming from.
n/a	The repository is not available	Usually happens due to a Java heap space problem.	The JVM's XMX parameter memory allocation is low.	Look into the server's launch config files (startup.bat / GXApplinXService.ini) and increase the -xmx value of the JVM.
n/a	General Javascript errors	The Framework's JavaScript engine encountered an error.	Could be caused by a host key not responding, or screen that wasn't refreshed after entering a value to an input field.	Open the browser's developer tools and use them to debug the scenario until you pinpoint the root cause.
5051	Procedure Exception: Cannot run path procedure proc_name, error getting host connection, error code	Service fails to run on the local server. The error code should be "ERROR_SERVICE_NOT_ACTIVE".	Connection pool isn't active.	Check connection pool configuration. If it is set to "when first accessed", change it to "manual".
5080	ERROR_CREATING_TABLE:Screen mismatch	The developer wants to redirect the user to the main menu screen (or some other screen).	The default behavior of the ApplinX Framework when it encounters an ApplinX session error is to redirect the user to the error.JSP page. This page will specify the error code and describe the error. For example: If for some reason the ApplinX session has been disconnected, pressing a PF key in the web application will result in an error.	Customize ApplinX Framework Session Error Handling.
n/a	Replayer configuration doesn't match the current host configuration.	When running a trace file from the designer there should be a match between the Replayer to the current host configuration.	Replayer configuration doesn't match the current host configuration. For example, the Replayer Expected Model is 5 and the Host configuration Model is 2.	Open the Host configuration and change the host configuration according to the trace file.
n/a	Error in Procedure. Repeat limit reached in step step_no. 500 repetitions.	Repeat limit has been reached.	To prevent creating infitinte loops by mistake, the default repeat limit value is set to 500.	Enter a higher value for repeat limit, or specify zero, which means a record can be used an unlimited number of times.