Обсуждение: Issues with PostgreSQL ODBC on Win 10
Hi,
I'm trying to debug a third party ODBC application but I can't seem to get the ODBC driver (latest version, from psqlodbc_09_05_0100-x86.zip) to log anything under Windows 10.
The check fields CommLog as well as MyLog don't seem to have any effect at all. But also the ODBC Admin built-in tracing doesn't work. It's definitely not a problem with the tracer as it traces other ODBC connections just fine.
Is it maybe necessary to select a custom trace DLL for this to work? Or is this just a bug?
Viktor
I'm trying to debug a third party ODBC application but I can't seem to get the ODBC driver (latest version, from psqlodbc_09_05_0100-x86.zip) to log anything under Windows 10.
The check fields CommLog as well as MyLog don't seem to have any effect at all. But also the ODBC Admin built-in tracing doesn't work. It's definitely not a problem with the tracer as it traces other ODBC connections just fine.
Is it maybe necessary to select a custom trace DLL for this to work? Or is this just a bug?
Viktor
Hi Viktor,
Don't Commlog or Mylog files exist in User(\Users\username) folder?
regards,
Hiroshi Inoue
On 2016/02/02 5:29, Viktor Trojanovic wrote:
Hi,
I'm trying to debug a third party ODBC application but I can't seem to get the ODBC driver (latest version, from psqlodbc_09_05_0100-x86.zip) to log anything under Windows 10.
The check fields CommLog as well as MyLog don't seem to have any effect at all.
Don't Commlog or Mylog files exist in User(\Users\username) folder?
regards,
Hiroshi Inoue
Hi Hiroshi,
So, that's where they were hiding! They are here, and they are called mylog_xxxx.log and psqlodbc_xxxx.log. I assume the latter is produced by the Commlog setting.
I guess the user interface of the driver could need some updating as it clearly states that the logs are to be found in the root (c:\) folder.
But in that case it's not so bad that the built-in ODBC trace isn't working as all the needed information is in the logs.
Thanks for the pointer!
Regards,
Viktor
On 02.02.2016 00:11, Inoue, Hiroshi wrote:
Hi Viktor,On 2016/02/02 5:29, Viktor Trojanovic wrote:Hi,
I'm trying to debug a third party ODBC application but I can't seem to get the ODBC driver (latest version, from psqlodbc_09_05_0100-x86.zip) to log anything under Windows 10.
The check fields CommLog as well as MyLog don't seem to have any effect at all.
Don't Commlog or Mylog files exist in User(\Users\username) folder?
regards,
Hiroshi Inoue
So, that's where they were hiding! They are here, and they are called mylog_xxxx.log and psqlodbc_xxxx.log. I assume the latter is produced by the Commlog setting.
I guess the user interface of the driver could need some updating as it clearly states that the logs are to be found in the root (c:\) folder.
But in that case it's not so bad that the built-in ODBC trace isn't working as all the needed information is in the logs.
Thanks for the pointer!
Regards,
Viktor
Hi Viktor,
When the driver couldn't write logs to root folder, it tries to write logs in user folder.
regards,
Hiroshi Inoue
On 2016/02/02 9:02, Viktor Trojanovic wrote:
Hi Hiroshi,On 02.02.2016 00:11, Inoue, Hiroshi wrote:Hi Viktor,On 2016/02/02 5:29, Viktor Trojanovic wrote:Hi,
I'm trying to debug a third party ODBC application but I can't seem to get the ODBC driver (latest version, from psqlodbc_09_05_0100-x86.zip) to log anything under Windows 10.
The check fields CommLog as well as MyLog don't seem to have any effect at all.
Don't Commlog or Mylog files exist in User(\Users\username) folder?
regards,
Hiroshi Inoue
So, that's where they were hiding! They are here, and they are called mylog_xxxx.log and psqlodbc_xxxx.log. I assume the latter is produced by the Commlog setting.
I guess the user interface of the driver could need some updating as it clearly states that the logs are to be found in the root (c:\) folder.
.
When the driver couldn't write logs to root folder, it tries to write logs in user folder.
regards,
Hiroshi Inoue