Microsoft Access Error Code 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 run time error 3151 odbc connection failed access 26, 2015 Ryan Networking & Web, Operating Systems, System Configuration Table
Runtime Error 3151 Odbc Connection Failed Access 2010
of ContentsThe ProblemThe AnalisysODBC Administrator (32-bit)ODBC Administrator (64-bit)The Fix If you stumbled upon this issue, chances are you're (re)installing an
Run Time Error 3151 Odbc Connection Failed Oracle
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
Error 3151 Odbc Connection Failed Windows 7
persistent ODBC connection to a local or remote DB via an ODBC DSN 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: runtime error 3151 odbc connection failed access 2013 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 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
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 20 Oct 2016 14:02:07 GMT by s_wx1196 (squid/3.5.20)
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack http://stackoverflow.com/questions/5583256/odbc-connection-failed-3151-ms-access-sql-server-2008 Overflow the company Business Learn more about hiring developers or posting ads with us http://www.access-programmers.co.uk/forums/showthread.php?t=240995 Stack Overflow Questions Jobs Documentation 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; it only takes a minute: Sign up ODBC Connection Failed #3151 MS Access --> SQL Server 2008 up vote 1 down vote favorite error 3151 I have an MS Access application that links to a SQL Server 2008 db for all of its data. For years, it has worked fine when the SQL Server was on Win2008 Standard 64-bit SP2 and SQL Server 2008 v10.0.4. I recently moved the back-end SQL db to a newer server (Win2008 R2 Standard 64-bit and SQL v10.50.1600). After the move, everything on the application worked just fine as expected, no error 3151 odbc issues. However, we have a month-end process that generates relatively large reports (300-500 pages) which uncovered an issue that we don't normally see in our day-to-day processing. My report is based on a pass-through query. The query runs almost instantaneously and produces 8000 rows. I can preview the query and quickly navigate to the end of the RS to see the 8000'th row. No problem. If I pull up the report that's based on that query, I can see that there are 350 pages and I can navigate page-by-page through the report with no problem. I can even type in a page number and jump to page 50, 100, 150, etc. with no problem. Note, there is no processing/code/logic happening on any fired events on the report - just displaying and formatting the data. HERE IS WHERE THE PROBLEM OCCURS: If I preview the report and try to jump to the last page from the first page, it'll sit and think for a while (38 seconds to be exact) and then throw Error #3151 ODBC Connection to [DNS Name] Failed. If I simply update the connect string on the pass-through query to point it back to the "older" SQL Server and run the same thing, it works just fine. I've t
Links Social Groups Pictures & Albums Members List Calendar Search Forums Show Threads Show Posts Tag Search Advanced Search Find All Thanked Posts Go to Page... Thread Tools Rating: Display Modes 01-29-2013, 04:09 AM #1 Insane_ai Newly Registered User Join Date: Mar 2009 Location: Cleveland, OH USA Posts: 161 Thanks: 1 Thanked 14 Times in 11 Posts Oracle ODBC Connection Error 3151 The following code works when employed on Windows XP clients. I am upgrading to Windows 7 Professional 64 bit. I have verified the ODBC connection is working properly through the ODBC management. I get Error 3151 Private Sub Form_Load() Dim DB As DAO.Database Dim TDF As DAO.TableDef 'Refresh Databse Link Set DB = CurrentDb() Set TDF = DB.TableDefs("EWVPD_PRODUCT") TDF.Connect = "ODBC;DSN=[DSN_NAME];UID=[USER];PWD=[Password]" TDF.RefreshLink DoCmd.OpenForm "Main", acNormal DoCmd.Close acForm, Me.Name End Sub Error Message: Run-time error '3151' ODBC connection to '[DSN_NAME] failed The code in RED is being flagged for the error. The file's location is in the trusted locations via registry edits. The idea of this code is to make a connection to the Oracle database in the background when the application opens to avoid password issues. Any advice on the configuration or re-coding of this is greatly appreciated. I suspect I will have to add code to compare the host operating system so I use the proper method depending on the client using the application. __________________ There's nothing like trouble shooting to find out how much I have yet to learn. Last edited by Insane_ai; 01-29-2013 at 04:38 AM. Reason: spelling error(s) Insane_ai View Public Profile Find More Posts by Insane_ai 01-29-2013, 04:38 AM #2 mdlueck Sr. Application Developer Join Date: Jun 2011 Posts: 2,584 Thanks: 110 Thanked 293 Times in 282 Posts Re: Oracle ODBC Connection Error 3151 Quote: Originally Posted by Insane_ai The following code works when employed on Windows XP clients. I am upgrading to Windows 7 Profes