| Subject | Re: [firebird-support] Unable to connect to data source: library 'gds32.dll' failed to load |
|---|---|
| Author | |
| Post date | 2014-01-03T23:00:23Z |
I started odbcad in system32 and syswow64 and they both show ODBCFB.DLL for Firebird. I see there is a OdbcFb.dll in System32.
I moved gds32.dll into SysWOW64 and the Perl client crashes immediately after trying to connect.
I remove gds32.dll from SysWOW64 and it still crashed.
I removed the 64-bit kit and removed all related files from system32 and syswow64.
Client stops with no driver defined error.
Installed 64-bit driver, now I get the gds32.dll failed to load error.
I load gds32.dll into SysWOW64 and I get the same error.
Interestingly, when I loaded the driver again it put a copy of the ODBCFB files back in both SysWOW64 and System32.
What I don't understand is why am I getting a message related to "gds32.dll?" It's not part of the Firebird driver. It's not part of Perl, the error message shows that it's coming from the Firebird driver. No changes were made to any of the server connection parameters.
I just loaded FlameRobin, put a copy of gds32.dll in SysWOW64 and it connected immediately.
But I try my 64-bit Perl client and it stops.
---In firebird-support@yahoogroups.com, <mark@...> wrote:On 2-1-2014 20:02, bandersnoot@... wrote:
> My PC was changed to Windows 7 64-bit. And I'm back in the same hole...Contrary to what you might expect from the names, System32 contains the
>
> My Environment:
>
> * Client PC is Windows 7 64-bit
> * Client code is Perl 64-bit
> * ODBC FB Driver 2.0.2 64-bit dated 7/8/2013
>
> I loaded the ODBC Driver, and its listed in ODBC Data Source
> Administrator. The drivers tab shows "Firebird/Interbas e(d) driver"
> and ODBCFB.DLL as the file.
>
> I checked and this file is in Windows\System32 and Windows\SysWOW64.
> When I run the script I get the "library 'gds32.dll' failed to load"
> error. I tried making a copy of odbcfb.dll and renaming it to gds32.dll
> and fbclient.dll and it causes the Perl client to crash when it tries to
> connect.
*64 bit* libraries and SysWOW64 the *32 bit*, if you mix that up things
won't work. Also make sure you are using the right ODBC Administrator;
the odbcad32.exe in System32 is *64 bit*, the one in SysWOW64 is *32 bit*.
Mark
--
Mark Rotteveel