You’re offline. This is a read only version of the page.
2
Greetings,
I've noticed that I am accumulating debugger files for all users in my C:\Program Files (x86)\Microsoft Dynamics\GP2013\Data folder. The files names are "Debugger_userid_DBID.log" We have the support debugger installed and I suspect that this is what is generating these files. However, I am not yet an expert with the tool and would like to know if this should or should be creating log files.
Any suggestions are greatly appreciated. Thanks.
Jim
*This post is locked for comments
Hi Jim
Only just had this post pointed out to me.
The logs probably contain security access issues. GP Power Tools has the option to stop logging of security issues to the log files so they will no longer be created unless you have other features enabled that write log entries.
Note: MBS_Debug_Mode=TRUE is used to enable the Advanced Mode features so they appear on the menus of the Support Debugging Tool.
This dex.ini setting is no longer used in GP Power Tools as all features are visible (as long as security access to the windows is granted).
David
Hi Jim,
I suspect MBS_Debug_Mode=TRUE should be set to false to disable the generation of these logs.
Best regards,
Kirk
Mahmoud,
Below is the contents of my dex.ini file. This is from our terminal server and is shared by all users (I believe). I've read in some posts where users should have a dex.ini in there folders on the TS, but I've not looked into that yet (suggestions welcome).
Feel free to provide any feedback on this file. I feel like there is a lot of extra "junk" in the file and you'll also notice a gap/blank lines about half way down. I don't know what that is about. As always, thank you for your help!
|
[General] MICR_PmCopyPrinterBin=Automatically Select WDC_WinFieldSecurityMaintenance=272,183,626,250,1 76 ScriptDebuggerProduct=0 |
One further point, could you please share the content of the Dex.ini file located on ( C:\Program Files (x86)\Microsoft Dynamics\GP2013\Data\Dex.ini ) ?
Your feedback is highly appreciated,
Mahmoud,
As always, thanks for your response! When I open the SDT, everything is off. If I go to Tools, Stop Logging is disabled (expected). However, when I review your second suggestion, I see the same screen, but nothing is checked (trigger). I marked the disable checkbox on the Default (we do not have any others) and deleted all of the log files. I'll monitor the folder to see if any more files are created. I'll follow up soon. Thanks.
Jim
Hello Jim
You are right, these files are generated by the Support Debugging Tool. I assume that the "Automatic Debugger Mode" is enabled. You may go to Microsoft Dynamics GP > Tools > Support Debugging Tool.
As you can see below, the Automatic debugger mode is enabled, and therefore the SQL logging is on, Dexterity Script logging and Dexterity Script profiling as well.
To turn off the Automatic debugging mode, go to the the Support Debugging tool and click on Tools > Stop logging.
Another thing to consider. Go to Debugger > Setup Automatic Debugger Mode (on the Support Debugging Tool window) . Check whether a specific trigger ID is configured to start up automatically on logic.
Your feedback is highly appreciated,
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (