Odbc драйвер postgresql ошибка 126

  • Remove From My Forums
  • Question

  • Logging into W2008R2 server with ID which is a member of «Administrators» group.  Installed 32-bit PostgreSQL driver via msi package.  When using 32-bit ODBC Administrator to create «System DSN», receive error as follows:
    «The setup routines for the PostgreSQL ANSI ODBC driver could not be loaded due to system error code 126: The specified module could not be found. (C:psqlODBC903binpsqlodbc30a.dll).

    I have verified the file does exist, by that name, in that location and the registry entries look good (I am not allowed to insert images until my account is «verified»).

    The ODBC Administrator lists the 32-bit driver (along with all the others) in the Drivers tab.  I am successful creating a System DSN if I choose a different 32-bit driver (e.g. the IBM DB2 driver).  Thank you for any direction you can provide.

Answers

  • Well, guess what?  After much pain, but absolutely worth it, I’ve gotten it to work.  It turns out that some postgre is compiled in C++
    and with Windows 2008, the C++ Redistributable is not installed by default.  So I installed this (won’t allow me to post links yet so I used _ so you will see where it is):

    www_microsoft_com/en-us/download/details_aspx?id=29

    And now I am able to configure the 32bit postgreSQL Unicode driver on my server, and of course I am also able to use it through my .asp page with connection string:

    connstr=  «Driver={PostgreSQL UNICODE};DATABASE=dbname;Server=ipaddress;UID=userid;PWD=password;»

    I really hope this helps, and thanks to all who looked into it.

    Thanks again,

    Denise

    • Proposed as answer by

      Thursday, February 21, 2019 8:58 PM

    • Marked as answer by
      JMARKS6205-2
      Thursday, February 21, 2019 9:40 PM

  • Hey Justin.  Thank you very much for the followup!  I have been trying to insert images to actually «show» you the registry values AND Windows explorer showing the file exists (so you could double check me), but have had no luck — this interface
    claims I have not «verified my account», ‘tho I believe I have done so several times — clearly, I’m missing something.

    The facts seem to be: 1.> the ODBC Admin displays the driver in its «Drivers» tab, 2.> when I try to «Add» a «System DSN», the ODBC Admin responds with the error I mention above, which explicity identifies the location and file name of the driver
    it is looking for.  The driver file DOES exist in that exact location — I did NOT «move» it there or anything like that, it was placed in the location by the driver installation process.  The registry entries seem to be spot on — which also
    makes sense, because the ODBC Admin is using those entries to both present the list of installed drivers, and to attempt to locate the driver files themselves.

    Because of time pressure, I was forced to «work around» the issue by moving our code to use the PostgreSql 64-bit drivers.   I will research the MDAC environment, based on the link you provided me above — thank you for that as well.  For now,
    it probably makes sense to close this thread.  THANKS for getting back to me.  — Jon

    • Marked as answer by
      Justin Gu
      Monday, April 28, 2014 4:50 PM

I am having an issue and just can’t seem to resolve it. I cannot get my postgresql connection string to work. Everything works fine with I create a DSN, but when I try to utilize the driver in a connection string I keep getting the datasource not found error. I have PostgreSQL ANSI(x64),PostgreSQL ODBC Driver(ANSI),PostgreSQL ODBC Driver(UNICODE),PostgreSQL Unicode(x64). In the connection string I use the Unicode one. Again, in the DSN and ODBC Manager it works great. But I am using classic ASP (in IIS7) to pull data from the dB and I keep getting error. People were referring me to the connection string site, and I’ve tried everything I can think of. To me, it looks perfect, but just can’t get past that error. Here is the string that I am using:

cst = "Driver={PostgreSQL ODBC Driver(UNICODE)};Server=ipaddress;Port=5432;Database=dbname;Uid=uid;Pwd=pw;"

Please please help?

By the way, I’m new to this site, so if I do something wrong with this question, please let me know. Thanks so much.

  • Remove From My Forums
  • Question

  • Logging into W2008R2 server with ID which is a member of «Administrators» group.  Installed 32-bit PostgreSQL driver via msi package.  When using 32-bit ODBC Administrator to create «System DSN», receive error as follows:
    «The setup routines for the PostgreSQL ANSI ODBC driver could not be loaded due to system error code 126: The specified module could not be found. (C:psqlODBC903binpsqlodbc30a.dll).

    I have verified the file does exist, by that name, in that location and the registry entries look good (I am not allowed to insert images until my account is «verified»).

    The ODBC Administrator lists the 32-bit driver (along with all the others) in the Drivers tab.  I am successful creating a System DSN if I choose a different 32-bit driver (e.g. the IBM DB2 driver).  Thank you for any direction you can provide.

