Sql Anywhere 17 Odbc Driver 64-bit Download
Janeth Counter
I am trying to convert data from a client's database that was built using the ASA 8.0 engine. ASA 8 has been out of support since 2008. The software company that created this no longer supports it, so can't provide me with the drivers. I've scoured the web and can't find anything.
I managed to get the installation files for this old software called BailCredit built by a company called SentryLink. I found what I presume to be the ODBC driver in the installation files (dbodbc8.dll) and I've tried manually registering that (Windows Server 2008 R2) but didn't get anywhere. When I try to create a new datasource, the ODBC Data Source Administrator gives me an error.
I wasn't able to find this commercially available anywhere. I happened to be able to get my hands on the installation for the software package that was using SQLAnywhere 8. By installing this, it installed the necessary drivers (but only worked on 32-bit OS).
i have install SQL Anywhere 10, with 32bit enable into a windows server 2008 64bit. when i try to create a ODBC using c:\windows\syswow64\odbcad32.exe to connect, it give me error "Found Server but communication error occured", but i try the same setting using c:\windows\system32\odbcad32.exe, test connection successful.
C:Program Files (x86)SQL Anywhere 10win32>dbping -m -c "DSN=EPETest" -l dbodbc10SQL Anywhere Server Ping Utility Version 10.0.1.3649Loaded ODBC driver dbodbc10Ping server failed -- [Sybase][ODBC Driver][SQL Anywhere]Connection error: Found server but communication error occurred.
What are the values of the DSN "EPETest"? (Note, you can still supply the same connection string when using DBPING -m, it's not necessary to use a DSN parameter here.) It's difficult to check for differences in the connection process when the connection string paramters may not be identically...
C:Program Files (x86)SQL Anywhere 10win32>dbping -m -c "DSN=EPETest" -l dbodbc10 SQL Anywhere Server Ping Utility Version 10.0.1.3649 Loaded ODBC driver dbodbc10 Ping server failed -- [Sybase][ODBC Driver][SQL Anywhere]Connection error: Found server but communication error occurred.
thank you for the reply. i have tried to uninstall and reinstall SQLA many many times with all the different option. i do check on the 32-bit checkbox when i doing installation. but still the same result. maybe you can help me to give me a more detail step for me to troubleshoot? thanks
Well, according to your client log you have been connected to the database server for a while (see 13:04:14 - 13:06:15), so I'm not sure whether this is an setup issue or not. So you are trying to connect locally from the machine the database server is running on (Not sure why shared memory would not work then)?
Forum problems?Maintenance logContact UsTerms of ServicePrivacy PolicyCopyright/Trademark InfoLegal
Powered by SQL Anywhere 17
Disclaimer: Opinions expressed here are those of the poster and do notnecessarily reflect the views of the company.
We have a customer in Saudi Arabia. Given the time difference and their security policies, it is difficult to effect a remote-in with them. I think they are running sqla 10 on a 32 bit server. They want to create a 64 bit odbc driver msi to install on a 64 bit workstation. Normally, I would just have them visit the sqla 10 Deployment directory and create a driver msi. However, since this is a 32 bit sqla on a 32 bit server, I don't think that sqla will offer the 64 bit option. Any ideas/suggestions for this customer?Thanks, Doug.
You need to instead take these files from an existing 64-bit SQL Anywhere installation. If you don't want to create an distribution MSI via the Deployment Wizard from the 64-bit installation as Dietrich/Volker suggests, the command to manually install the ODBC driver is short if you are just copying the files:
In case they also have a v12 64-bit installation available, they could also use that to create a v12 ODBC client MSI with the help of the Deployment Wizard - in general a v12 client should work with a v10 server as well as a v10 client.
Thank you for the great feedback this issue. It's wonderful when feedback on a technical issue is both informative and entertaining. I decided to create an odbc client msi with my 64 bit SQLA 12. I zipped-up the msi and sent it to our customer. Thanks again!
hello Beautiful people as the topic says i want to install IBM INFORMIX ODBC DRIVER 64 Bits version but i cant find it anywhere i even uninstalled my ibm informix odbc driver package from my pc and re-installed it again to check if i missed something to checkmark at the installation process, but even that i can only install the 32 bit version as the picture shows:
its the IBM INFORMIX ODBC DRIVER 64-bit version!!! does anyone knows where can i find it or what to do to install it? i already checked on ibm webpage of course but im open to any suggestion or ideas, thanks!
u.u the second options doeskin seems trusty , my anti-virus prevent it to start when i tried to install it, and the first option just provides the installer i already have ? , i just need the Driver but the only Driver i find is the 32 bits that i already have , thanks anyways Frederico
The SQL Anywhere installer makes changes to the Windows Registry to identify and configure the ODBC driver. If you are building an installation program for your end users, you should make the same registry settings.
The simplest way to do this is to use the self-registering capability of the ODBC driver. You use the regsvr32 utility on Windows or the regsvrce utility on Windows Mobile. Note that for 64-bit versions of Windows, you can register both the 64-bit and 32-bit versions of the ODBC driver. By using the self-registering feature of the ODBC driver, you are ensured that the proper registry entries are created. To register the 32-bit and 64-bit versions of the ODBC driver, open up a command prompt and issue the following commands.
Our Powerbuilder application uses the SQL Anywhere database through an 32-bit ODBC setting. In the past we rarely had more than 20-25 users and were happy just to install the SQL Anywhere network client from a SQL Anywhere CD setup, but now we are getting into deploying many more, and this is becoming unfeasible.
We would like to copy these (and if necessary, any other files) just in a subfolder of our application, say C:\OurSystem\Drivers, as a part of a deployment to the new client, but what other steps do we need to carry out regarding registry (or otherwise) to make sure that we can open ODBC Administrator and create an ODBC Data source?
It's possible the issue is related to SQL Anywhere 11 and Windows 8, since SQL Anywhere 11 is not supported on this OS. Does the same process work with v16? What's the complex looking error look like?
I should have made a screenshot of the error message, I have no access to it until Monday, but it actually could be what Mikel said below, that I just ran the 64-bit one, and I should have made sure that I ran regsvr32.exe from C:\Windows\SysWOW64\. I'll check on Monday.
Great. Just in case, we'll copy in all the files from the link Mikel provided. You have already answered the main thing - that we need to run regsvr32 on dbodbc11.dll only, and that this will stuff the key values needed into the registry.
* NOTE: There are several files that you are deploying which are not related to the ODBC driver. For example, rteng11.lic, dblib11.dll, and dbctrs11.dll are engine deployment files which are not needed for a client only install.
and is likely the result of running without administrative level authority and dbelevate11.exe not deployed or found by dbodbc11.dll during the registration process. You can either deploy that file (recommended) or ensure that you are running with elevated administrator authority. This is generally done from a shortcut by selecting "Run as Administrator" from the popup menu for the shortcut or checking that option in the Advanced settings for the shortcut (select properties from the shortcut popup menu.
Using the (64-bit) ODBC Administrator, I can create system DSNs and they test out perfectly. (From my test Access database, I can use these DSNs to pull data from SQL Server and from SQL Anywhere.) Since this is working, I'm pretty confident that my drivers are all 64-bit and that everything is happy.
When I try to create a new data source in the ColdFusion Administrator and I use, the "ODBC Socket" option, I am presented with a drop-down list of my 64-bit ODBC system DSNs (good!), but whenever I select one and save, I invariably get an "architecture mismatch" error like below:
I am well aware that "architecture mismatch" errors mean that you're trying to mix 32-bit drivers with a 64-bit application (or vice-versa), but I'm pretty sure that everything in my environment is 64-bit.
As a further test, I created a few 32-bit ODBC system DSNs and the ColdFusion Administrator does not present them as options in the drop-down list of ODBC DSNs (good!). So, it seems like the Administrator is smart enough to show only the 64-bit DSNs, but whenever you try to connect to one, it gets confused and kicks up an "architecture mismatch" error.
So is there any obvious configuration error here? Is there a 32-bit subcomponent to ColdFusion (JDBC, etc.) that's confusing things? (I ran the ColdFusion_9_WWE_win64.exe setup downloaded from Adobe's site.) Is 64-bit ColdFusion ready for prime time? Any suggestions would be greatly appreciated. Thanks, Joe
There just might be. As far as I recall, these 64 bit drivers, particualarly the 64 bit Access driver, did not exist when ColdFusion 64 bit came out. You may be using a piece of ColdFusion that the Adobe engineers had nothing to test against when they where building the thing.
c80f0f1006