SAP Knowledge Base Article - Public

1220085 - How to trace report connectivity to SAP data sources, like SAP Tables or BEx Queries, from Crystal Reports?

Symptom

  • How do you enable logging when running connecting to SAP System from Crystal Reports?
  • How to trace connectivity issues to BEx Query, or ECC Tables, or InfoSet from Crystal Reports?
  • How to enable logging when troubleshooting issue connecting to SAP Tables, or SAP BW BEx Query from Crystal Reports?

Environment

  • SAP Crystal Reports 2008
  • SAP Crystal Reports 2011
  • SAP Crystal Reports 2013
  • SAP Crystal Reports 2016
       
  • SAP BusinessObjects Enterprise XI 3.1
  • SAP BusinessObjects Business Intelligence Platform 4.0
  • SAP BusinessObjects Business Intelligence Platform 4.1
  • SAP BusinessObjects Business Intelligence Platform 4.2

Resolution

  • For Tracing the SAP data connections with Crystal Reports, modify the registry keys corresponding to the type of SAP connectivity you will like to trace:
      
    ***WARNING***: The following resolution involves editing the registry. Using the Registry Editor incorrectly can cause serious problems. Use the Registry Editor at your own risk. Refer to the SAP Knowledge Base Article 1323322 for more information.
      
    1. Close Crystal Reports.
           
    2. Open the Microsoft Registry Editor.  
      1. In MS Windows, under the menu "Start", select "Run".
      2. Type "regedit"
      3. Then click "OK"
            
    3. Navigate to the registry corresponding to the version of the product you are using:    
      • For Crystal Reports 2008:
            
        • For 32 bit version of MS Windows: 
          HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP
              
        • For 64 bit version of MS Windows:
          HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Business Objects\Suite 12.0\SAP

            
      • For Crystal Reports 2011, 2013 and 2016:
           
        • For 32 bit version of MS Windows:
          HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Suite XI 4.0\SAP
              
        • For 64 bit version of MS Windows:
          HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP BusinessObjects\Suite XI 4.0\SAP
                
             
    1. Add the Directory in which the trace will be written to: ( Registry Key: TraceDir )
      1. Right-click the "SAP" registry subkey, and select "New - String Value"
      2. Type "TraceDir" as the name of the new string value.
      3. Right-click the registry entry "TraceDir", and select "Modify"
      4. Then set its value to the location where you want the trace files to be stored.  For example:  C:\SAP_Trace
             
    2. Below "SAP", select the registry key corresponding to the type of SAP Connection to trace:
      • Authentication
      • BW MDX Query Driver
      • BW Query Driver
      • BW Query Report Wrapper
      • Infoset Driver
      • ODS Drive
      • OpenSQL Driver
                  
    3. Change the value of the registry key "Trace", to: "Yes"
           
    4. Open Crystal Reports and create, or open and refresh your report based off an SAP data source to reproduce the issue; or
           
      For SAP BusinessObjects Enterprise or SAP BusinessObjects BI Platform, restart the Central Management Server, Crystal Reports Servers ( Cache servers, processing servers, ... ). Note that it is safe to restart all services, if you can. Also, if this is a cluster environment then, follow the above steps for each cluster and restart all the services.
            
      Important Note: Once you finish tracing, do not forget to turn off the trace.

 

Keywords

LOGGING, TYPE, ENABLE, CONFIGURE, START, XI R2, LOG FILES, BusinessObjects Enterprise. Integration Kit for SAP Logging , c2019106, CR Trace, Tracing R3, sap table, SAP BW, , KBA , BI-RA-CR , Crystal Reports designer or BusinessViews Manager , How To

Product

Crystal Reports 2008 V1 ; SAP Crystal Reports 2011 ; SAP Crystal Reports 2013 ; SAP Crystal Reports 2016