Below are the steps followed to load Sybase ASE ODBC Driver on Windows 7:
Tried to run the exe file odbcad32.exe from directory C:\Windows\SysWOW64
Gave the network address on ODBC Sybase ASE Driver Setup page and clicked on TestConnect button. Logon to Sybase ASE window opened.
When I gave the login details on the Logon to Sybase ASE window, the following warning message popped up:
[MERANT][ODBC Sybase ASE driver]
Unable to load communication module. Netlib Driver has not been correctly installed.
If anyone has faced such issue and know the resolution, please help.
That sounds like the old MERANT driver was incompletely or incorrectly installed.
You could try a driver from a different vendor, like my employer's Single-Tier "Lite" Edition ODBC Driver for Sybase & Microsoft SQL Server. (The same driver supports connections to all versions of Microsoft SQL Server and Sybase ASE, and most versions of SQL Anywhere/Sybase ASA.) This driver has no external dependencies, and both 32-bit and 64-bit variants have been proven to work on Windows 7.
Related
System specs: 64-bit OS (Win7), 64-bit R (3.3.3), 32-bit MS Access (2016).
I have data in a 32-bit .accdb file and I want to read it into R. I tried this:
con <- odbc::dbConnect(odbc::odbc(),
dsn="MS Access Database")
but saw the following error:
Error: nanodbc/nanodbc.cpp:950: IM014: [Microsoft][ODBC Driver Manager]
The specified DSN contains an architecture mismatch between the Driver and Application
Web search indicated that the bit difference between R and the database is the culprit. The default ODBC manager in Windows doesn't include drivers for MS Access (or rather, it seems to, but attempting to manage them using that tool gives you an architecture error). Following other advice, I used the ODBC manager for 32-bit programs (c:\windows\sysWOW64\odbcad32.exe) to create a new DSN with a new name for MS Access files, and then called this DSN:
con <- odbc::dbConnect(odbc::odbc(),
dsn="MSAccess32")
I got the same error, however, and suspect there is something I don't understand about what this error means. Is there a known workaround for the problem?
The access file itself knows nothing about bitness, its only about the client application and the bitness of the odbc driver:
If your R is 64 bit, you need the 64bit ODBC driver for access and therefore also use the odbc manager for 64bit, which is C:\Windows\System32\odbcad32.exe (in Win7 64bit).
While if your R is 32bit, you need the 32bit ODBC driver, located at C:\Windows\SysWOW64\odbcad32.exe.
You can download the required Access Database Engine 2010 Redistributable from here: https://www.microsoft.com/en-US/download/details.aspx?id=13255
So, download the 64 bit Access Database driver, create a 64bit DSN entry and you should be fine.
OS: Microsoft Windows Server 2008 R2 Enterprise - 64-bit - En.Us
DBMS: Microsoft SQL Server 2008 R2 Standard - Windows - 64-bit - En.Us
ODBC Driver: Progress OpenEdge 10.2B - Windows - 32-bit - En.Us
I don't have the related ODBC Driver in 64-bit version.
Do I have options to connect, to the Progress Database, using Query, or Linked Server? If I have, what are my options?
Thank you all!!!
The Progress ODBC drivers can be downloaded from the Progress site. Log in with your ID on http://www.progress.com/esd/
Contact support if you can't find them.
There's also a product called "Pro2" replication that can "almost live" replicate from Progress to for instance SQL server if you have that demand. It might only be offered from 11.X and forward, I'm unsure about that.
https://www.progress.com/openedge/features/openedge-pro2/
If you were to download one of the 11x 64bit Client Access bundles, these will quite happily connect to a 32bit 10.2b database.
http://knowledgebase.progress.com/articles/Article/P88405
You do have options. Fundamentally, you can use our Multi-Tier ODBC Drivers for Progress (versions 6.x to 10.x) to connect a 64-Bit ODBC Compliant application to a 32-Bit Progress RDBMS. This 64-Bit client to 32-Bit server bridging is achieved as a result of the RDBMS-independent communications layer used by these drivers.
I have created an ODBC connection in PB10 Data Source and once I attempt to connect, below stop sign error occurs. Any idea on how to resolve this kind of connection error?
Error : ODBC Driver Manager The specified DSN contains an architecture mismatch between the Driver and Application
Also, you could try to create the 32-bit ODBC in the 64-bit Operating System.
Here's the exe you need to execute to create 32-bit ODBC in a 64-bit Operating System.
c:\windows\syswow64\odbcad32.exe
Use odbcad32.exe under C:\Windows\SysWOW64\ to configure the DSN.
I suspect that you are on 64-bit system and that the DSN you try to connect to uses a 64-bit odbc driver. PowerBuilder applications are 32-bit and can only use 32-bit odbc drivers.
We have an ASP.net web-app running in the following environment -
Existing Environment
Operating System : Windows 2003
Framework : .NET Framework : 2.0
IIS : 6.0
Database : Oracle 10g
We wished to upgrade this to the following environment
Present Environment
Operating System : Windows 2008 R2 x64
Framework : .NET Framework : 2.0
IIS : 7.0
Database : Oracle 11g
While doing so, we face the below issue
ODBC Connection Issue on Windows Server 2008 R2 64 bit
ODBC connection could not be established from the ASP.net Web Application in Windows Server 2008 R2.
Application throws an Error : ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.
Connection String :
<add name="ConnectionString" connectionString="Driver=Oracle in XE;Dsn=winerenew;uid=winere;pwd=winere;dbq=XE;dba=W;apa=T;exc=F;fen=T;qto=T;frc=10;fdl=10;lob=T;rst=T;btd=F;bam=IfAllSuccessful;num=NLS;dpm=F;mts=T;mdi=F;csr=F;fwc=F;fbs=64000;tlo=O" providerName="System.Data.Odbc"/>
Application works perfectly in windows 2008 x86.
We have tried the following ways to resolve this issue in Windows Server 2008 x64,
1) Enabled the 32-Bit Application in the Application Pool (IIS 7)
2) Executed the ODBC 32 Bit driver with the following command C:\Windows\SysWOW64\odbcad32.exe
3) Installed the oracle 64-bit ODBC driver.
The above methods doesn't seem to solve this issue. Could anyone tell me the problem behind it and the solution to solve this issue?
Set default ODBC driver.
From the Windows Start menu, click Control Panel > Administrative Tools > Data Source (ODBC).
Open the System DSN tab.
Select ODBC_NAME and click Configure.
Normally system use 32 bit ODBC as default. but if you dont have 32bit then configure 64bit and set as default.
For me it's working.
I build VS application in 64bit and published on IIS by setting default ODBC driver. O
If you have working DNS then you can enable tracing ODBC calls from odbcad32.exe. Then test Oracle connection from any ODBC editor/tool (I often test it with simple Python program that uses odbc module). Such tracing will create file with a successful attempt to connect to database. After connecting do database close program, stop tracing and rename trace file.
Now you will have to create such tracing for your application: enable tracing, start your program, try to connect do database, close program, stop tracing. You have two files with attempts to connect to database via ODBC: one successful and one with failure. Compare them.
why can i use myob Odbc direct driver v7my with windows 7, i have tried using the same odbc driver with XP and vista and it works fine.
please help me tnx.
If you're running a 64bit version of Windows, then you need to make sure you run the 32-bit version of the ODBC control panel to get access.
C:\Windows\SysWOW64\odbcad32.exe
However, need a bit more detail to find out if that's your problem.