You might say that I am biased. As the developer of the Support Debugging Tool for Microsoft Dynamics GP, I believe that every Microsoft Dynamics GP site (v8.0, v9.0 & v10.0) should have the tool installed. Even if you don’t need it straight away, it is always there when you do.
You might get an error condition occurring that you would like to obtain logs for. However, if you modify the Dex.ini file to turn on logging as described in the Knowledge Base (KB) articles below, you will need to restart the application for the settings to take effect. Many times, you will find that restarting the application has resolved the issue and you have not got any closer to identifying the root cause.
If you had the Support Debugging Tool already installed, you could start the logging manually with a single mouse click without needing to exit the application at all. Once the error has occurred you can stop the logging and provide the resulting logs to support for analysis. Then the root cause can be found and the issue fixed.
My friend Mariano Gomez has added to his blog post First Look at Support Debugging Tool for Microsoft Dynamics GP with an article on MSDynamicsWorld.com, please have a read:
Note: You will need to register your free account to be able to read the entire article.
You can also find a post about the tool on the Microsoft Dynamics GP UK Blog Post: Support Debugging Tool.
If you want more information about the release of the tool (including the download links from PartnerSource), have a look at the announcement post on this blog: Support Debugging Tool – The wait is over
For other related articles and posts have a look at the Support Debugging Tool Tag page.
I am currently working on a new build of the Support Debugging Tool with new features and enhancements to existing features… watch this blog for more info.
06-May-2009: Added link to the Support Debugging Tool Tag page.