error while parsing ODBC column description types

[joelharder]

Hello,

I am currently experiencing an error in Alteryx Designer (v24.2). Every input/output data tool I use that accesses my (PostgreSQL) database gives the following errors:

Unexpected error while parsing ODBC column 1 description types:
Unexpected error while parsing ODBC column 2 description types:
...

repeated for however many columns are in the table.

This error only started occurring after I updated my PostgreSQL ODBC driver to the latest version (v17.00.00.04).

I could not find any instances of people having this error on the Alteryx community at all, but I did see that it was listed in more than one patch note as being fixed (such as https://help.alteryx.com/release-notes/en/release-notes/designer-release-notes/designer-2023-1-relea... and https://help.alteryx.com/release-notes/en/release-notes/designer-release-notes/designer-2024-1-relea...).

It floods my output with error messages which is annoying, but everything appears to be working as usual, and the data is getting properly input/output to the database regardless of these errors.

I’ve been playing with it for about a day now, and nothing I can think of gets it to go away. Any help would be greatly appreciated!

[apathetichell]

turn on increased logging in your odbc 64 connection. look at the logs. I'd recommend 1) downgrading your driver. 2) opening a support ticket with Alteryx. You have the newest (most likely to have bugs) version of Alteryx. you're also running a newer driver. Get your errors in your logs - and use that to explain your issue to support.

[BLamb]

I have also been seeing the exact same error. 

I've tried downgrading the odbc drivers but this didnt work - will raise a ticket with Alteryx also.

[apathetichell]

@BLamb- if you turn on logging in the ODBC you should be able to inspect the logs to see exactly what the error is/where it's being generated.

[spencermerlo]

Did you find a resolution to this error? We are experiencing the same issue.

[Arlete]

Has anyone found a solution to this error?

We are facing the same issue.

Thanks.

[apathetichell]

@Arletehey - I provided instructions on how to troubleshoot this. follow my instructions. see what you see. post the results.

[BLamb]

Hi, 

From looking at the logs the error seems to be stemming from: 

EXIT SQLGetDescFieldW with return code 100 (SQL_NO_DATA_FOUND)

Im thinking this is something to do with the driver bein a unicode connection but don't know enough to confirm this.

[jrainone]

same issue, same error in logs.  this was after upgrading alteryx to 2022.3.  i am opening a support ticket and if i get a fix will post it.

[jrainone · Accepted solution]

just downgraded to v11.01 and it is not throwing an error. 

https://www.postgresql.org/ftp/odbc/versions.old/msi/