Bookshelf Home | Contents | Index | PDF     

Siebel Reports Guide > Troubleshooting Siebel Reports >

Troubleshooting Error Messages for Siebel Reports

This topic describes guidelines for fixing error messages that occur with Siebel Reports. To fix one of these problems, look for it in the Symptom or Error Message column in Table 10.

Table 10. Problems with Siebel Reports
Symptom or Error Message
Solution

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

This error might occur if you fail to upload the template to the Oracle BI Publisher Server. It might occur in a connected or disconnected client.

To fix this problem, see Fixing Errors That Occur When Running Siebel Reports (SBL-OMS-00203).

Siebel CRM displays the following message if you click Submit in the Run Report pane"

"Unable to find definition for component XMLPReportServer(SBL-SRQ-00103)"

This error might occur after you click Submit to run a report. It might occur in a connected or disconnected client.

To fix this problem, see Fixing Errors That Occur After Clicking Submit in the Run Report Pane (SBL-SRQ-00103).

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

This error might occur if the path settings in the configuration files are not correct. It might occur in a connected or disconnected client.

To fix this problem, see Fixing Errors That Occur Due to Incorrect Configuration File Settings (SBL-DAT-00322).

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

This error might occur if you do not provide a sample XML data file for creating an XLIFF file. It occurs only in a disconnected client.

To fix this problem, see Fixing XLIFF File Errors.

Siebel CRM displays the following message if you run a report:

Class name incorrect

This error might occur if Oracle BI Publisher or the JAR files are not loaded. It occurs only in a disconnected client.

To fix this problem, you set the classpath. For more information, see Fixing the CLASSPATH Settings.

Siebel CRM does not create reports that include a custom java class.

Verify that the SiebelCustomXMLP.jar and SiebelXMLP.jar files reside in the following folder:

SIEBSRVR_ROOT\classes

Make sure that the Oracle BI Publisher Server path is the following:

$OC4J_PATH\j2ee\home\applications\xmlpserver\xmlpserver\WEB-INF\lib

For Siebel Industry Applications, make sure the following files reside in each of these paths:

  • SiebelCustomXMLP_SIA.jar
  • SiebelXMLP.jar

This problem occurs only in a connected client.

The Oracle BI Publisher log file or console displays the following message:

][java.lang.String][EXCEPTION] oracle.apps.xdo.XDOException: XSLT10gR1: Failed Secure Java Extensions check.

This error occurs if you run a report and:

  • You do not copy the JAR files to the Oracle BI Publisher Server.
  • The Disable External Reference parameter attribute is not set to FALSE.

To fix this problem, see the topic on starting and stopping OC4J and Oracle BI Publisher in 1501378.1 (Article ID) on My Oracle Support.

SBL-EAI-04116 BIP: Server connection is lost

This error might occur with a very large or complex report. It occurs only in a connected client.

You can increase the HTTPSleepTime method argument to fix this problem. For more information, see Modifying the Sleep Time.

Siebel CRM displays one of the following messages in the XMLP log file:

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

This error message displays if you do not provide the correct user ID and password for the Oracle BI Publisher Server in the XMLP Report server component parameters. This problem occurs only in a connected client.

To fix this problem, see Fixing Oracle BI Publisher Server Login Errors.

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

Make sure the temp\xmlp folder exists in the SIEBSRVR_ROOT folder. If it does not, then add it. For more information, see Directory Structure That Siebel Reports Uses.

Also, make sure the Siebel File System is set correctly. For information about setting the Siebel File System, see Siebel System Administration Guide.

This problem might occur in a connected or disconnected client.

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

Make sure 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 (%)

This problem occurs only in a connected client.

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 might occur if you run a report that includes missing information on the Oracle BI Publisher Server. A missing .xdo file is an example of missing information.

To fix this problem, upload the report template from Oracle BI Publisher. For more information about uploading report templates, see Registering Report Templates.

This problem occurs only in a connected client.
  • An column alignment problem occurs in HTML report output.

This problem might occur if the table header row and the data row reside in two different tables, but Siebel CRM displays them as a single table because no space exists between these tables. HTML or EXCEL might create this output.

This problem might occur in a connected or disconnected client.

To fix this problem, see Fixing Alignment Problems in HTML.

One of the following problems occur:

  • An alignment problem occurs in report that runs in Japanese or PSJ.
  • The PPT output type for Japanese (JPN) is distorted in a report.

To fix this problem, you can create the font mappings for the Oracle BI Publisher Server to make sure that the HTML output displays correctly. This problem occurs only in a connected client.

To fix this problem, see Fixing Japanese Font Errors.

Siebel CRM displays one of the following message when you upload files to Oracle BI Publisher:

  • 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 : <?>

