Odbc Error 3146 Call Failed
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 22 Oct 2016 08:59:15 GMT by s_wx1011 (squid/3.5.20)
first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start odbc call failed access 2013 viewing messages, select the forum that you want to visit from the selection below. Results 1 to 5 of 5 Thread: Error (3146) ODBC --call failed Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 02-08-11,15:10 #1 Stium View Profile View Forum Posts Registered User Join Date Jan 2011 Posts 19 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 Unanswered: Error (3146) ODBC --call failed I'm got a situation where I run a set of reports for different areas. Most of the areas work but some I get this error. Error (3146) ODBC --call failed. [Oracle][OCBC][Ora]ORA-00600: internal error code, arguments.In this case I'm having access call an Oracle database. Suggestions that I found would include refreshing the link or dropping the table and adding it again. I've tried http://www.dbforums.com/showthread.php?1664131-Error-(3146)-ODBC-call-failed both. This isn't a single machine issue, it is happening network wide. Any suggestions? Reply With Quote 02-10-11,12:34 #2 pkstormy View Profile View Forum Posts Moderator Join Date Dec 2004 Location Madison, WI Posts 3,926 I might try re-creating the ODBC DSN. Also make sure that you don't have an ODBC DSN connecting to the same db by another ODBC DSN name. You want all users/computers that are connecting to the db to have the EXACT same ODBC DSN name. A mispelled (or spelled slightly different) ODBC DSN for one user/computer can cause problems for others. (but this usually causes problems for some users and not others). If that isn't the problem, I might try running any dbcc checkdb type commands on the Oracle server against the db (I'm not sure what the Oracle commands are to check the db.) This seems more likely since you said it's for all users. Lastly, when you link the tables, make sure the "Save Password" check box is checked when linking (although this wouldn't cause the problems you noted.) If all else fails, you could also try creating a File DSN versus a System DSN. Expert Database Programming MSAccess since 1.0, SQL Server since 6.5, Vis
the Driver and Application If you go to the ODBC Data Source Administrator, you will http://www.gfixpc.com/2014/01/sql-microsoft-access-error-3146-odbc.html see the windows like this There is only one https://bugs.mysql.com/bug.php?id=76136 component exit, other are gone Solution: S1: That's because of your OS is 64bits Go to Control Panel -> ODBC Data Source Administrator, right click -> Properties S2: 1. Download and run AccessDatabaseEngine_x64.exe (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c06b8369-60dd-4b64-a44b-84b371ede16d&displaylang=en) 2. Change the connection string error 3146 : EX: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=xxxx;Driver={Microsoft Access Driver (*.mdb)}; replaced to be Provider=Microsoft.Jet.OLEDB.4.0;Data Source=xxxx;Driver={Microsoft Access Driver (*.mdb, *.accdb)}; Some Server Connection Strings don't need add "*.accdb", I don't know why, but for in case, add it Reactions: #Office #SQL 1 comment Anonymous said... odbc call failed Thx August 26, 2014 Post a Comment Newer Post Older Post Home Newer Newer Post Older Older Post Subscribe to: Post Comments (Atom) Search This Blog Loading... Blog Archive 2016 (5) July (1) June (1) May (1) March (1) February (1) 2015 (15) October (2) September (4) July (1) June (2) May (2) April (2) March (1) January (1) 2014 (42) December (2) November (4) October (4) September (3) August (4) July (13) June (5) May (1) April (1) March (1) January (4) [SQL]MSACCESS.EXE error - MSVCR90.dll [Life]Honesty is the Key for the career and the li... [Hyper-V]Mapping a USB device on VMs [SQL] Microsoft Access Error "3146 ODBC-Call Faile... 2013 (34) December (4) November (2) October (7) September (16) August (2) April (1) January (2) 2010 (5) October (2) August (1) July (2) Popular Tags [SQL] (12) [SQL]CDC (6) [SQL]Concurrency (9) [SQL]Failover (3) [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 O