A Troubleshooting

Troubleshooting PMDA (R3) Paper Forms

Sl No Issue Cause Resolution
1 Missing or invalid junk characters instead of Japanese characters Japanese fonts are not installed in the BI Publisher Server Follow Argus Safety Install Guide section 13.2.1 Installing and Configuring East Asian Fonts
2 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 Argus Safety Install Guide section 13.3.3.2 Managing Folder Privileges
3 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.
    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.
    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
    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
4 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
    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
5 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"/>

Troubleshooting Flexible Aggregate Reports

Sl No Issue Cause Resolution
1 BIP Icons are not displayed against corresponding BIP specific fields/tabs in the Argus UI - Periodic Reporting Configuration BI Publisher Periodic reports are not enabled in the Argus Console In the Argus Console, navigate to System Configuration > Enabled Modules. Make sure that BIP Aggregate Reporting is checked
The page level cache is not refreshed Restart the IIS server
2 BI Publisher Periodic report does not Execute from Argus UI and the status of the reports remains in "Pending" status in the Report Generation Screen 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 BIP Periodic reports.
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.
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
The Oracle Data Access version present in the AGProc.config file is incorrect Refer to the Install guide and make sure the correct entry is provided.
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
3 The BIP Report fails with error: Report data size exceeds the maximum limit (<n> bytes). Stopped processing The report exceeds the maximum data size specified for report generation Log in to Oracle BI Publisher - http://hostname:port/xmlpserver/

  • Go to Administration > Runtime Configuration > Memory Guard

Update the parameters Maximum Report Data Size for online reports and Maximum report data size for offline (scheduled) reports as needed.

  • Go to Administration > Runtime Configuration > Data Model

Update the Maximum data size limit for data generation value as required.

Note that the value needs to be in bytes.
4 Database connection errors The BI Publisher report cannot utilize the JDBC provided Make sure the JDBC connection name is in lowercase (asbip)
5 BI Publisher Scheduled Report Output does not show up in the Argus application Invalid or missing Report Output Pusher job Make sure that the Report Output Pusher is running without any failure
Invalid database link AS_TO_BIPREP Verify whether the database link AS_TO_BIPREP is valid and pointing to the proper DEV_BIPLATFORM metadata repository database
Unscheduled Reports The reports are not scheduled in the BI Publisher, but being run (using the "open" option)
6 Error, ORA-01427: single-row sub-query returns more than one rowORA-06512: at "<bip_owner>.PKG_AGG_RPT" for p_updclinicaldrugrole procedure Study configuration is having duplicate attributes Check the study configuration and ensure that it does not have any duplicates
7 Error, ORA-20005: object statistics are locked (stattype = ALL) >> Error while copying case series - 1, USER NAME - <logged in user>. Required tables are locked. exec dbms_stats.unlock_table_stats('BIP_OWNER', 'GTT_RPT_AGG_UNIQ_CASES');
8 UserID: AG_batch_periodic_reports, Login to BIP Server failed

Exception DetailsMessage:

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\ArgusWeb\Bin\Argusvr2.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"/>
9 UserID: <AgUserID>, Report Scheduling to BIP Server failed

Exception DetailsMessage:

org.xml.sax.SAXException: SimpleDeserializer encountered a child element, which is NOT expected, in something it was trying to deserialize.

Stack Trace……

 Argusvr2.config entries are wrong Verify the <endpoint address> elements are correctly configured, and set it right.

(For more details, refer to the Configure AG Service and Configure Web Service (Expedited Reports only) sections in the Argus Safety Installation Guide.) http://<host>:<port>/xmlpserver/services/v2/SecurityService where the name attribute is set to SecurityService

http://<host>:<port>/xmlpserver/services/v2/ScheduleService where the name attribute is set to SchedulingService

http://<host>:<port>/xmlpserver/services/v2/ReportService where the name attribute is set to ReportService