A script-enabled browser is required for this page to function properly.

FRM-92050

Cause: Heavy load on the server. There are too many simultaneous requests that the server cannot handle. This mainly depends on the server machine performance and configuration. This error can occur when:

Action: Use the Oracle Forms Runtime Prestart feature of Oracle Forms 10g. This feature pre-spawns a configurable number of runtime engines to respond to the incoming client requests and avoiding system hangs because of a rush. Upgrade the hardware of the server machine to handle the high number of simultaneous requests.

Cause: Missing serverURL parameter in the configuration file (formsweb.cfg).

Action: Edit the forms configuration file to enter a valid serverURL parameter value.

Cause: The value of FORMS_TIMEOUT parameter is incorrect.

Action: Verify the envfile (default.env) and the registry for the FORMS_TIMEOUT parameter value. The value should be an integer. The value should not be in quotes.

Cause: Incorrect Use of RUN_PRODUCT. RUN_PRODUCT should only be used in Oracle Forms 9.0.x for integration with
Oracle Graphics 6i.

Action: RUN_PRODUCT Built-in calls to integrate Forms with Oracle 9.0.2 Reports should be replaced using the newer RUN_REPORT_OBJECT Built-in.

Cause: Missing ServerArgs parameter from the HTML file that loads the applet.

Action: Make sure that the HTML file that loads the Forms applet has the serverArgs parameter in it. Make sure that the value of the serverArgs is not null. Remember, the Form name is required in serverArgs. These parameters can be defined in the Forms configuration file (formsweb.cfg) or can be directly passed in the URL that calls the Form.

Cause:The forms web executable frmweb.exe is not able to find the jvm.dll.

Action: Ensure that jvm.dll is located in a directory specified in the PATH environment variable. Set the PATH environment variable in the formsweb.cfg’s envFile (typically ORACLE_HOME/forms/server/default.env) to point to the location of the jvm.dll.