Using In-process Reports Server Causes FRM-41213 After System Startup

Oct 11, 2012

If you have the in-process reports server (rep_wls_reports_hostname_asinst_1) configured for generating reports, there have been situations where FRM-41213 occurs after startup of either WLS_REPORTS or the server/PC itself. FRM-41213 means that Forms is unable to connect to the reports server (either the in-process reports server which runs inside WLS_REPORTS or the standalone reports server which is a separate instance from WLS_REPORTS).

There are two solutions which can solve the problem:

  • Using the standalone reports server (usually called RptSvr_hostname_asinst_1)
    1. Go to your env file associated to your Forms application.
    2. Look for a variable called ‘APP_RS’ or ‘RSERV’. (If they do not exist, skip to step 4)
    3. Change the value of the variable from the in-process reports server to the standalone reports server. Save any changes made in the file.
    4. If the reports server is referenced directly in your WHEN_NEW_FORM_INSTANCE trigger, you will need to make the change specified in step 3 in the form itself. Save and recompile the form.
  • Starting the in-process reports server before using application (methods shown below)
    • Starting the in-process reports server through Enterprise Manager FMW Control (only possible for 11g)
    • Starting the server by URL: http://hostname:port/reports/rwservlet/startserver
    • Calling anything in rwserver by URL (Example: Go to Showjobs at http://hostname:port/reports/rwservlet/showjobs)

If you choose to switch to the standalone reports server, it will always be running after starting up your system as all OPMN processes start automatically in Windows. The standalone reports server will be ready instantly to generate Oracle Reports as soon as all WebLogic servers are up and running.

NOTE: For 12c, OPMN is no longer used for managing the standalone reports server. Although the in-process reports server continues to be managed by WLS_REPORTS, the standalone reports server is now controlled by the Node Manager. However, the Node Manager can also be configured to automatically start up on startup.