1220085 - How to trace SAP data source connections in Crystal Reports? (SAP Tables, SAP BW Queries,...)

• How do you enable logging when connecting to SAP Data Sources from Crystal Reports?
• How to trace connectivity to SAP BW Query, or ECC Tables, or ERP Systems, or InfoSet query from Crystal Reports?
• How to enable logging when troubleshooting issue connecting to SAP Tables, or SAP BW Query from Crystal Reports?

• SAP Crystal Reports 2013
• SAP Crystal Reports 2016
• SAP Crystal Reports 2020    

• To trace SAP data source connections in Crystal Reports, modify the registry key corresponding to the type of SAP data source connection you are using:
      
  WARNING: The following involves editing the Microsoft Registry. Using the Microsoft Registry Editor incorrectly can cause serious problems. Use the Microsoft 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. (regedit)
1. 2.1 In MS Windows, under the menu "Start", select: Run
2. 2.2 Type: regedit
3. 2.3 Then click: OK
                   
3. Navigate to the registry corresponding to the version of Crystal Reports, and version of MS Windows you are using:       

• For Crystal Reports 2020: (64bit)
  HKEY_LOCAL_MACHINE\SOFTWARE\SAP BusinessObjects\Suite XI 4.0\SAP
      
• For Crystal Reports 2013, 2016: (32bit)
• 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
               
4. Add the path to the directory where the trace will be written to: ( Registry Key: TraceDir )
1. 4.1 Right-click the registry subkey: "SAP", and select: "New - String Value"
2. 4.2 For the new string value, type: TraceDir
3. 4.3 Right-click the registry entry: "TraceDir", and select: "Modify"
4. 4.4 Add the path to the location where you want the trace files to be stored.  For example:  C:\SAP_Trace
                   
5. 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
            
6. Change the value of the registry key "Trace", to: Yes
        
7. Open Crystal Reports and reproduce the issue by:
   - Creating a new report based on the SAP Data Source Connection you are experiencing an issue; or
   - Opening and refreshing your report based on a SAP data source connection.         
      
   Important Notes:
         
• For SAP BusinessObjects Business Intelligence Platform, for the trace to work, restart the following servers:
  - Central Management Server (CMC),
  - Crystal Reports Cache Server,
  - Crystal Reports 20XX Processing Server
  
  Or you can restart all the servers, if you can.
  Also, if it is a cluster environment, then follow the above steps for each cluster and restart all the servers.
      
• Once you finish tracing, it is very important to turn off the trace, by setting the registry key: Trace, to: False, for the connectivity type you were tracing, otherwise, if you do not turn off the trace, it will cause performance issue.

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 Business View Manager , How To

SAP Crystal Reports 2013 ; SAP Crystal Reports 2016 ; SAP Crystal Reports 2020