SAP Knowledge Base Article - Public

2628688 - OData service connection in SAP Analytics Cloud ***Master KBA***

Symptom

  • This article summarizes common error messages when connecting to an OData service in SAP Analytics Cloud (SAC).
  • You have followed the steps to set up an OData service URL and an Import Data connection as per the online help Import Data Connection to OData Services or guided playlist SAP Analytics Cloud > Learning > Guided Playlists > OData Services.
  • Some error messages occur when connecting to an OData service in SAP Analytics Cloud, for example:
    • Unable to connect to OData Services with error: 503 There is no SAP Cloud Platform Cloud Connector (SAPCP CC / SCC) connected to your subaccount. Requested opening of a tunnel for subaccount <name of your subaccount> and default SCC location ID, that is, empty string or simply not configured. Check the configuration on SCC and cloud side.. Check the connection details and user credentials then try again.
    • Unable to connect to OData Services with error: Error sending request to proxy. Status: 403 Reason: Forbidden. Check the connection details and user credentials then try again.
    • Unable to connect to Odata Services with error: 502 The requested URL could not be retrieved. Check the connection details and user credentials then try again.
    • The user doesn't have permission to access the requested resource.
    • The request is unauthorized, please check data service url and credentials.
    • Unable to connect to OData Services with error: response status 404. Check the datasource URL and on-premise option then try again.
    • Authentication is required. Please select one authentication type.
    • Unable to connect to OData Services with error: 503 Application Server Error. Check the connection details and user credentials then try again.
  • Other errors in the Chrome developer tools may also occur, for example:
    • {"result":"{\"error\":{\"code\":\"ERROR_ACCESS_DENIED\",\"rawError\":\"Forbidden Access denied to system <SERVER>:443. In case this was a valid request, ensure to expose the system correctly in your cloud connector.\",\"params\":[]}}"}

Environment

  • SAP Analytics Cloud

Reproducing the Issue

Follow the steps in the online help Import Data Connection to OData Services and/or guided playlist SAP Analytics Cloud > Learning > Guided Playlists > OData Services.

  1. For an on-premise OData service host http://<HOST>:<PORT>/<Package>/<Service>, create the following mapping entry:

    1. In the SAPCP Cloud Connector navigation panel, select Cloud to on-premise.
    2. Under the Access Control tab, select + (Add)
    3. Fill in the Edit System Mapping dialog:
      • Back end Type: Other SAP System
      • Protocol: HTTP (or HTTPS depending on whether you implemented SSL)
      • Virtual Host: <HOST>
      • Virtual Port: <PORT>
      • Internal Host: <HOST>
      • Internal Port: <PORT>
      • SAProuter: <leave empty>
      • Principal Type: None
      • SNC Partner Name: <leave empty>
      • Description: OData service host
      • Check Internal Host: [Checked]
    4. Click Save
      NOTE: When you specify the Data Service URL = http://<HOST>:<PORT>/ in SAP Analytics Cloud, it will use the SAPCP Cloud Connector to look up the  <HOST>:<PORT> specified in <Virtual Host>:<Virtual Port> and route the request to the <Internal Host>:<Internal Port>.
    5. Select the system you added to the Mapping Virtual To Internal System list
    6. In the Resources Accessible area, select + (Add)
    7. Fill in the Add Resource dialog
      • URL Path: /<Package>
      • Enabled: [Checked]
      • Access Policy: Path and all sub-paths
      • Description: OData service for <purpose>
    8. Click Save
      NOTE: When you specify Data Service URL = http://<HOST>:<PORT>/ in SAP Analytics Cloud, the SAPCP Cloud Connector will permit access to the /<Package> and all sub-paths on <Internal Host>:<Internal Port>.
  2. For all other cloud OData services, use the OData service URL in SAC which is accessible from the internet.
    • Note: In case you have exposed the on-premise OData datasource externally, the checkbox "Connect to an On-Premise OData service" must be left empty. Since the service URL is accessible externally on internet it can be considered as a Cloud datasource from SAC perspective. Otherwise you will need to expose the service per steps in paragrap "A" and mark this checkbox.

Resolution

  1. Unable to connect to OData Services with error: 503 There is no SAP Cloud Connector (SCC) connected to your subaccount. Requested opening of a tunnel for subaccount "<name of your subaccount>" and default SCC location ID, that is, empty string or simply not configured. Check the configuration on SCC and cloud side.. Check the connection details and user credentials then try again.

    • Reason: Subaccount not connected in SAP Cloud Connector.
    • Solution: Connect the subaccount of your tenant in the SAP Cloud Connector.
  2. Unable to connect to OData Services with error: Error sending request to proxy. Status: 403 Reason: Forbidden. Check the connection details and user credentials then try again.

      • Reason: Subaccount config not complete by Operations team.
      • Solution: Open Incident via the SAP ONE Support Launchpad on the component: LOD-ANA-BI (SAP Analytics Cloud)
    1. Unable to connect to Odata Services with error: 502 The requested URL could not be retrieved. Check the connection details and user credentials then try again.

      • Reason: [Connect to an On-Premise Odata service] is not checked.
      • Solution: Check it.
    2. The user doesn't have permission to access the requested resource.

      • Reason: Data Service URL is not properly defined/mapping is not done properly.
      • Solution: Make sure you're connecting to the Virtual Host / Port and the path is defined correctly.
      • More information in article 2739706.
    3. The request is unauthorized, please check data service url and credentials.

      • Reason: Credentials (User Name or Password) are incorrect.
      • Solution: Perform a test by navigating to the internal Odata URL and make sure the credentials are correct and the OData entities can be listed.
    4. Unable to connect to OData Services with error: response status 404. Check the datasource URL and on-premise option then try again.

      • Reason: The URL path is not defined properly. Although UserName/Password works, there should be a missing directory/folder or something incorrectly defined in the URL itself after the host.
      • Solution: Make sure you're using the same format of the URL like the one you are accessing internally.
    5. Authentication is required. Please select one authentication type.

      • Reason: Self explaining, please select one auth. type.
      • Solution: Choose another authentication type (like: Basic Authentication).
    6. Unable to connect to OData Services with error: 503 Application Server Error. Check the connection details and user credentials then try again.

      • Reason: Error being raised by the HANA WebDispatcher handling HTTP(S) requests.
      • Solution: Open Incident via the SAP ONE Support Launchpad to the HANA WebDispatcher team (Component/Expert Area: BC-CST-WDP) to troubleshoot further.

    See Also

    Your feedback is important to help us improve our knowledge base.

    Keywords

    EPM, SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, EPM-ODS, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics, OData, 403, On-Premise, premise, connector, hcc, scc, ODAta, HANA, URL, Service 503, 404, 403 , KBA , LOD-ANA , SAP Analytics Cloud , LOD-ANA-BI , SAP Analytics Cloud - Business Intelligence (BOC) , LOD-ANA-BR , SAP Analytics Cloud - Digital Boardroom , LOD-ANA-PL , SAP Analytics Cloud – Planning (BOC) , LOD-ANA-PR , SAP Analytics Cloud – Predictive (BOC) , Problem

    Product

    SAP Analytics Cloud 1.0