When GP crashes for my customer, the error below pops up. They would like to know if that DEBUG button can be disabled. ScriptDebugger is set to FALSE inn the dex.ini. I told the customer that I believe it was built into the code and could not be disabled but would research it for them
The Dex.ini settings should be left as ScriptDebugger=FALSE and ScriptDebuggerProduct=0 unless actively using the Debug Menu.
FYI: You can get access to all the logging features (and more) without needing the debug menu using GP Power Tools.
The Debug button on the screenshot is not related to the Dexterity script Debugger.
It is a Windows button to access a Just in Time Debugger. They may be a way to remove it but I am not aware if the registry changes that would be needed.
The bigger issue is what is causing GP to crash. GP crashing means it never completed what it was doing and there could be data damage.
If you can replicate the crash, I would suggest using GP Power Tools to capture logs up to the point of the crash. The last script executed will be logged in the Script*.log file.
Regards
David
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
366
Share
Report
All responses (
Answers (
