A Troubleshooting

This appendix lists the probable issues you may encounter while installing, configuring, customizing, and adding a report to the BI Publisher.

A.1 BIP Icon not Displayed Against Corresponding BIP Specific Fields in the Periodic Reporting Configuration

Alternately, BIP Aggregate Reporting does not show up under Reporting in Common Profile switches.

Cause

BI Publisher Periodic reports are not enabled.

Solution

On the Argus Console, navigate to System Configuration > Enabled Modules. Make sure that BIP Aggregate Reporting is checked.

Figure A-1 BIP Aggregate Reporting Enabled

Description of ''Figure A-1 BIP Aggregate Reporting Enabled''
Cause

The page level cache is not refreshed.

Solution

Restart the IIS server.

A.2 BI Publisher Periodic report does not Execute from Argus UI

The BI Publisher Periodic reports do not run when invoked from the Argus UI. The status of the report remains Pending on the Background Reports screen.

Cause

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

Solution

Make sure there is a user ID present in the BIP Aggregate Reporting common profile switches. Verify that the user ID and password present in this switch can login to the BI Publisher. Also, make sure that the user ID has complete access to all reports.
Cause

In Linux/Unix the report path is case sensitive. The Report path in the REPORT_TEMPLATE is empty or has an incorrect path.

Solution

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.

Figure A-2 Verify Report Template Path

Description of ''Figure A-2 Verify Report Template Path''
Cause

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

Solution

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.
Cause

The Oracle DataAccess version present in the AGProc.config file is incorrect.

Solution

Refer to the Install guide and make sure the correct entry is provided.
Cause

Missing Argus UI user in the BI Publisher.

Solution

Make sure that the Argus UI user exists and is allowed to login and run the required reports.

A.3 Database Connection Errors

Cause

The BI Publisher report cannot utilize the JDBC provided.

Solution

Make sure the JDBC connection name is in lowercase. (asbip)

Note:

Sometimes, customer may have configured each service associated to one exe files. In such scenarios, the AG _Proc config related to Peridic Reporting should be modified.

A.4 BI Publisher Scheduled Report Output does not Show up

Make sure:

The report is scheduled and not open if run from the BI Publisher Console.
The database job used for copying the report output is running correctly.
The database link AS_TO_BIPREP is valid

A.5 ORA-01427: single-row sub-query returns more than one rowORA-06512: at "<bip_owner>.PKG_AGG_RPT" for p_updclinicaldrugrole procedure

Cause

The issue has been caused due to the study configuration having duplicated attributes.

Make sure:

To check the study configuration and ensure that it does not have any duplicates.

A.6 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 we 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 we 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 agservice 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 BI Publisher console

A.7 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
1		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');