• No results found

SIEBSRVR_ROOT \classes.

In document Reports (Page 163-167)

Make sure that the Oracle BI Publisher Server path is:

$OC4J_PATH\j2ee\home\applications\ xmlpserver\xmlpserver\WEB-INF\lib For Siebel Industry Applications, make sure the following files are in both paths:

■ SiebelCustomXMLP_SIA.jar ■ SiebelXMLP.jar Connected only ][java.lang.String][EXCEPTION] oracle.apps.xdo.XDOException: XSLT10gR1: Failed Secure Java Extensions check.

This error appears in the Oracle BI Publisher log file or console when generating a report when the JAR files have not been copied to the Oracle BI Publisher Server, or the required Disable External Reference parameter attribute has not been set to FALSE.

To resolve, see “Starting and Stopping OC4J and Oracle BI Publisher” on page 49.

Not applicable

Verify the BIP Server Userid and Password. (SBL-RPT-50529) or Failed to log into BI Publisher: invalid username or password.

This error message appears in the XMLP log file, because the user has not provided the correct User ID and password for the Oracle BI Publisher Server in the XMLP Report Server component parameters.

To resolve, see “Troubleshooting Oracle BI Publisher Server Login Errors” on page 169.

Connected only Table 10. Resolving Siebel Reports Error Messages

Error Message or Symptom Description and Solution

Connection Mode

Generic Error in Compression Routine (SBL-UIF-00227)

Verify whether the temp\xmlp directory exists in the Siebel Server root directory (SIEBSRVR_ROOT). If it does not, create one. Also make sure the Siebel File System is set appropriately. For information about setting the Siebel File System, see Siebel System Administration Guide.

Connected and

disconnected

PublicReportService::executeCreate Report Failure: due to Report Name contains special characters for report

Make sure that the report name does not contain the following special characters: ■ Forward slash (/) ■ Backslash (\) ■ Double quote (") ■ Single quote (') ■ Tilde (~) ■ Ampersand (&) ■ Asterisk (*) ■ Plus sign (+)

■ Left angle bracket (<) ■ Right angle bracket (>) ■ Percent sign (%)

Connected only

SBL-EAI-04308: Operation

'runReport' of Web Service 'http:// xmlns.oracle.com/oxp/service/ PublicReportService.PublicReportSer viceService' at port

'PublicReportService' failed with the following explanation:

"oracle.apps.xdo.webservice.

exception.OperationFailedException: PublicReportService::

generateReport failed: due to oracle.apps.xdo.servlet.

CreateException: Report definition not found:/SiebelCRMReports/ <Report Name>/<Report Name>.xdo".

This error occurs when you execute a report that has missing bits on the Oracle BI Publisher Server (such as the .xdo file). To resolve, upload the layout template from Oracle BI Publisher using the Report Template Registration view. For more information about uploading layout templates, see “Registering Report Layout Templates” on page 114.

Connected only Table 10. Resolving Siebel Reports Error Messages

Error Message or Symptom Description and Solution

Connection Mode

Alignment issues with columns with HTML file output type

The problem occurs when the table header row and the data row are composed of two different tables with no space between them. HTML, and sometimes EXCEL, might generate output with alignment issues. NOTE: There are two tables, one for Table Header and one for Data Row. But they look like one single table, because there is no space between the two tables.

To resolve, see “Troubleshooting Alignment Problems in HTML Output” on page 169.

Connected and

disconnected

Alignment issue with JPN/PSJ environment in the reports.

The PPT output type for Japanese (JPN) is distorted in generated reports. Create the font mappings for the Oracle BI Publisher Server to make sure that the HTML output appears correctly.

To resolve, see “Troubleshooting Japanese Font Errors” on page 169.

Connected only Table 10. Resolving Siebel Reports Error Messages

Error Message or Symptom Description and Solution

Connection Mode

SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService : com/siebel/ data/SiebelPropertySet -- JVM Exception:java.lang.NoClassDefFoun dError: com/siebel/data/ SiebelPropertySetObjMgrBusService Log

Object manager error: ([0] Class name incorrect or does not extend SiebelBusinessService : <?>

This error occurs while uploading files to Oracle BI Publisher.

To resolve, verify the following:

■ JAVA_HOME variable is set correctly. ■ The following JAR files (Siebel.JAR,

SiebelXMLP.JAR, XSLFunctions.JAR, SiebelCustomXMLP.JAR, and

SiebelCustomXMLP_SIA.JAR) are copied from the following directory:

siebelroot\classes\original

Then make sure they are copied to the following directory:

ORACLE_HOME\j2ee\home\

applications\xmlpserver\xmlpserve\ WEB-INF\lib

■ The CLASSPATH variable is set correctly in the JVMSubSys profile.

■ The JVM SubSystem Name parameter for XMLPReportServer is set to XMLPJvmSubsys.

NOTE: If this value is JAVA, override it. Not applicable

SBL-EAI-04308: Operation

'uploadReport' of Web Service 'http:/ /xmlns.oracle.com/oxp/service/v11/ PublicReportService.PublicReportSer viceService' at port

'PublicReportService_v11' failed with the following explanation:

"oracle.apps.xdo.webservice.excepti on.InvalidParametersException: PublicReportService::executeUpload Report Failure: Due to Report with Path [/SiebelCRMReports/Application Activity/Application Activity.xdo] already exist!".

This error occurs while uploading files to Oracle BI Publisher.

This error indicates that the Oracle BI Publisher Server already has a copy of the file that is currently being uploaded. The uploadReport method does not support uploading a new version of an existing file. To resolve, the administrator must either rename or delete the folder for the existing instance of the report on the Oracle BI Publisher Server. The Oracle BI Publisher Server stores the report layout templates in:

ORACLE_HOME\xmlp\XMLP\Reports\ SiebelCRMReports

Not applicable Table 10. Resolving Siebel Reports Error Messages

Error Message or Symptom Description and Solution

Connection Mode

Troubleshooting Errors While Running Siebel Reports (SBL-OMS-

In document Reports (Page 163-167)