To fix this problem, verify the following:

  • JAVA_HOME variable is set correctly.
  • The following JAR files are copied from the siebelroot\classes\original folder to the ORACLE_HOME\j2ee\home\applications\xmlpserver\xmlpserve\WEB-INF\lib folder:
    • Siebel.JAR
    • SiebelXMLP.JAR
    • XSLFunctions.JAR
    • SiebelCustomXMLP.JAR
    • SiebelCustomXMLP_SIA.JAR
  • The CLASSPATH variable is set correctly in the JVMSubSys profile.
  • The JVM SubSystem Name parameter for XMLPReportServer is set to XMLPJvmSubsys. If this value is JAVA, then set it to XMLPJvmSubsys.

Siebel CRM displays the following message when you upload files to Oracle BI Publisher:

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 indicates that the Oracle BI Publisher Server already includes a copy of the file that you are uploading. The uploadReport method does not support uploading a new version of an existing file.

To fix this problem, you must 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 template files in the following directory:

ORACLE_HOME\xmlp\XMLP\Reports\
SiebelCRMReports

Fixing Errors That Occur When Running Siebel Reports (SBL-OMS-00203)

This topic describes how to fix an error that occurs while running Siebel Reports.

To fix errors that occur when running 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 folder.

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

Regenerating XML and Running the Report

If you create a report template with a database, but then register it with a different database, then the report might fail. This topic describes how to fix this problem.

To regenerate XML and run the report

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

    For more information, see Registering Report Templates.

  3. Rerun the report.

Fixing Errors That Occur After Clicking Submit in the Run Report Pane (SBL-SRQ-00103)

This topic describes how to fix an error that occurs after you click Submit in the Run Report pane.

To fix errors that occur after clicking Submit in the Run Report pane

  1. Enable and synchronize the XMLP Report server 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.

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

This topic describes how to fix an error that occurs due to incorrect configuration file settings.

To fix errors that occur due to incorrect configuration file settings

  1. Make sure Siebel File System path is correct:
    1. Navigate to the Administration - Server Configuration screen, Servers, and then the Components view.
    2. Query for the object manager that your Siebel application uses.

      For example, Call Center, Siebel Sales, or Siebel Service.

    3. Click the Parameters tab, query for FileSystemManager, and then click Advanced.
    4. In Siebel File System field, enter the following path:

    \\computer name\fs

    1. Make sure that the fs folder exists in the D drive and 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 Windows, the CLASSPATH separator is a semicolon (;). In UNIX, the CLASSPATH separator is a colon (:).

Fixing Errors in Disconnected Clients

This topic describes how to fix an error that occurs in a disconnected client.

To fix errors in disconnected clients

  1. In the application .cfg file, set the following value for the FileSystem parameter:

    FileSystem \\computer name\fs\att

  2. Make sure the fs folder in the path that you added in Step 1 is shared.
  3. In the XMLPReports section of the .cfg file, make sure the following section is defined:

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

  4. To determine if the path to the file system is set properly, try to register the report template.

    If you can successfully register the report template, then you can drill down on the XLIFF file. If you cannot browse the report template, or if you cannot drill down on the XLIFF file, then you must make sure the path to the file system is set correctly.

Fixing XLIFF File Errors

This topic describes how to fix an error that occurs if you do not provide a sample XML data file when you create the XLIFF files.

To fix XLIFF errors

  1. Log in to the Siebel client with administrator privileges.
  2. Navigate to the Administration - BI Reports screen, and then the Sample Data File Generation view.

    For more information about this view, see Creating XML Files from Integration Objects.

  3. Choose the integration object associated with the report, and then click Generate Sample XML.

Fixing the CLASSPATH Settings

This topic describes how to fix the CLASSPATH parameter.

To fix the CLASSPATH parameter

  1. Log in to the Server Manager command-line interface.

    For information about how to use the srvrmgr program, see Siebel System Administration Guide.

    Run 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;

Fixing Oracle BI Publisher Server Login Errors

This topic describes how to fix Oracle BI Publisher Server login errors.

To fix Oracle BI Publisher Server login errors

  1. Log in to the Siebel client with administrator privileges.
  2. Navigate to the Administration - Server Configuration screen, and then the Servers view.
  3. Click the Component tab, and then query for XMLP Report Server.
  4. Click the Parameters tab, query for BIP Server Login, and then enter the correct login information for the Oracle BI Publisher Server.
  5. Query for the BIP Server Password, and then enter the correct password for the Oracle BI Publisher Server.

Fixing Alignment Problems in HTML

This topic describes how to fix alignment problems that occur in the HTML output of a report.

To fixing alignment problems in HTML

  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 header and data row.

Fixing Japanese Font Errors

Fixing Japanese Font Errors that occur with Oracle's Siebel Reports.

To fix Japanese font errors

  1. Locate the msgothic.ttc file.
  2. Copy the file you located in Step 1 to the following folder on the computer where you installed the Oracle BI Publisher Server:

    \Java\jdk\jre\lib\fonts

  3. Restart OC4J.

    For more information about OC4J, see How Siebel CRM Creates Reports.

  4. Log in to Oracle's BI Publisher Server.
  5. Navigate to Admin, Runtime configuration, and then Font Mappings.
  6. Create the following font mappings:
    • Arial, Normal, msgothic.ttc
    • Arial, Bold, msgowthic.ttc
    
Siebel Reports Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.