Forum Discussion

Ayupchap's avatar
Ayupchap
Icon for Helper III rankHelper III
8 years ago

ODBC 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 "WIN1252";
Error while executing the query"

 

 

Anyone know how I can get around this issue?

Need Help
Show and Tell

9 Replies

  • Johannf78's avatar
    Johannf78
    Icon for Advocate I rankAdvocate I
    4 years ago

    Clicking on the "Manage DSN" Button and changing the driver from "PostgreSQL ANSI(x64)" to "PostgreSQL Unicode(x64)" solved it for me.

    You have to save and restart the machine tough 

  • Anonymous's avatar
    Anonymous
    Not applicable
    4 years ago

    Conseguimos resolver da seguinte forma.

     

    Driver={PostgreSQL Unicode(x64)}; Server= IP do servidor ; Port= Nome da porta; Database= Nome do Bando de dados

     

    Colocando isso na conexão do ODBC, e mudei o DNS do usuário colocando unicode, e no DNS do sistema para Unicode também.

    • Anonymous's avatar
      Anonymous
      Not applicable
      2 years ago

      This solution solved the problem for me! Fortunately, I can read Spanish. lol. Install the PostgreSQL ODBC for Unicode(x64) and use that one instead when connecting to the DB. In my case, I was trying to connect to AWS Cloud version of PostgreSQL in Supabase. 

    • Ayupchap's avatar
      Ayupchap
      Icon for Helper III rankHelper III
      8 years ago

      Ah 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's avatar
        HotChilli
        Icon for Community Champion rankCommunity Champion
        8 years ago

        Getting 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/

         

  • dataco's avatar
    dataco
    New Member
    7 years ago

    Hi,

     

    I have same problem, anyone have find out solution?, please

  • Anonymous's avatar
    Anonymous
    Not applicable
    2 years ago

    I had this issue with Power Bi and Postgres. The solution was to setup a SYSTEM DSN (Not user DSN) with Unicode NOT Ansi64 in the odbc driver

     

     

  • otavio's avatar
    otavio
    New Member
    2 years ago

    Para que tiver com esse problema no Power BI, na barra de endereco na sua fonte de dados altere o nome de "PostgreSQL ANSI (x64)" para "PostgreSQL Unicode (x64)".

     

    No meu caso resolveu o problema