This section lists some of the common errors you may encounter while using the Forms and the Web Transaction test type. The following topics are covered here:
The section covers the following:
This section lists some of the common errors you may encounter while playing back a Forms transaction and provides suggestions to resolve these errors.
Error Message: Connection to Forms Server is lost. Possible version mismatch between agentjars and formsjars.
Possible Cause: The transaction was recorded using an out-of-the-box Forms version.
Solution: Verify the version of the Forms Application that you are running by checking the version number in the About Oracle Forms Online Help. If this version is not supported, follow the steps listed under Error Message 2.
Error Message: Version Not Supported <forms_version>
Possible Cause: The machine on which the beacon has been installed does not contain the necessary forms jar files.
Solution: To resolve this error, follow these steps:
Login to the system on which the Forms server has been installed. Locate the frmall.jar (if you are using Forms 10.1 or later) or f90all.jar (if are using Forms 9.0.4 or later) under the $FORMS_HOME/forms/java directory.
Login to the system on which the beacon has been deployed and copy the jar file to the $ORACLE_HOME/jlib/forms/<version>/ directory. The version you specify here should be the same as the version string in the error message. Make sure that the directory is empty before you copy over the jar file.
If you are using Oracle Applications R12 and you encounter this error, follow these steps to resolve the error:
Login to the system in which the Oracle Application server has been deployed. Locate the following files:
$JAVA_TOP/oracle/apps/fnd/jar/fndforms.jar $JAVA_TOP/oracle/apps/fnd/jar/fndewt.jar
Login to the system on which the beacon has been deployed and copy these files to the $ORACLE_HOME/jlib/forms/apps/ directory. Make sure that the directory is empty before you copy over the jar files.
Note:
You cannot monitor two deployments of Oracle Applications from the same beacon if different versions of Oracle Applications have been used.
Error Message: Forms URL is not pointing to the forms servlet.
Possible Cause: When the Forms transaction was recorded, the location of the forms servlet could not be determined.
Solution: Make sure that the Forms URL Parameter is pointing to the forms servlet. It should be http://<hostname>:<port>/forms/frmservlet for Forms10g or http://<hostname>:<port>/forms/f90servlet for Forms 9i. This parameter is automatically set by the Forms Transaction Recorder. But if it has not been set, you can locate the URL by following these steps:
Launch the Forms application.
View the source HTML file in the Forms launcher window.
Locate the xsurl variable. The URL is stored in this variable.
Error Message: Could not connect to <machine name>.
Possible Cause: The machine on which the beacon has been installed cannot access the Forms Application.
Solution: Make sure the machine on which the beacon has been installed can access the Forms Application and firewalls have been properly configured. Support for playing back Forms transactions through proxy server is not available in this release.
Error Message: Invalid module path in the initial message.
Possible Cause: The transaction may have been incorrectly recorded or may be corrupt.
Solution: Try to record the transaction again.
Error Message: Cannot connect to login server.
Possible Cause: This error may occur due the following reasons:
The Login URL that you have specified may be incorrect.
An invalid HTTPS certificate may have been provided for the login server.
Solution:
Verify that the Login URL is correct.
If you are using HTTPS to connect to login server, make sure the certificate on the server is written for the login server machine itself. Make sure the SSL Certificate is imported into Agent and the CN of the certificate matches the host name of the login Server URL.
This section lists some troubleshooting steps that you can use when the Forms transaction cannot be recorded successfully.
Make sure that all your Internet Explorer instances are closed and no java runtime programs are open.
Start recording again with the java console open. You can view any exceptions or error messages displayed on the console.
You should now see the text "Forms Transaction Recorder Version: <version number>" on the console. If this text is displayed, proceed to step 5. If you do not see the text, check if the formsRecorder.jar has been copied to the Forms archive directory. You can perform this check using either of the following methods:
Navigate to the Forms archive directory and check if the formsRecorder.jar file is present in the directory.
Navigate to the Enable Forms Transaction Monitoring page, select the corresponding Forms server target and click Configure. Enter the host credentials to see if the Forms Transaction Recorder has already been configured on this Forms server. If the formsRecorder.jar is not present in the Forms archive directory, you need to configure your Forms server for transaction monitoring. After ensuring that the formsRecorder.jar is present in the archive directory of the Forms server, go back to Step 1 and try recording again.
If you see an exception related to the java .policy file displayed on the java console, check the file to ensure that it has the required content and is in the right location. If any errors are found, you must fix these errors and try recording again.
If the recording still fails, check if the Enterprise Manager Certificate has been imported to the secure site.f the certificate has not been imported, you must import it and try recording again.
Note:
In Enterprise Manager 13.1, the Web Transaction recording and playback (including Browser Simulation) feature is not available. You cannot record new transactions or play back existing Web transactions.
This section lists some of the common errors you may encounter while recording and playing back Web Transactions.
Scenario: Verify Service Test displays: Connection establishment timed out -- http://..../
Possible Cause: The beacon can only access that URL via a proxy server and it has not been configured.
Solution: From the All Targets page, select the beacon, click Configure and set the beacon proxy setting.
Scenario: Verify Service Test displays: Authorization Required -- https://...../
Possible Cause: The Basic Authentication information is not recorded automatically.
Solution: To resolve this error, follow these steps:
From the Service Tests and Beacons page, select the service test, click Edit.
Make sure you enter all the Basic Authentication information: Username, Password, and Realm.
Note:
Realm usually appears above the Username label in the Browser's authorization dialog box.
Scenario: Verify Service Test displays sun.security.validator.ValidatorException: No trusted certificate found -- https://....../.
Possible Cause: The beacon does not know about this SSL Certificate.
Possible Solution: From the Service Tests and Beacons page, select the service test, and click Edit. Under Advanced Properties, and set Authenticate SSL Certificates to No.
Scenario: Verify Service Test displays: Timeout of 300000 exceeded for https://....../ Response time = 3000000
Possible Cause: The test may be too complex to complete within the allotted time. Or, this may be an actual performance issue with the server.
Possible Solution: From the Service Tests and Beacons page, select the service test, and click Edit. If this is not a server performance issue, under Advanced Properties, increase the Timeout Value.
Scenario: The Verify Service Test option reports that the service as down, but the Web application is up and you can successfully play back the Web transaction.
Possible Cause: The Web application is only compatible with Internet Explorer or Mozilla-based browsers.
Possible Solution: From the Service Tests and Beacons page, select the service test, and click Edit. Under Advanced Properties, set the User Agent Header as Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) OracleEMAgentURLTiming/3.0.
Note:
For Enterprise Manager 10.2.0.4 and beyond, this User Agent Header is set automatically during Web transaction recording.
Scenario: Test Performance Page does not show any step metrics.
Possible Cause: By default, only transaction-level metrics are collected.
Possible Solution: From the Service Tests and Beacons page, select the service test, click Edit, and set Data Granularity to Step.