Siebel Collaboration Guide > Getting Started with Siebel Collaboration >

Troubleshooting Siebel Collaboration Setup


This topic provides guidelines for resolving Siebel Collaboration setup problems.

You can find information to help you diagnose setup problems with Siebel Collaboration in the following files:

  • There are two Siebel Server log files you must verify. The log file for the Siebel application, for example, the log file for the Call Center application contains SCCObjMgr_enu in the file name. Secondly, the log file for the Siebel inbound Web Service. This is the log file associated with the Custom Application Service and contains CustomAppObjMgr in the file name.

    For debugging Siebel Collaboration, it is recommended that you set the log level to 5.

NOTE:  For general information about Siebel log files, see the Siebel System Monitoring and Diagnostics Guide.

  • The Event Viewer (Application log) on the SharePoint server. The Siebel Web Part logs entries with the Siebel Web Part. Similarly, the Siebel-SharePoint Integration Web Service logs entries the Event Source of the Siebel SharePoint Integration Web Service.

    Logging to the Event Viewer is enabled through the registry files as described in Configuring the Collaboration Service.

If an error occurs in the Siebel application, check the log files on the Siebel Server. If an error occurs in the team space, check the Event Viewer log. If the log indicates a problem on the Siebel Server, then check the Siebel Server log also.

Troubleshooting Reference for Siebel Collaboration Setup

This topic provides guidelines for resolving Siebel Collaboration Setup problems. To resolve the problem, look for it in the list of Symptoms/Error messages in Table 5.

Table 5 describes possible symptoms and error messages when setting up Siebel Collaboration and their corresponding causes and solutions.

Table 5. Troubleshooting the Siebel Collaboration Setup
Symptom/Error Message
Diagnostic Steps/Causes
Solution

In the Siebel application, the Collaborate and Create Team Space buttons do not appear.

  • Siebel Collaboration is not enabled in the Siebel application CFG file.
  • License key for Siebel Collaboration has not been entered.
  • The Internet Explorer browser cache needs to be cleared.
  • User authentication is not set correctly.

In the Siebel application, the Team Space column does not appear.

In the Siebel application, Collaborate and Team Space buttons are disabled.

In the Siebel application, the Team Space column is empty (does not show any icons).

  • The Siebel Server is not configured correctly with the Siebel-SharePoint Integration Web Service.
  • The Siebel application cannot communicate with the Siebel-SharePoint Integration Web Service on the SharePoint host machine

In the Siebel application, when a user clicks Collaborate, the application displays the message, "Collaboration user ID cannot be located."

Siebel Collaboration has been configured for SSO user authentication and the user has not been added to the Siebel Server's SSO Team Space Collaboration record.

Add the user to the Team Space Collaboration record in the SSO Systems Administration list. (See Setting Up the Single Sign-On Table for Siebel Collaboration.)

In the Siebel application, when a user clicks Collaborate, a Windows login dialog box appears.

  • The user does not have access to the SharePoint host machine.
  • The SharePoint host machine has not be added to the browser as a local or trusted site with automatic logon.
  • Confirm that, external to the Siebel application, the user has login access to the SharePoint host machine.
  • Add the SharePoint host machine as a local or trusted site:
    1. In Internet Explorer, navigate to Tools > Internet Options > Security.
    2. Add the SharePoint host machine in either the Local intranet or Trusted sites zone.
    3. For the security level of the zone, set the User Authentication > Logon setting to Automatic logon with current username and password.

In the Siebel application, when a user clicks Collaborate, the team site page displays an error page with the message, 'The "SiebelWebPart" Web Part appears to be causing a problem.'

The Siebel Web Part is incorrectly configured on the SharePoint server.

Confirm that the policy file for the SharePoint portal site is correctly configured.

The Siebel Web Part displays the message, "Web Part Error: A Web Part or Web Form Control on this Web Part Page cannot be displayed or imported because it is not registered on this site as safe."

The Siebel Web Part is incorrectly configured on the SharePoint server.

Confirm that Siebel Web Part has been registered as a safe control in the web.config file for the SharePoint portal site. This is located in the SharePoint Portal Server home directory.

The Siebel Web Part displays the message, "An Unexpected Error occurred."

The Siebel Web Part cannot communicate with the Siebel-SharePoint Integration Web Service.

  • Confirm that the Siebel-SharePoint Integration Web Service is running.
  • Confirm that the URI for the Siebel-SharePoint Integration Web Service is correctly specified in the registry. (See Configuring the Collaboration Service.)

The Siebel Web Part displays the message, "Unable to retrieve the Siebel data for this site."

  • The Siebel-SharePoint Integration Web Service cannot communicate with the Siebel inbound Web Service.
  • The Siebel-SharePoint Integration Web Service is not configured correctly.
  • Confirm that the correct URI for the Siebel inbound Web Service is specified in the config.xml file. (See Configuring the Collaboration Service.)
  • Confirm that the Siebel inbound Web Service is running.
  • Confirm that the correct values are specified in the registry settings through the WebParts.reg and IntegrationWebService.reg files; in particular, make sure that the names for the XSL files are correct. (See Configuring the Collaboration Service.)

The Siebel Web Part displays any other error message.

  • The Siebel Web Part is not configured correctly.
  • The Siebel-SharePoint Integration Web Service is not configured correctly.
  • The Siebel-SharePoint Integration Web Service cannot communicate with the Siebel inbound Web Service.

Siebel Collaboration Guide Copyright © 2006, Oracle. All rights reserved.