I have this error on login but I don’t know at all how I can search for an error ?
I tried to run it as admin and still not working
I compared to another DMT.exe.config file (From a 2025.2 environment) and it seems similar so I don’t see why this new environment in 2026.1 doesn’t work
What comes to mind is maybe the Environment is not pointing to the right server. As for tracing an error message in an exe I don’t know of a clean way. You could try running the DMT directly through cmd and then getting the error level there. You would run the following command in the folder you have Power Tools installed.
DMT.exe -User {yourusername} -Pass {yourpassword} -ConfigValue {yourserver}.sysconfig -LogDetailedException True
echo %ERRORLEVEL%
Pick your environment in the first dropdown. It always defaults to the top one and is wrong.
Also make sure update PowerTools every time there is a patch. Even the dot patches require a new install or at least from .5 to .9 did.
I had a ticket with Support for this issue. It is the incorrect environment. The fix provided by Support for me was to remove all the incorrect sysconfig files in \<powertoolsinstalldir>\config to another folder (e.g., “SAVE”).
So in my \config folder, there is only the one legit sysconfig:
In the \SAVE folder are all the incorrect ones:
Support said that these were all just left over from development testing, so they have no business being there. Development needs to clean up their stuff before they ship product!
I’m glad that they are continuing to develop DMT but sometimes it feels like as a heavy DMT user that I am also a beta tester.
I think DMT is the best of the tools. Not much has really changed over the years other than a facelift.
The first command works (It just opens the interface if I put .\ before, otherwise, it doesn’t recognize the DMT.exe command) but I don’t see how it’s supposed to print the error after that ?
Already removed everything from there but I only had 2-3 incomplete files on my side (default.sysconfig being one of them). Didn’t work unfortunately but that’s nice to know!
As I understand it really just sends a number back on what level of error it was in windows. Was a bit of a long shot on possible issue since you can’t really debug an exe without decompiling it.
But glad it was just the wrong server selected.
But glad it was just the wrong server selected.
Not sure where I wrote this but it still isn’t working. I’ll try to see with our consultant for some help with that