Solved ODBC tracing log, I cannot create one for MariaDB support to examine

watching that video, he can open up system DSN tab. I can not even running as admin the ODBC 32 bit windows app.

I want to create a tracing log to send into MariaDB support

Well, my Dell 7530 allows me to select options for ODBC tracing, so maybe it will work.

Why the desktop refuses?

I was able to create just one trace file on the Dell 7530, then it refused to make any more trace files.
How flaky is that?
Why is this being so difficult?

It was also missing registry entries according to this site, which I added before I made a log file.

I figure very few people here have made trace log files for ODBC drivers.

Is there some dumb rule that once a trace log file is created, it must always continue to use that one trace log file for a user?
And maybe just continually appended onto?
And the trace log file cannot be renamed or moved from where it was originally created? I mean that would make zero sense to me.
The ODBC manager allows for a user selectable place to write a log file. I renamed and it removed it to the desktop to zipit and send it off.
Then created a new folder on C: drive for future trace logs. The original location was in user appdata local temp, buried in a place difficult to get to. I know sometimes programmers do stupid stuff like this.

a

rebooted machine and following more guides modified registry manually putting in locations of the files, as the ODBC manager refused to do it, still no worky


to here

beginning to think its a bug when it works.

was googling then read this

set tracing to not be machine wide. Started tracing and it has made 2 trace logs in the location I spec'd manually.

this is super flakey. Day ago, it made a trace log without me inputting paths for the files in registry settings manually, and it was set for machine wide.

I could tell it was working as my program suddenly slowed way down

stopped tracing, renamed file started and made another trace log.

will mark to resolved for now, but i did nothing to make work what should just work.

will do same steps on the desktop to see what happens

yes changing all those things on the AMD desktop, now produces a trace log
user on laptop is called user
user here on amd desktop is called sdown

My particular manually set registry changes, must be set the same in both places
Windows ODBC manager is supposed to set this for you, but on 2 different Pc's it did not, you have to manually set it up.
set Trace to 1 means enabled

current user


local machine

I did just notice ODBC manager when turning tracing on changes Trace reg setting to 1 and turning tracing off, sets Trace reg setting to 0
So it does actually look at the reg settings

ODBC manager just never wrote out the Tracefile and TraceDll settings, left them at 1

Since I had to do that manually, perhaps all logs will stay at that manual location even if I change [path settings in ODBC manager, will test that next

well now ODBC manager is changing it. Could it be when I first looked at the setting it was set to 1 instead of blank?

Well it is changing it now. Change the path in ODBC manager, it updates the registry the way it should.
It was not doing this earlier today,