Bookshelf Home | Contents | Index | PDF     

Siebel Reports Guide > Troubleshooting Siebel Reports >

Troubleshooting Error Messages for Siebel Reports

Table 10 contains the error messages that you might encounter when using Siebel Reports and the suggested solutions for resolving the errors.

Table 10. Resolving Siebel Reports Error Messages
Error Message or Symptom
Description and Solution
Connection
Mode

SBL-OMS-00203: Error <?> invoking method "<?>" for Business Service "<?>"

This error occurs when you fail to upload the template to the Oracle BI Publisher Server.

To resolve, see Troubleshooting Errors While Running Siebel Reports (SBL-OMS-00203).

Connected
and
disconnected

"Unable to find definition for component XMLPReportServer(SBL-SRQ-00103)" error when I clicked on the Submit button to generate the report."

This error occurs after clicking Submit to generate a report.

To resolve, see Troubleshooting Error After Clicking Submit to Generate a Report (SBL-SRQ-00103).

Connected
and
disconnected

The specialized method 'GetFileToDir' is not supported on Business Component 'Report Template BC' used by Business Object 'Report Administration'.
(SBL-DAT-00322)

This error occurs when the path settings in the configuration files are incorrect.

To resolve, see Troubleshooting Errors That Occur Due to Incorrect Configuration File Settings (SBL-DAT-00322).

Connected
and
disconnected

SBL-RPT-50504: Error occurred while saving the record. No data file provided for XLIFF generation.

This error occurs when users forget to provide a sample XML data file for generating an XLIFF file.

To resolve, see Troubleshooting XLIFF File Errors.

Disconnected
only

"Class name incorrect" error when generating BI Publisher reports

This error occurs when Oracle BI Publisher or the JAR files are not loaded.

To resolve, set the classpath, see Troubleshooting the CLASSPATH Settings Using Siebel Server Manager.

Disconnected
only

Reports having custom java class involved are not generating.

Verify that SiebelCustomXMLP.jar, SiebelXMLP.jar are under SIEBSRVR_ROOT\classes.

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.

Not applicable

SBL-EAI-04116 BIP: Server connection is lost

 

This error might occur if the report generation has extended the HTTP Sleep Time, typically only for very large or complex reports.

To resolve, increase the HTTPSleepTime method argument for the XMLP Driver Service business service.

Connected only

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.

Connected
only

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::executeCreateReport 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.PublicReportServiceService' 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.

 

Connected
only

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.

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.

Connected
only

SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService : com/siebel/data/SiebelPropertySet -- JVM Exception:java.lang.NoClassDefFoundError: com/siebel/data/SiebelPropertySetObjMgrBusServiceLog

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.PublicReportServiceService' at port 'PublicReportService_v11' failed with the following explanation: "oracle.apps.xdo.webservice.exception.InvalidParametersException: PublicReportService::executeUploadReport 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

Troubleshooting Errors While Running Siebel Reports (SBL-OMS-00203)

Use the following procedure if errors occur while generating Siebel Reports (error message SBL-OMS-00203).

To troubleshoot errors while generating Siebel Reports

  1. Make sure the XMLP Report Server component is enabled.
  2. Increase the XMLP Report Server component log level to 5 to create a more detailed log file.
  3. Copy the xdodebug.log file to the jre\lib directory.

    For information about performing these tasks, see Enabling Logging for Siebel Reports in the Siebel Application and Enabling and Disabling Debugging for Siebel Reports in Disconnected Mode.

Additionally, you might encounter an instance where a layout template was registered with one database, but you generated it with a different database, and the generation fails. If this error happens, you must complete the following task.

To regenerate and rerun the report

  1. Regenerate the XML data.
  2. Reregister the layout template.
  3. Regenerate the report.

Troubleshooting Error After Clicking Submit to Generate a Report (SBL-SRQ-00103)

Use the following procedure if an error occurs after clicking Submit to generate a report (error message SBL-SRQ-00103).

To troubleshoot if an error occurs after clicking Submit to generate a report

  1. Enable and synchronize the XMLPReportServer component.

    For information about enabling this component, see Siebel System Administration Guide.

  2. Restart the Siebel Server.

    For information about restarting the Siebel Server, see Siebel System Administration Guide.

Troubleshooting Errors That Occur Due to Incorrect Configuration File Settings (SBL-DAT-00322)

