Forum Discussion
Ayupchap
Helper III
7 years agoODBC Error - Not sure how to resolve it
Hi all OK so I am getting this error with an SQL query: Details: "ODBC: ERROR [22P05] ERROR: character with byte sequence 0xe2 0x80 0x8e in encoding "UTF8" has no equivalent in encoding "WIN1...
Ayupchap
Helper III
7 years agoAh ok, yes, postgres
So I changed the DSN to unicode in the ODBC connector. I thought it had worked as it shows me the load sample data
Any idea why this might still be happening? Thanks for your help on this.
HotChilli
Community Champion
7 years agoGetting closer!
Can you experiment by clicking 'edit' instead of load. Can you get to the Advanced editor and try a different encoding? Try selecting a more limited selection of fields. That might help you discover whether it's an unusual character that doesn't translate to code page 1252 in Windows or a hidden character.
Found this on the forum:
Using the postgres ODBC and configuring the connection in unicode mode on System DSN the issue is solved (PBI connection will be ODBC)
https://www.postgresql.org/ftp/odbc/versions/dll/