Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM ODBC Driver » View Thread |
Messages 1 to 9 of 9 total |
Error Code 193 running ODBC setup on Windows Server 2003 64-bit |
Mon, Dec 17 2007 4:40 PM | Permanent Link |
Dave Stephenson | I have been trying to get the DBISAM Ver 3 ODBC drivers running on Windows SErver 2003 64
bit. Installing them was successful (supposedly), but they did not appear in the ODBC Data Source Administrator. I added them manually via regedit and they appeared. But when I try to Add a Data Source I get the error: "The setup routines for the DBISAM 3 ODBC Driver ODBC Driver could not be loaded due to system error code 193." Is there anything I need to do? Thanks Dave |
Tue, Dec 18 2007 9:33 AM | Permanent Link |
Eryk Bottomley | Dave,
> I have been trying to get the DBISAM Ver 3 ODBC drivers running on Windows SErver 2003 64 > bit. Installing them was successful (supposedly), but they did not appear in the ODBC > Data Source Administrator. I added them manually via regedit and they appeared. But when > I try to Add a Data Source I get the error: "The setup routines for the DBISAM 3 ODBC > Driver ODBC Driver could not be loaded due to system error code 193." > > Is there anything I need to do? Try running: "c:\windows\syswow64\odbcad32.exe" ...from the command line. Eryk |
Fri, Jan 4 2008 10:00 AM | Permanent Link |
Chris Holland SEC Solutions Ltd. Team Elevate | I get the same problem with DBISAM version 4 ODBC driver in Windows
Vista 64 bit. The setup completes with no errors but the driver does not appear in the list. Adding the registry entries and then trying to use the driver results in an error 193 Chris Holland Dave Stephenson wrote: > I have been trying to get the DBISAM Ver 3 ODBC drivers running on Windows SErver 2003 64 > bit. Installing them was successful (supposedly), but they did not appear in the ODBC > Data Source Administrator. I added them manually via regedit and they appeared. But when > I try to Add a Data Source I get the error: "The setup routines for the DBISAM 3 ODBC > Driver ODBC Driver could not be loaded due to system error code 193." > > Is there anything I need to do? > > Thanks > > Dave > |
Mon, Jan 7 2008 7:18 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Chris,
<< The setup completes with no errors but the driver does not appear in the list. Adding the registry entries and then trying to use the driver results in an error 193 >> Just to let you know, the setups now are 64-bit aware, so they use the proper installation directories. But, Eryk is correct about running the 32-bit odbcad32.exe application for configuring data sources. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Jan 8 2008 6:49 AM | Permanent Link |
Chris Holland SEC Solutions Ltd. Team Elevate | Hi Tim,
Running the program that Eryk suggests only gets me access to configure the ODBC. I have done this by using RegEdit but the problem is that when I try and connect using the ODBC driver on a 64 bit machine I get an error 193. Chris Holland Tim Young [Elevate Software] wrote: > Chris, > > << The setup completes with no errors but the driver does not appear in the > list. Adding the registry entries and then trying to use the driver results > in an error 193 >> > > Just to let you know, the setups now are 64-bit aware, so they use the > proper installation directories. But, Eryk is correct about running the > 32-bit odbcad32.exe application for configuring data sources. > |
Tue, Jan 8 2008 9:56 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Chris,
<< Running the program that Eryk suggests only gets me access to configure the ODBC. I have done this by using RegEdit but the problem is that when I try and connect using the ODBC driver on a 64 bit machine I get an error 193. >> So, you can configure the ODBC driver okay, but cannot use it in an application ? It sounds like the application is linking against or loading the wrong driver manager, thus resulting in the driver manager not finding/loading the DBISAM ODBC driver. Error 193 simply means that the DBISAM ODBC driver DLL cannot be loaded because it cannot be found. Did you also fix the registry settings for the driver installation under the Wow6432Node ? HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ http://blog.wadewegner.com/PermaLink,guid,9d1ef109-430a-44a6-808b-807695592583.aspx -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Jan 10 2008 6:19 AM | Permanent Link |
Chris Holland SEC Solutions Ltd. Team Elevate | Hi,
Just a quick note for anybody else using Visual Studio that is having this problem. By default VS creates the .exe to run under any platform (x86, x64 and Itanium), so I am assuming that when I ran my program on a 64 bit machine that it was looking for a 64 bit ODBC driver. When I changed the CPU target for my .exe to be "x86" and setup the registry entries under the Wow6432 node it all worked as expected. Chris Holland Tim Young [Elevate Software] wrote: > Chris, > > << Running the program that Eryk suggests only gets me access to configure > the ODBC. I have done this by using RegEdit but the problem is that when I > try and connect using the ODBC driver on a 64 bit machine I get an error > 193. >> > > So, you can configure the ODBC driver okay, but cannot use it in an > application ? It sounds like the application is linking against or loading > the wrong driver manager, thus resulting in the driver manager not > finding/loading the DBISAM ODBC driver. Error 193 simply means that the > DBISAM ODBC driver DLL cannot be loaded because it cannot be found. > > Did you also fix the registry settings for the driver installation under the > Wow6432Node ? > > HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ > > http://blog.wadewegner.com/PermaLink,guid,9d1ef109-430a-44a6-808b-807695592583.aspx > |
Thu, Jan 10 2008 6:00 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Chris,
<< By default VS creates the .exe to run under any platform (x86, x64 and Itanium), so I am assuming that when I ran my program on a 64 bit machine that it was looking for a 64 bit ODBC driver. When I changed the CPU target for my .exe to be "x86" and setup the registry entries under the Wow6432 node it all worked as expected. >> Further to this issue - the next build (4.25 build 8) of DBISAM will use the latest Inno Setup installer with proper 64-bit installation support, so it should create the registry entries, etc. properly. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Jan 11 2008 3:14 AM | Permanent Link |
Chris Holland SEC Solutions Ltd. Team Elevate | Excellent, thanks Tim.
Chris Holland Tim Young [Elevate Software] wrote: > Chris, > > << By default VS creates the .exe to run under any platform (x86, x64 and > Itanium), so I am assuming that when I ran my program on a 64 bit machine > that it was looking for a 64 bit ODBC driver. When I changed the CPU target > for my .exe to be "x86" and setup the registry entries under the Wow6432 > node it all worked as expected. >> > > Further to this issue - the next build (4.25 build 8) of DBISAM will use the > latest Inno Setup installer with proper 64-bit installation support, so it > should create the registry entries, etc. properly. > |
This web page was last updated on Thursday, April 18, 2024 at 10:42 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |