Show TOC

TroubleshootingLocate this document in the navigation structure

This section provides information about common issues and errors and possible solutions related to the collaboration components.

Most Common Errors

For the Social Media Integration Share and Discuss features, all errors are displayed as a standard error message to the user. A more detailed explanation of the error appears in the browser’s console. The tables below reference the error messages in the console.

Table 1: Errors Related to Share Feature / REST Tunnel
Error Possible Reason Solution
HTTP code 403 (Forbidden): Access denied The user does not have authorization to share in the SAP Jam group.
Example The group is a read-only group, which means that only the group administrator can share content.
 Contact the administrator of the SAP Jam group to request the necessary authorization for the user. This will allow the user to share content to that particular SAP Jam group.
HTTP code 403 (Forbidden): The termination occurred in system <<system name>> with error code 403 and for the reason Forbidden. The selected virtual host was 0. What can I do? Select a valid URL. If it is a valid URL, check whether service <<service name>> is active in transaction SICF. The OData service is not activated. Activate the OData service (see Activating the OData Services).
HTTP code 400 (Bad Request): No entry found for platform type Jam and <<endpoint name>>. The Social Media Integration whitelist for the REST tunnel is missing the corresponding whitelist entries. Configure the whitelist (see Configuring REST Tunnel).
HTTP code 409 (Conflict): Item has already been shared in this group. The business object has already been shared in the SAP Jam group. No action is required. This error does not affect the user and will not prevent the user from sharing the content in SAP Jam; it only informs the user that the business object has already been featured in the SAP Jam group.
HTTP code 401 (Unauthorized): SAML authentication failed. Detail: Could not find unique user with email <<email address>> in company <<company name>>. The user's email address is missing or invalid in the back-end system. Verify the user’s email address in the user master record (transaction SU01) in the back-end system.
HTTP code 500 (Internal Server Error): No System Alias found for Service <<service name>> and user <<username>>. The Social Media Integration OData service (SM_INTEGRATION_V2_SRV) is not activated. Activate the OData service (see Activating the OData Services).
Bad Request (400 error) This error can occur in the case of an incorrect request.

If you are sure that your request is correct, the instance profile parameter may not be set to true. This can cause a truncation in the request URL.

Example

In the example below, the group ID is not present in the value of the path_info header returned by the server object, which can cause certain endpoints to fail in the REST tunnel.

Request that was sent (with group ID): https://ldcigm6.wdf.sap.corp:44333/sap/bc/ui2/smi/rest_tunnel/Jam/api/v1/OData/Groups('O9EeD2KWFpNea1lMXUZWvx')/$links/FeaturedExternalObjects

Truncated URL sent back because of incorrect parameter configuration: /Jam/api/v1/OData/Groups/$links/FeaturedExternalObjects
  1. Add the instance profile parameter ict/odata_compatible_urls=true.
  2. Restart the server on which you set the instance profile parameter.
Table 2: Errors Related to Discuss Component
Error/Issue Possible Reason Solution
HTTP code 401 (Unauthorized): SAML authentication failed. Detail: Could not find unique user with email <<email address>> in company <<company name>>. The user's email address is missing or invalid in the back-end system. Verify and add the user’s email address in the user master record (transaction SU01) in the back-end system.
HTTP code 403 (Forbidden): The single-use token from SAP Jam was not returned successfully.
  • The user's email address is missing or invalid in the back-end system.
  • The single-use token from SAP Jam has expired.
 Refresh the page and try the same operation. If this does not resolve the problem, verify add the user’s email address in the user master record (transaction SU01) in the back-end system.

HTTP code 403 (Forbidden)

Issue: You are using Google Chrome as your browser and cannot see others' feed entries in the Discuss Dialog component.

The cookie setting in Google Chrome is set to Block all cookies.

  1. In Google Chrome, go to Manage cookie blocking.

  2. Add the collaboration domain sapjam.com to the cookie and site data exceptions.
Table 3: Errors Related to SAP Fiori Launchpad
Error Possible Reason Solution
HTTP code 404 (Not Found): Could not load user image from <<service path>>
Note This error message appears in the console for the SAP Fiori launchpad.
 The user does not have a profile photo in SAP Jam. This error does not prevent the user from continuing the operation; however, to avoid this error, the user needs to add a profile photo in SAP Jam.
Other Issues
Issue Possible Solution
The user has uploaded a file but cannot see the file in SAP Jam. On the SAP Gateway server, run transaction SBGRFCMON to identify upload issues.

This transaction allows system administrators to monitor the queues used for upload operations. Note that there is one queue for each file upload.

The user receives an error message when attempting to use the Share or Discuss feature.
  1. Check the configuration of the front-end and back-end systems (see Front-End Configuration and Back-End Configuration).
  2. Run report RCLB2_CUST_CHECK or RCLB2_DEMO_GENERIC to check the connectivity.
  3. If applicable to your system setup, ensure that the configuration (Customizing) is set up properly.

    In the back-end system, check the following:

    1. External URL mapping in the HTTPURLLOC table (see Enabling URL Rewriting)
    2. Business object mapping in table CLB2C_APPL_CONT (see Defining the Application Context on the Back-End Server), and view cluster CLB2VC_GW_SRV_C and the mapping Business Add-Ins (see Registering OData Services)
    In SAP Jam, check the following:
    1. External application (see Setting Up the External Application in SAP Jam)
    2. Record type (see Adding Record Types to an External Application (Manual))
The Share or Discuss button is disabled. Check the configuration as described above. If the configuration is correct, there may be an issue with the SAP Fiori launchpad.
In the SAP Fiori app, the user cannot see other users' feed for a specific business object in the Discuss Dialog component.
  1. Ensure that the external application and external object are set up correctly in SAP Jam (see Configuring SAP Jam).
  2. Ensure that the URL mapping is correctly configured on the SAP Gateway server in table HTTPURLLOC (see Enabling URL Rewriting).
  3. If the configuration above is correct, ensure that the user is authorized to access information in the back-end system.