Odbc Failed Error 3146
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 22 Oct 2016 08:38:30 GMT by s_wx1157 (squid/3.5.20)
Board Games Movies Role-Playing Games TV Series Videogames Italiano ODBC Call Failed - Error 3151 on Windows 7 64-bit and how to fix it August 26, 2015August 26, 2015 Ryan Networking & Web, Operating Systems, System Configuration Table
Run Time Error 3146 Odbc Call Failed Mysql
of ContentsThe ProblemThe AnalisysODBC Administrator (32-bit)ODBC Administrator (64-bit)The Fix If you stumbled upon this issue, chances
Odbc Call Failed Access 2013
are you're (re)installing an old software client on a new-or-newly-updated Windows 7 64-bit system. That program - often an archive/administrative/management service client or a similar home-made piece of software - uses a persistent ODBC connection to a local or remote DB via an ODBC DSN interface defined at user or system level using the http://answers.microsoft.com/en-us/msoffice/forum/msoffice_access-mso_other/access-2007-odbc-call-failed-error-3146-only-on/27172fb8-958f-4222-be8e-9083541c8891 Windows ODBC Administrator tool. The Problem The aforemetioned client can't find the ODBC Data Source entry, therefore showing an error pop-up containing the following: ODBC Call Failed - Error 3151 Or, depending on the ODBC driver installed: ODBC Connection Failed - Error 3146 First thing we need to do is to check if the latest version of the Windows ODBC is properly installed and if a proper Data Source pointing to the DB we need http://www.ryadel.com/en/odbc-call-failed-error-3151-on-windows-7-64-bit-and-how-to-fix-it/ to connect has been set: you can check both of these by opening the Windows Control Panel and navigate through Administrative Tools -> ODBC Data Source Administrator. If there's something missing there, fix that and check again, otherwise keep reading. The Analisys This specific issue is mostly related to how Windows 7 and above handles ODBC connections. Starting from Win7 the OS contains two different ODBC Data Source Administration tool executables: the 32-bit one and the 64-bit one. You can find them in the following folders, as explained in a note of this official KB article: ODBC Administrator (32-bit) c:\windows\sysWOW64\odbcad32.exe 1 c:\windows\sysWOW64\odbcad32.exe ODBC Administrator (64-bit) c:\windows\system32\odbcad32.exe 1 c:\windows\system32\odbcad32.exe Which one should we use? It obviously depends on the Data Source we need to set-up. If your client supports a 64-bit connection driver you will go with the x64 version, otherwise you need to use the 32-bit one. If you're experiencing the Error 3151 problem and your ODBC connection works, chances are you're doing the right thing while using the wrong tool, i/e the 64-bit ODBC Administrator instead of the 32-bit one. The Fix Needless to say, the problem can be fixed by launching the proper ODBC Administrator tool, which - if you're here - often is the 32-bit one. The fact that the latest versions of Windows are shipping two di
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings http://stackoverflow.com/questions/730414/determine-real-cause-of-odbc-failure-error-3146-with-ms-access and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation https://bugs.mysql.com/bug.php?id=76136 Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; error 3146 it only takes a minute: Sign up Determine real cause of ODBC failure (error 3146) with ms-access? up vote 6 down vote favorite 2 My client is using Access as a front end to a SQL Server database. They recently started getting ODBC - 3146 errors from time to time when running some reports. From what I can tell, this odbc call failed is just a generic ODBC call failed error. I've tried sticking some error handling in the VB script that is launching the reports, but I am not having any luck getting extra error information. Code looks a bit like this. Public Function RunReports() On Error GoTo MyErrorTrap DoCmd.OpenReport "blah", acViewPreview DoCmd.Close DoCmd.OpenReport "foo", acViewPreview DoCmd.Close Exit_function: Exit Function MyErrorTrap: Dim errX As DAO.Error Dim MyError As Error If Errors.Count > 1 'This always seems to be 0, so no help For Each errX In DAO.Errors 'These are empty even if dont check for Errors.Count Debug.Print "ODBC Error" Debug.Print errX.Number Debug.Print errX.Description Next errX Else Debug.Print "VBA Error" Debug.Print Err.Number Debug.Print Err.Description End If 'Also have tried checking DBEngine.Errors, but this is empty too End Function I've also enabled tracing on the ODBC side, but that has bogged things down way too much, and I am so far unable to recreate the ODBC error. I am completely open for suggestions on how to diagnose this. vba ms-access vbscript odbc share|improve this question edited Jun 16 '14 at 20:23 S
Updates: Status: Can't repeat Impact on me: None Category:Connector / ODBC Severity:S2 (Serious) Version:5.1.13 OS:Microsoft Windows (Windows 7/8.1) Assigned to: Tags: 5.3.4, ODBC 5.1.13 View Add Comment Files Developer Edit Submission View Progress Log Contributions [3 Mar 2015 20:02] Mihai Preda Description: When using MS Access as front end for MySQL via odbc connector versions 5.1.13 and 5.3.4, the odbc call fails with the error listed in the synopsis. When I click on the debug button I get the following line highlighted: sql = 'update table set field = 'value'; How to repeat: This can be replicated if running Microsoft DAO 3.6 Object Library and MS Access 9.0 Object Library. Have not tried to replicate using ADO or RDO code. Suggested fix: Odbc 5.1.12 and prior seem to work fine with DAO object libraries. [3 Mar 2015 20:55] Miguel Solorzano Thank you for the bug report. Same error reported on https://bugs.mysql.com/bug.php?id=57256. Looks like duplicate?. Thanks. [4 Mar 2015 16:13] Mihai Preda Thank you for pointing that our Miguel, but I don't think it's the same issue since we haven't had any problems with ODBC calls failing until ODBC Connector versions 5.1.13 and 5.3.4. In fact our DSN accepts log in credentials and I think the DSN is created. It's the sql update, delete and insert functions that fail from what I can tell. [10 Mar 2015 11:32] Chiranjeevi Battula Hello Mihai Preda, Thank you for your feedback. Could you please provide us VB code sample, create table statements and ODBC trace to confirm this issue at our end? Thanks, Chiranjeevi. [23 Mar 2015 3:38] Eric Black Hi, I am using MS access 2010 with mysql database Software version: 5.5.42-cll - MySQL Community Server (GPL) Protocol version: 10 Server charset: UTF-8 Unicode (utf8) With ODBC 5.02.07 or 5.03.04, on querying the database, MS Access returns ODBC call failed. However, ODBC 5.1.11 works. I would use 5.1.11 but the issue is that it fails with long table names and the database I am connecting to has long table names. your help is much appreciated. [23 Mar 2015 6:41] Chiranjeevi Battula Hello Eric Black, Thank you for the bug report. This is duplicate of Bug #65200 which is fixed in 5.2 version. If yo