Microsoft Access Error 3151
Contents |
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, runtime error 3151 odbc connection failed access 2010 Operating Systems, System Configuration Table of ContentsThe ProblemThe AnalisysODBC Administrator (32-bit)ODBC Administrator (64-bit)The Fix If
Run Time Error 3151 Odbc Connection Failed Oracle
you stumbled upon this issue, chances are you're (re)installing an old software client on a new-or-newly-updated Windows 7 64-bit error 3151 odbc connection failed windows 7 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 runtime error 3151 odbc connection failed access 2013 interface defined at user or system level using the 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
Microsoft Visual Basic Runtime Error 3151 Odbc Connection Failed
the Windows ODBC is properly installed and if a proper Data Source pointing to the DB we need 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 down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 16:18:24 GMT by s_wx1126 (squid/3.5.20)
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: MS Access Runtime 2010 ODBC call to Oracle not working Microsoft Office > Office 2010 - IT Pro General Discussions https://social.technet.microsoft.com/Forums/office/en-US/8c416503-c07c-4736-b93d-0d7a13ac6a9e/ms-access-runtime-2010-odbc-call-to-oracle-not-working?forum=officeitproprevious Question 0 Sign in to vote I have a MS Access 2010 applicaton http://www.sqlservercentral.com/Forums/Topic446169-5-1.aspx that links through an ODBC call to Oracle read data from a table. I have been using this call from MS Access (2000, 2003) to Oracle to read the data for several years. In Windows XP. When it is run under Windows 7 using the full version of MS Access 2010 using the ODBC connection error 3151 it works fine. When it is run on another machine under Windows 7 that has only the MS Access 2010 runtime installed through the ODBC connection it returns error 3151 - Cannot connect. I tried, ADO as well as DAO with DNS and DNS less connection. No results. Does anybody knows why it does not function under Access 2010 runtime and does function under Access 2010 full version? Thursday, error 3151 odbc November 03, 2011 7:25 PM Reply | Quote Answers 0 Sign in to vote Hello Jim, It’s still unclear what version of Oracle you are running. FYI, the Microsoft ODBC driver for Oracle was last developed for Oracle 7 and tested for basic functionality against Oracle 8. Beyond those versions you should be using the driver provided by Oracle. Do you receive the same errors when using the Oracle driver with the runtime? I have found that you have another thread discussing this same issue on the msdn forum. http://social.msdn.microsoft.com/Forums/en-US/accessdev/thread/620d70f1-5bca-4a51-9afc-10fcba4e866e/ I have discussed this with Sharon and we’ve decided that she will continue working with you on that thread. Please continue your posts on that thread. Regards, Dennis Edited by Dennis Wi - MSFTMicrosoft employee Friday, November 18, 2011 3:08 PM Marked as answer by Rex ZhangModerator Wednesday, December 07, 2011 2:19 AM Friday, November 18, 2011 3:07 PM Reply | Quote All replies 0 Sign in to vote Hello factsjim, Thank you for your post. This is a quick note to let you know that we are performing research on this issue. Sincerely Rex Zhang Monday, November 07, 2011 4:40 AM Reply | Quote Mo
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Administration » Getting run-time error 3151 ODBC connection... 21 posts,Page 1 of 3123»»» Getting run-time error 3151 ODBC connection to ... failed Rate Topic Display Mode Topic Options Author Message pete.doylepete.doyle Posted Tuesday, January 22, 2008 5:12 PM Forum Newbie Group: General Forum Members Last Login: Monday, January 28, 2008 4:02 PM Points: 8, Visits: 17 Hi - hope someone can help.I've inherited the maintenance and support of a SQL Server 2000 database with an Access 2000 based front-end, running on an SBS 2003 server. All worked fine up until yesterday when trying to login using the usual username/password gives the above 3151 error. The line in the VB which generates this is: Set rstRoles = sfdb.OpenRecordset("Roles", dbOpenDynaset, dbSeeChanges)which is opening a simple table of roles to check which level the given user is at. Two things:1 I've noticed the transaction log is huge (12 GB) and had just run out of space to grow, but having freed up plenty more disk space, I still get the error2 I can open the database in admin mode and view the tables as normal. Just can't run the front end which the users need.I noticed one post which recommended running the linked tables utlility, which I've done but no difference.Any thoughts or suggestions welcome.:) Post #446169 Minaz AminMinaz Amin Posted Tuesday, January 22, 2008 11:22 PM Mr or Mrs. 500 Group: General Forum Members Last Login: Thursday, September 10, 2015 1:24 AM Points: 580, Visits: 1,750 Is it possible to post the SQL Server error message. Please go to the LOG folder of the SQL Server and read the error log without any extension. "More Green More Oxygen !! Plant a tree today" Post #446246 pete.doylepete.doyle Posted Wednesday, January 23, 2008 12:46 AM Forum Newbie Group: General Forum Members Last Login: Monday, January 28, 2008 4:02 PM Points: 8, Visits: 17 Hi - thanks for the speedy response - I really appreciate it.I've extracted the error message plus the contents of the last 2 error logs into the attached Word document. I can't see anything wrong, but hopefully you might!!ThanksPete Post Attachments SQL Screens.doc (68 views, 106.00 KB) Post #446265 Minaz AminMinaz Amin Posted Wednesday, January 23, 2008 1:53 AM Mr or Mrs. 500 Group: General Forum Members Last Login: Thursday, September 10, 2015 1:24 AM Points: 580, Visits: 1,