Considerations for Ingres and 4GL Runtime Errors
In general, if the error message returned by the front-end application is “OpenROAD ORASO Application Server (0x8004A000) Ingres or 4GL runtime error: 0x00000001”, its cause is Ingres-related and should be approached as an Ingres problem. The following are situations that can cause such problems. Use common sense when deciding the order in which to check for causes, based on the nature of the problem.
• Ensure that Ingres is running on the OpenROAD Server side and the databases side if the OpenROAD Server is connecting to a remote database.
• Check the W4GL log file on the OpenROAD Server side for errors. The log is typically located in the %II_STSTEM%\ingres\files directory.
• Check the application log (specified by the -L flag) for errors.
• Check for errors in the errlog.log of the Ingres installation on the OpenROAD Server side as well as the database side if the AppServer is connecting to a remote database.
• If the front-end application is a web application (that is, IIS is involved in some way) ensure that the VNODE information (connection and login) is defined as GLOBAL because IIS has no access to any PRIVATE vnode information.
• Ensure that the OpenROAD Server image can be run successfully using the runimage command as if it were an image of a regular OpenROAD application.