Answers

  • Well, guess what?  After much pain, but absolutely worth it, I’ve gotten it to work.  It turns out that some postgre is compiled in C++
    and with Windows 2008, the C++ Redistributable is not installed by default.  So I installed this (won’t allow me to post links yet so I used _ so you will see where it is):

    www_microsoft_com/en-us/download/details_aspx?id=29

    And now I am able to configure the 32bit postgreSQL Unicode driver on my server, and of course I am also able to use it through my .asp page with connection string:

    connstr=  «Driver={PostgreSQL UNICODE};DATABASE=dbname;Server=ipaddress;UID=userid;PWD=password;»

    I really hope this helps, and thanks to all who looked into it.

    Thanks again,

    Denise

    • Proposed as answer by

      Thursday, February 21, 2019 8:58 PM

    • Marked as answer by
      JMARKS6205-2
      Thursday, February 21, 2019 9:40 PM

  • Hey Justin.  Thank you very much for the followup!  I have been trying to insert images to actually «show» you the registry values AND Windows explorer showing the file exists (so you could double check me), but have had no luck — this interface
    claims I have not «verified my account», ‘tho I believe I have done so several times — clearly, I’m missing something.

    The facts seem to be: 1.> the ODBC Admin displays the driver in its «Drivers» tab, 2.> when I try to «Add» a «System DSN», the ODBC Admin responds with the error I mention above, which explicity identifies the location and file name of the driver
    it is looking for.  The driver file DOES exist in that exact location — I did NOT «move» it there or anything like that, it was placed in the location by the driver installation process.  The registry entries seem to be spot on — which also
    makes sense, because the ODBC Admin is using those entries to both present the list of installed drivers, and to attempt to locate the driver files themselves.

    Because of time pressure, I was forced to «work around» the issue by moving our code to use the PostgreSql 64-bit drivers.   I will research the MDAC environment, based on the link you provided me above — thank you for that as well.  For now,
    it probably makes sense to close this thread.  THANKS for getting back to me.  — Jon

    • Marked as answer by
      Justin Gu
      Monday, April 28, 2014 4:50 PM

Well, guess what? After much pain, but absolutely worth it, I’ve gotten it to work. It turns out that some postgre is compiled in C++ and with Windows 2008, the C++ Redistributable is not installed by default. So I installed this:
http://www.microsoft.com/en-us/download/details.aspx?id=29
And now I am able to configure the 32bit postgreSQL Unicode driver on my server, and of course I am also able to use it through my .asp page with connection string:
connstr= «Driver={PostgreSQL UNICODE};DATABASE=dbname;Server=ipaddress;UID=userid;PWD=password;»
I really hope this helps, and thanks to all who looked into it.
Thanks again,Denise

> Date: Sun, 1 Jun 2014 19:29:32 -0700
> From: adrian(dot)klaver(at)aklaver(dot)com
> To: denisemichele(at)outlook(dot)com; pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] 126 Error Connecting With psqlODBC 32 bit
>
> On 06/01/2014 01:53 PM, Adrian Klaver wrote:
> > On 05/22/2014 04:37 PM, Denise McGrath wrote:
> >> Hi,
> >>
> >> I got your email from the faq page
> >> http://psqlodbc.projects.pgfoundry.org/faq.html. I am having a really
> >> difficult time setting up the 32 bit psqlodbc driver. I have the 9.3
> >> version of PostgreSQL. It downloaded the psqlodbc_09_03_0210-x64
> >> <http://ftp.postgresql.org/pub/odbc/versions/msi/psqlodbc_09_03_0210-x64.zip>
> >> and
> >> that worked fine as far as connecting to the database through
> >> pgAdminIII, but I need to use a 32 bit because I am running an asp page
> >> that connects to the PostgreSQL 9.3 database.
> >>
> >> So I downloaded the psqlodbc_09_03_0210.zip
> >> <http://ftp.postgresql.org/pub/odbc/versions/msi/psqlodbc_09_03_0210-x64.zip>
> >> latest
> >> driver.
> >
> >>
> >> «The setup routines for the PostgreSQL ANSI ODBC driver could not be
> >> loaded due to system error code 126: The specified module could not be
> >> found. (C:Program Files (x86)psqlODBC903binpsqlodbc35w.dll).»
> >>
> >
> >> Is there anything else that I am missing? Please please help as I have
> >> working on this for almost a week with no luck and am completely
> >> baffled :-(
> >
> > Anyone have an idea on what is going on here. I confirmed the error
> > using a clean Windows Server 2008R2 AMI on AWS. I tried to add a 32bit
> > DataSource and got the same error.
>
> Well the previous comment was about psqlodbc_09_03_0210.zip.
>
> With psqlodbc_09_03_0300-x64.zip I cannot even get it to install.
> Running Dependency Walker psqlodbc30a.dll shows several issues seen in
> the attached screenshot.
>
> I see the same thing with psqlodbc_09_03_0300.zip
>
> >
> >>
> >> Thanks!
> >> Denise
> >
> >
>
>
> —
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com

Hi Ibarrau,

Thanks for your response.

Postgres is in Google cloud.  I tested the ODBC test connection and the message displayed as test successful. When i try to connect Power BI with ODBC then i get the below error.

 Details: «ODBC: ERROR [IM003] Specified driver could not be loaded due to system error 126: The specified module could not be found. (PostgreSQL ANSI, C:Program FilesTableauDriverspsqlODBC906binpsqlodbc30a.dll).»

i tried to connect the database through postgres directly, i downloaded npgsql-4.1.1 but still did not connect.

So both the ways i was unsuccessful in connecting to the postgres DB. Please help

Thanks & Regards,

Понравилась статья? Поделить с друзьями:
  • Octopus frp tool ошибка при запуске 0xc000007b
  • Oct 7 ошибка старлайн а93
  • Ocs inventory service код ошибки 20
  • Ocr с ошибками что это
  • Oce plotwave 345 ошибка 22552