You are creating a Live Data connection in SAP Analytics Cloud and get the following error: failed to connect to system.
- SAP Analytics Cloud 2017
- Data Sources: SAP HANA, S/4HANA, SAP BW, etc.
This message appears in Live connections when we can't stablish connection to the data source.
There are multiple data sources and methods to create a Live Connection, follow the steps that best describe your scenario.
Using Direct Connection (CORS)
When you select Direct Connection, your browser is connecting directly to SAP Analytics Cloud and your data source: HANA, BW, S/4HANA, Live Universe Connection, etc. using two different requests. This type of connection requires CORS enabled: Cross Origin Resource Sharing in your backend.
These are some of the possible causes:
- HTTPS Certificate: the certificate used by your data source is not trusted by your browser. This is easy to test: open a new browser tab and connect directly to the data source. For example, for HANA you can use: https://<xs-host:port>/sap/bc/ina/service/v2/GetServerInfo and verify if the certificate is automatically trusted. You shouldn't see any warnings or requested to accept exceptions. More information in KBA 2482807
- Authentication method not correctly configured in your data source. You may have selected SAML SSO in your connection as authentication method, but the current SAP Analytics User doesn’t exist in the data source (S/4HANA or HANA) or the user or connection (InA) doesn't allow to SAML as authentication method. To verify it, open a new tab in your browser and use the URL indicated in the previous example (HANA, S/4HANA, etc.). It should open without prompting for a new authentication. You will find notes on how to perform this action in the product’s documentation. you can use KBA 2545434 with more information on SAML SSO settings for SAP HANA and KBA 2487567 - Troubleshooting SAML assertions when configuring SAML SSO in SAP Analytics Cloud
- CORS configuration. After verifying the two previous steps, you may still have problems if the backend CORS configuration is incorrect. To verify that this is the case, you can open the Chrome Developer Tools and check that the Console shows an error similar to this:
https://<xs-host:port>/sap/bc/ina/service/v2/GetServerInfo?timestamp=1507241400382: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://yoursapanalytics.cloud' is therefore not allowed access
If you see that error in the console, it means that your data source has incorrect CORS settings, rejecting the request from your SAP Analytics Tenant to get data in the same page. Verify your data source CORS settings.
Using SAP Cloud Platform connection
This is similar to the previous scenario. You can only experience this problem if:
- CORS: you have selected authentication method None but you have not configured correctly CORS in HANA.
- SAML Single Sign On: the user doesn't exist in HANA or the SAML configuration for HANA is incorrect. For more details on how to enable SAML SSO to HANA in SAP Cloud Platform, you can use the blog SAP Analytics Cloud: Live Data Connection to HANA in SAP Cloud Platform With SSO
- Username requires to change password. If you selected the box on expiration of the password and the user must change the password on the next logon, you may see the following error if you open Chrome Developer tools in your browser: Status Code 403. You can test trying to connect directly to your HANA in SAPCP and verify if you are prompted to change your password.
Using Reverse Proxy
This applies to different on-premise data sources: HANA, S/4HANA, BW, SAP Universe Live Connection, etc.
You will need to examine the logs of your reverse proxy to examine why the connection failed. You still can have the same scenarios described for Direct Connection: CORS configuration and incorrect SAML SSO method.
- Certificate: your reverse proxy may not trust the certificate sent by your data source if you are connecting to it using HTTPS. To verify this is the issue, you can test simply using HTTP connection instead in your reverse proxy configuration and verify if this works correctly. You can either resolve the trust issue importing the certificate authority or configure your reverse proxy to ignore certificate warnings as indicated in KBA 2391607 for Apache.
- Path or settings: if you have incorrectly configured parameters in your reverse proxy, SAP Analytics Cloud can't connect or authenticate. To verify it, open a new tab in your browser and connect directly to the path used for your data source. For example, for HANA:
Live Data connection to SAP Universe
Many of the requirements for HANA also apply for Live connections to SAP Universes. For specific configuration you can use the KBA 2527393
- Help resources and free SAP Analytics Cloud content
- Help portal
- SAP Community ( Questions & Answers / Direct Link to ask question / Blogs )
- SAP community wiki
- Enhancement requests using SAP Customer Influence (formerly known as Ideaplace)
- Video tutorials
- Videos by topic areas: ( Overview, Models and Connections, Stories, SAP Digital Boardroom, Planning, Collaboration, Administration )
- Training events
- Past event recordings
- New user handbook
- 2487011 - What information do I need to provide when opening incidents with SAP Analytics Cloud
Your feedback is important to help us improve our knowledge base.
Please rate how useful you found this article by using the star rating feature at the beginning of this article.
HANA, SAML SSO, IdP, live, direct, remote, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJ, BOBJcloud, BOCloud., BICloud, BO Cloud, connecting, conecting, conectando, conexão, SAC, Business Objects, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics , KBA , LOD-ANA , SAP Analytics Cloud , LOD-ANA-BI , SAP Analytics Cloud - Business Intelligence (BOC) , Problem