1. Flexible Reporting Extensibility Guide
  2. Troubleshooting
  3. Troubleshooting PMDA (R3) Paper Forms

Troubleshooting PMDA (R3) Paper Forms

Issue Cause Resolution

Missing or invalid junk characters instead of Japanese characters

Japanese fonts are not installed in the BI Publisher Server

Follow Oracle Argus Safety Installation Guide section 13.2.1 Installing and Configuring East Asian Fonts

Error message:

The server cannot be used due to a configuration error, please contact the administrator.

If you are the administrator, please consult BI Publisher user guide for proper configuration. Error DetailResourceProvider is null"

The catalog privileges are not set properly.

Follow Oracle® Argus Safety Installation Guide section 13.3.3.2 Managing Folder Privileges

Unable to manually generate (R3) Paper report from Argus UI

The BIP Common user ID or password entered for the BIP Aggregate Reporting Common Profile Switch is wrong or empty

Make sure there is a user ID present in the BIP Reporting common profile switches. Verify that the BIP Common User and Password present in this switch can login to the BI Publisher console. Also, make sure that the user ID has complete access to all PMDA (R3) Paper Forms.

Unable to manually generate (R3) Paper report from Argus UI

The Report path in the REPORT_TEMPLATE is empty or has an incorrect path

The Report path present in the code list REPORT_TEMPLATE must have a proper value. The value can be verified by comparing it against the actual report path in the BIP Publisher catalogs. In Linux/Unix the report path is case sensitive.

Unable to manually generate (R3) Paper report from Argus UI

The endpoint address present in the Web.config file is incorrect

Confirm the following:

  • The endpoint address is present
  • It points to the BI Publisher Server (including the port number).
  • No unnecessary space is present in the URL.

Services are properly mentioned SecurityService is mapped against SecurityService, and ScheduleService is mapped against SchedulingService and ReportService is mapped against ReportService

Unable to manually generate (R3) Paper report from Argus UI

Missing Argus UI user in the BI Publisher

Make sure that the Argus UI user exists and is allowed to login and run the required reports from BI Publisher Console

Unable to generate (R3) Paper report through Auto Schedule

(Reports are running fine manually)

The endpoint address present in the agproc.config file is incorrect

Confirm the following:

  • The endpoint address is present
  • It points to the BI Publisher Server (including the port number).
  • No unnecessary space is present in the URL.

Services are properly mentioned SecurityService is mapped against SecurityService, and ScheduleService is mapped against SchedulingService and ReportService is mapped against ReportService

Unable to generate (R3) Paper report through Auto Schedule

(Reports are running fine manually)

Missing AG Service user (user ID used for Batch report generation) in the BI Publisher

Make sure that the AG service user exists and is allowed to login and run the required reports from the BI Publisher Console

UserID: AG_batch_periodic_reports, Login to BIP Server failed

Exception Details Message:

The request channel timed out while waiting for a reply after 00:00:59.5468739. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout

Timeout occurs while calling the BIP server

Add/Modify the following in C:\Program Files (x86)\Oracle\Argus\Argus Safety\ AGProc.config:

<binding name="SecurityServiceSoapBinding" maxReceivedMessageSize="2147483647" openTimeout="00:10:00" closeTimeout="00:10:00" sendTimeout="00:10:00" receiveTimeout="00:10:00"/>

<binding name="ScheduleServiceSoapBinding" maxReceivedMessageSize="2147483647" openTimeout="00:10:00" closeTimeout="00:10:00" sendTimeout="00:10:00" receiveTimeout="00:10:00"/>

<binding name="ReportServiceSoapBinding" maxReceivedMessageSize="2147483647" openTimeout="00:10:00" closeTimeout="00:10:00" sendTimeout="00:10:00" receiveTimeout="00:10:00"/>

Parent topic: Troubleshooting