- #Odbc manager not working windows 10 64 Bit
- #Odbc manager not working windows 10 driver
- #Odbc manager not working windows 10 32 bit
- #Odbc manager not working windows 10 software
Towards the bottom of the first paragraph it says that on a 64 bit system the 64 bit drivers are held at a certain registry location.
#Odbc manager not working windows 10 32 bit
Reading various posts online I would expect the 32 bit version to refer to syswow64 files and the 64 bit be populated with the system32 ones if they were there, which they are not. The 32 bit version is populated including a SQL Server whereas the 64 bit version only has SQL Server. For the 64 bit version the only entry is SQL Server with the same version.
However, in User Data Sources both sets of files are flagged as 32 bit platform and in About all the ODBC Core Components for both versions are pointing to system32 location which is the 64 bit.įor the Drivers tab the 32 bit version is fully populated including SQL Server, most having a version no. User DSN, System DSN (empty), File DSN, Tracing and About appear to be the same in both. When you open up both versions to look at the Administrators, the data appears to be identical for both in some cases. system 32 for the 64 bit and SySwow64 for the 32 bit.
#Odbc manager not working windows 10 software
The Control Panel shows the two entries for this software as it should for a 64 bit system and when you drill down to General under Properties it shows the correct shortcuts for both versions, i.e. So, depending on what sort of datasource you need (for 64-bit or 32-bit access) you have to use either of these two: For 64-bit: %SystemRoot%\system32\odbcad32.exe (or simply use the shortcut in "Control Panel" -> "Administrative Tools") For 32-bit: %SystemRoot%\SysWOW64\odbcad32.exe (Note that both files have the same name "odbcad32.exe", even the 64-bit version - the difference in the two files is their location, where again it is confusing that the tool for the 32-bit datasources is in a folder that is called "SysWOW64".) For users of 32-bit LISTSERV, the solution is to re-create the datasource as a 32-bit datasource using the "hidden" 32-bit ODBC tool (which, as noted above, is no longer hidden as of Windows Server 2016).I suspect that something is not correct concerning the configuration of ODBC. The 32-bit version is in a special sub-folder of the Windows folder. Unfortunately, the shortcut to the tool which you can find at the usual location in "Control Panel" -> "Administrative Tools" points to the 64-bit version of the tool without even a hint that there also is a different version. That is, if a 32-bit program needs to access the datasource, you have to create this datasource using the 32-bit version of the tool. When creating a datasource you have to take care to use the correct tool in respect to which client programs will be using the datasource. On an 圆4 system there are two versions of the "ODBC Datasource Administrator" tool: One version for 64-bit and one version for 32-bit.
Since L-Soft no longer provides a 32-bit version of LISTSERV, it is unlikely that users of the current supported version will notice this issue but since Windows Server 2016 provides easy access to BOTH the 32- and 64-bit ODBC administrators, we're leaving it in for now. NOTE: This FAQ is really more aimed at the 32-bit version of LISTSERV running under a 64-bit version of Windows. We are using the same ODBC_* settings that worked on our 32-bit server (or we have otherwise correctly set up LISTSERV to talk to ODBC).
#Odbc manager not working windows 10 driver
> IM002/0: Data source name not found and no default driver specified > 08003/0: Connection not open 18:18:27 > Error X'0100003B' opening DBMS list Severity: Error 18:18:27 -> Facility: DBMS interface 18:18:27 -> Abstract: SQL error 18:18:27 Connecting to ODBC data source MYDBMS. When attempting to use ODBC to connect to a database under Windows 圆4, the following error appears in the log:
0 kommentar(er)
