Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. KB 850996 - How to create a Dexsql.log file to troubleshoot error messages in Microsoft Dynamics GP

KB 850996 - How to create a Dexsql.log file to troubleshoot error messages in Microsoft Dynamics GP

View products that this article applies to.

INTRODUCTION

This article describes how to create a Dexsql.log file for Microsoft Dynamics GP.

↑ Back to the top

More Information

When you receive an error message in Microsoft Dynamics GP, a Dexsql.log file is a helpful tool that can frequently provide more information to troubleshoot issues. If you can re-create the error message, the Dexsql.log file can capture this information.


To create a Dexsql.log file, follow these steps:
  1. Open the Dex.ini file. By default, this file is in the following location:
    • Microsoft Dynamics GP 10.0 and later releases:  
      C:\Program Files\Microsoft Dynamics\GP\Data
  2. Locate the following statements in the Dex.ini file: 
    SQLLogSQLStmt=FALSE
SQLLogODBCMessages=FALSE 
SQLLogAllODBCMessages=FALSE
  3. If the statements are currently set to FALSE, change the statements to TRUE, as follows: 
    SQLLogSQLStmt=TRUE 
SQLLogODBCMessages=TRUE 
SQLLogAllODBCMessages=TRUE
  4. Start Microsoft Dynamics GP. If Microsoft Dynamics GP is already started, exit Microsoft Dynamics GP, and then restart it.
  5. Re-create the scenario in which you received the error message. Log into the window needed, bug before you do the steps to generate the error message, you should go  clear out the dexsql.log that has ran to this point (as you only want it to capture generating the error message only, and don't need anything captured up to this point ). To do this, go to the next step.
  6. In Windows Explorer, open the Microsoft Dynamics GP application folder that you opened in step 1. Locate the Dexsql.log file.  Simplly delete or rename this file, as you do not need anything it captured up to this point.

    (If you do not see the Dexsql.log file listed, click View, and then click Refresh so that you can see the new file.  Or check your path.)
  7. Now back in Microsoft Dynamics GP, continue to perform the final steps to re-create the error message.  A new Dexsql.log file will be generated in the Microsoft Dynamics GP application folder again, that contains only the syntac of generating the error message.
  8. Turn the dexsql.log off:  To do this, open the Dex.ini file, and then reset the statements to FALSE or to the original settings.  (Note: it will continue to run until the user logs out of Microsoft Dynamics GP and back in again.  It doesn't hurt to leave it run either, but may result in the log getting large and causing performance issues down the road.)

↑ Back to the top

Keywords: kbmbsgp10,, kbfreshness2007, kbentirenet, kbexpertisebeginner, kbhowto, kbexpertiseinter, kbmbspartner, kbmbsmigrate, kbmbspilot, kb

↑ Back to the top

Article Info
Article ID : 850996
Revision : 3
Created on : 6/5/2018
Published on : 6/5/2018
Exists online : False
Views : 511