Use one of the following procedures to correct errors that occur due to incorrect configuration file settings (error message SBL-DAT-00322).

To troubleshoot for errors when in connected mode

  1. Make sure Siebel File System path is correct by doing the following:
    1. Navigate to the Administration - Server Configuration screen, Servers, and then the Components view.
    2. Query for the Callcenter Object Manager (or other application specific Object Manager, like Siebel Sales or Siebel Service).
    3. Click the Parameters view tab, and then query for FileSystemManager, and then click Advanced.
    4. In Siebel File System field, provide the path as \\<machine name>\fs.
    5. Make sure that the fs directory exists in the D: drive and also that it is shared.
  2. Restart the Siebel Server.
  3. Verify that the File System component is running.
  4. Verify that CLASSPATH is set in the JVMSubSys profile parameter.
  5. Verify that all the required JAR files are included and available in the CLASSPATH.
  6. Verify that the CLASSPATH separator is in the correct format for Windows or UNIX.

    In UNIX, the CLASSPATH separator is a colon (:). In Windows, the CLASSPATH separator is a semicolon (;).

To troubleshoot for errors when in disconnected mode

  1. In the application .cfg file, search for FileSystem, and then add \\<machine name>\fs\att as the value, making sure the fs directory is shared.
  2. In the [XMLPReports] section of the .cfg file, make sure this section is defined as follows:

    [XMLPReports]
    XdoDir = /xmlp/templates/
    ReportOutputDir = /xmlp/reports/
    ReportDataDir = /xmlp/data/

  3. To check whether the file system path is set properly, try to register the template.

    If registering the template is successful, you can drill down on the generated XLIFF file. If either browsing the template fails or the drilldown fails, this means that the file system path is not set appropriately.

Troubleshooting XLIFF File Errors

Use the following procedure when users forget to provide a sample XML data file when generating XLIFF files.

To troubleshoot XLIFF errors

  1. Navigate to the Administration - BI Reports screen, then the Sample Data File Generation view.
  2. Select the integration object associated with the report, and then click Generate Sample XML.

Troubleshooting the CLASSPATH Settings Using Siebel Server Manager

Use the following procedure to change the CLASSPATH parameter using the Siebel Server Manager utility.

To change the CLASSPATH parameter using Siebel Server Manager

  1. Log in to the Server Manager command-line interface (srvrmgr program).

    For information on how to start and use the srvrmgr program, see Siebel System Administration Guide.

    Execute the following command to change the CLASSPATH:

    change param CLASSPATH=SIEBSRVR_ROOT\classes\Siebel.jar; SIEBSRVR_ROOT\classes\SiebelXMLP.jar;SIEBSRVR_ROOT\classes\wlfullclient.jar;

Troubleshooting Oracle BI Publisher Server Login Errors

Use the following procedure when Oracle BI Publisher login errors occur.

To troubleshoot Oracle BI Publisher Server login errors

  1. Navigate to the Administration - Server Configuration screen, then the Servers view.
  2. Click the Component view tab, and query for XMLP Report Server.
  3. Click the Parameters view tab, query for BIP Server Login, and then enter (or verify) the correct login information for the Oracle BI Publisher Server.
  4. While still in the Parameters view tab, query for the BIP Server Password, and then enter (or verify) the correct password for the Oracle BI Publisher Server.

Troubleshooting Alignment Problems in HTML Output

Use the following procedure to troubleshoot alignment problems in HTML output.

To fix alignment problems in HTML output

  1. Add a row to the Table Header.
  2. Copy the Form fields from the data row in the added row.
  3. Delete the previous table that contained the data row.

    The single table now contains both header and data row.

Troubleshooting Japanese Font Errors

Use the following procedure to properly display JPN (Japanese) fonts in Siebel Reports.

To create font mapping to display Japanese fonts properly

  1. Search for msgothic.ttc, and then copy the file to the computer on which the Oracle BI Publisher Server is installed:

    \Java\jdk\jre\lib\fonts

  2. Restart OC4J (Oracle Application Server Containers for Java Platform, Enterprise Edition).
  3. Launch the Oracle BI Publisher Server URL.
  4. Log in to Oracle BI Publisher Server.
  5. Navigate to Admin, Runtime configuration, and then Font Mappings.
  6. Create the following two font mappings:
    • Arial, Normal, msgothic.ttc
    • Arial, Bold, msgothic.ttc

    
Siebel Reports Guide Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.