This page (revision-23) was last changed on 26-Nov-2021 10:22 by ibarr

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
23 26-Nov-2021 10:22 8 KB ibarr to previous
22 26-Nov-2021 10:22 8 KB rforbes to previous | to last
21 26-Nov-2021 10:22 8 KB jmyers to previous | to last

Page References

Incoming links Outgoing links
SOFTWARE_INSTALLATION.TROUBLESHOOTING
SOFTWARE_INSTALLATION.TROUBLESHOOTING

Version management

Difference between version and

At line 16 added one line
\\ \\
At line 17 removed one line
\\ \\
At line 19 changed 5 lines
!Problem
There is an attempt to run a report in [{$applicationname}] and a red bar is automatically encountered, indicating the report has failed.
!Solution
*Review your [IMST] preferences by ensuring all reports preferences are correct. See step 6: configuring IMST preferences. [Configure IMST Preferences|SOFTWARE_INSTALLATION.CONFIGURING_BI#ConfigureEPersonalityIMSTPreferences]
*Review the OPMN logs for any errors with the MEX ID of the report that failed. If you are unable to determine the cause the problem from the logs, please upload the logs to support for review.
;Problem:There is an attempt to run a report in [{$applicationname}] and a red bar is automatically encountered, indicating the report has failed.
;Solution:Review your [IMST] preferences by ensuring all reports preferences are correct. See step 6: configuring IMST preferences. [Configure IMST Preferences|SOFTWARE_INSTALLATION.CONFIGURING_BI#ConfigureEPersonalityIMSTPreferences]\\ \\Review the OPMN logs for any errors with the MEX ID of the report that failed. If you are unable to determine the cause the problem from the logs, please upload the logs to support for review.
\\ \\
At line 25 removed one line
\\ \\
At line 28 changed 6 lines
!Problem
A configuration change such as changing the OC4J instance port prevents it from starting up due to port conflict.
!Solution
Ensure all the OC4J containers are configured with a static port. From a command prompt, run the below command from the following directory: AS10G_RL3|AS10G_BI/bin\\ \\opmnctl status –fmt %prt%por\\
*Make a note of the RMI ports assigned to each OC4J container and update the OPMN.XML file by assigning a free port to the OC4J instance that failed to start.
*Reload and start the container.
;Problem:A configuration change such as changing the OC4J instance port prevents it from starting up due to port conflict.
;Solution:Ensure all the OC4J containers are configured with a static port. From a command prompt, run the below command from the following directory: AS10G_RL3|AS10G_BI/bin\\ \\opmnctl status –fmt %prt%por\\ \\Make a note of the RMI ports assigned to each OC4J container and update the OPMN.XML file by assigning a free port to the OC4J instance that failed to start.\\ \\Reload and start the container.
\\ \\
At line 35 removed one line
\\ \\
At line 37 changed 4 lines
!Problem:
When a user runs a report and an output link is created to open the report, click the link does not open the report.
!Solution:
• Review your IMST preferences ATTACHMENTS_FLDR and ensure the path is correctly specified. The path is relative to the Oracle Application Server.
;Problem:A report is run and an output link is created to open the report. When the link is clicked, the report is not opened.
;Solution:Review your [IMST] preferences ATTACHMENTS_FLDR and ensure the path is correctly specified. The path is relative to the Oracle Application Server.
\\ \\
At line 42 removed one line
\\ \\
This page (revision-23) was last changed on 26-Nov-2021 10:22 by ibarrTop