KB46125: How to trace the communication of the MicroStrategy provided Salesforce ODBC driver

During trouble-shooting cases involving the Strategy Salesforce ODBC driver, sometimes it may be useful, or even necessary, to do a trace of the communication done by the driver. The step below outlines the procedure for enabling tracing of the Salesforce driver.
 

1. Locate the file ddlog.properties. By default this file is in the following folder "C:\Program Files (x86)\Common Files\MicroStrategy\ODBC\ddlog.properties"
    
   
2. Edit the property “java.util.logging.FileHandler.pattern” in that file as per the following example to specify the location where the trace file should be written:
    
   For example, to write to the C:\tmp directory specify the value as follows making sure to escape any backslashes:
    
   
   java.util.logging.FileHandler.pattern = C:\\tmp\\ddlog%g.log
   
    
   
3. Edit the properties at the bottom of that file to specify FINEST instead of FINER / OFF.
    
   For example,
   
   PHP
   
   # logger for web service adapter: use CONFIG, FINE, FINER, FINEST
   com.ddtek.cloud.adapter.level = FINEST
   # logger for sql engine: use CONFIG, FINE, FINER, FINEST
   com.ddtek.cloud.sql.level = FINEST
   # logger for jdbc spy: use FINER or FINEST
   com.ddtek.jdbc.cloud.level = FINEST
   # logger for communication to ODBC driver: use FINER
   com.ddtek.cloud.drivercommunication.level = FINER
   
   
   
4. Launch the Microsoft ODBC Administrator tool and  choose to configure the Strategy Salesforce ODBC data source.
    
   
5. To enable SalesForce JAVA tracing, add the file name and location of “ddlog.properties” to the 'Log Config File' property in the 'Advanced' tab of the Strategy Salesforce ODBC Data Source.
    
   
   C:\Program Files (x86)\Common Files\MicroStrategy\ODBC\ddlog.properties
   
    
   
6. Reproduce the error in the application.  The log files will be generated in the location specified for the java.util.logging.FileHandler.pattern in the ddlog.properties file.
    
7. After the problem has been reproduced and the logs created disable tracing by setting the values back to OFF or FINER.

 
This is a fairly robust trace and as such should not be left on during general use due to the performance impact it would have.