Access 2010 Run Time Error 3151
Contents |
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 runtime error 3151 odbc connection failed access 2010 posts,Page 1 of 3123»»» Getting run-time error 3151 ODBC connection to ... failed Rate Topic
Run Time Error 3151 Odbc Connection Failed Oracle
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, microsoft visual basic runtime error 3151 odbc connection failed 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 error 3151 odbc connection failed windows 7 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
Runtime Error 3151 Odbc Connection Failed Access 2013
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
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 02-10-2009, 09:53 AM #1 odbc – connection to
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 Overflow the company Business Learn more about hiring developers or posting ads with us http://stackoverflow.com/questions/5583256/odbc-connection-failed-3151-ms-access-sql-server-2008 Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community http://www.ryadel.com/en/odbc-call-failed-error-3151-on-windows-7-64-bit-and-how-to-fix-it/ Stack Overflow is a community of 4.7 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 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 error 3151 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 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 time error 3151 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 tried adjusting the connect string to use IP address instead of DNS name, no luck. This is a process that's worked for years with no problem so I know the client-side logic is sound. Any thoughts or suggestions? sql-server ms-access odbc share|improve this question edited Apr 7 '11 at 15:11 Tony Toews 7,02511324 asked Apr 7 '11 at 15:04 lunchroom 6112 Is there anything in the SQL Errorlog? What about the Event Logs? (Server side and Client). When you jump to page 349 and th
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 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 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 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 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