SAP Knowledge Base Article - Public

2630653 - How to Troubleshoot and Trace SAP Analytics Cloud connecting to on-premise / acquired / imported data *** Master KBA ***

Symptom

  • You are using SAP Analytics Cloud (SAC) and want to connect to data stored on your network:
    • SAP Business Warehouse (BW),
    • SAP BW/4HANA,
    • SAP S/4HANA,
    • SAP HANA,
    • Universes,
    • SQL Server databases etc.
    • Note: All supported data sources are listed here: Data Connectivity – Import.
  • What tracing and logging information is needed to help troubleshoot errors and issues?

Environment

  • SAP Analytics Cloud (Enterprise)

Resolution

Trace the SAP Cloud Platform (SAP CP / SAPCP) Cloud Connector:

Trace the SAP Analytics Cloud Agent:

  • SAP Analytics Cloud Agent is a web application (C4A_AGENT) and is usually deployed in the Apache Tomcat webserver.

  • Tomcat Access Logger can be used to determine if communication from the SAP CP Cloud Connector is reaching the SAP Analytics Cloud Agent:
    See http://www.techstacks.com/howto/configure-access-logging-in-tomcat.html
    • This log should contain a similar entry when the SAP CP Cloud Connector contacts the SAP Analytics Cloud Agent.

10.165.19.90 - orca [09/Apr/2019:12:36:30 -0700] "GET /C4A_AGENT//deploymentInfo HTTP/1.1" 200 19

  • Tomcat Error Logger can be used to troubleshoot errors between SAP Analytics Cloud Agent and Data Source such as SAP Universe.
    • The Tomcat error log can be found at <Tomcat_Install_Dir>/logs/tomcat-stderr.<DATE>.log   (for example "tomcat7-stderr.2018-04-09.log").
      • Inside this log file you should see an entry for the error.
        Here are some examples:
        • April 09, 2018 11:29:48 AM com.sap.fpa.cloud.internal.DAException logException
        • SEVERE: Could not reach CMS '10.165.28.118'. Specify the correct host and port and check for network issues. (FWM 20030)
        • Could not reach CMS '10.165.28.118'. Specify the correct host and port and check for network issues. (FWM 20030)
    • The Tomcat catalina log can be found at <Tomcat_Install_Dir>/logs/catalina.<DATE>.log   (for example "catalina.2018-04-09.log")
      • Inside this log file you should see an entry for the error. Here are some examples:
        • SEVERE [http-nio-8080-exec-4] com.sap.fpa.logging.CoreLogger.log Enterprise authentication could not log you on. Please make sure your logon information is correct. (FWB 00008)
          com.crystaldecisions.sdk.exception.SDKServerException: Enterprise authentication could not log you on. Please make sure your logon information is correct. (FWB 00008)
          cause:com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2
          detail:Enterprise authentication could not log you on. Please make sure your logon information is correct. (FWB 00008)
          The server supplied the following details: OCA_Abuse exception 10496 at [exceptionmapper.cpp : 67] 42040 {}
          ...Enterprise authentication could not log you on. Please make sure your logon information is correct. (FWB 00008)

Traces on various data sources:

  • SAP Universe: 2531819 - Troubleshooting errors importing SAP Universe (UNX) in SAP Analytics Cloud
  • SAP HANA: 2525191 - How to use SAP HANA MDS tracing with SAP Analytics Cloud (SAC)?
  • SAP BW / SAP BW/4HANA2834064 - How to enable RSTT Trace in SAP BW for import BW scenario on specific query or CDS View in SAP Analytics Cloud (SAC) 

Browser side tracing (Chrome Developer Tools / HTTP Archive Files (HAR)):

  • Article 2280022 - How to collect HAR files in SAP Analytics Cloud
    • The Chrome Developer Tools network panel is useful for troubleshooting page loading performance and obtaining request / response information.
    • In the network panel, detailed action log and resource information for each request can be seen by reviewing the Header, Preview, Response, Cookies, and Timing sections.
      • Header: The Request Payload is important to get the detail action log and resource information
      • Preview: In preview tab, we can also find the detail data source information.
      • Response: In response tab, we can find the status information for the request resource data.
      • Timing: Timing information is helpful when troubleshooting the performance issue. In the timing tab, we can know how the time is distributed for each request, especially for the request time and waiting time.
  • Article 2413393 - How to record timelines in Chrome Developer Tools in case of SAP Analytics Cloud performance issues

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, Import, Acquired, Acquire, SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, Troubleshoot, Troubleshooting, bp, bps, T-shooting , KBA , sap sac load failures , load failures , loading dataloads data loads , import connection , bw note checkig tool sac , checking , LOD-ANA-BI , Business Intelligence Functionality, Analytic Models , LOD-ANA-PL , Planning , LOD-ANA-BR , SAC Boardroom , LOD-ANA-PR , SAC Predicitive , Problem

Product

SAP Analytics Cloud 1.0