Access Error Number 3151
Contents |
soon) Ruby (coming soon) Getting Started Code Samples Resources Patterns and Practices App Registration Tool Events Podcasts Training API Sandbox Videos Documentation Office Add-ins Office Add-in Availability Office Add-ins Changelog Microsoft Graph API Office 365 Connectors access error 3151 odbc connection to failed Office 365 REST APIs SharePoint Add-ins Office UI Fabric Submit to the Office Store
Microsoft Access Error 3151
All Documentation https://www.yammer.com/ http://feeds.feedburner.com/office/fmNx Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My
Ms Access Error 3151
Forums Asked by: ODBC Call Failed - Error 3151 Microsoft Office for Developers > Access for Developers Question 0 Sign in to vote We have an Access database migrated from Access 97 to Acces 2007
Access Runtime Error 3151
with some linked tables to an SQL Server 2008 database. We are using a File DSN in the ODBC Administrator. Connection tests work fine there. In fact, we have a main form in the Access 2007 application that shows the data always correctly. The problem appears when we execute a task that makes the following call: Dim dbs As Database Dim rstAppend As Recordset Set dbs = CurrentDb Set rstAppend = error 3151 odbc connection failed windows 7 dbs.OpenRecordset(strAccessTable, dbOpenDynaset, dbSeeChanges) OpenRecordset throws the error number 3151 and occurs randomly but it appears quite frequently. It's sporadic. When we don't get the error, the task works fine. It not happens always, mosty we're fine. When it happens it happens for all subsequent tasks tried. We have to close and reopen the Access database and pray to the good Lord that it works. 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 runtime error 3151 odbc connection failed access 2010 or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x run time error 3151 odbc connection failed oracle Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it microsoft visual basic runtime error 3151 odbc connection failed 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 https://social.msdn.microsoft.com/Forums/office/en-US/dc8b91f0-d176-4ccb-9282-134fa17a2e9e/odbc-call-failed-error-3151?forum=accessdev 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 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 http://stackoverflow.com/questions/5583256/odbc-connection-failed-3151-ms-access-sql-server-2008 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 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 Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Administration » Getting http://www.sqlservercentral.com/Forums/Topic446169-5-1.aspx run-time error 3151 ODBC connection... 21 posts,Page 1 of 3123»»» Getting run-time error http://www.pcreview.co.uk/threads/re-odbc-connection-error-3151-windows-7.4001591/ 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 error 3151 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. error 3151 odbc 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 las Lafontaine Guest If you are running on a 64 bit OS, make sure that you are using the 32 bit version of the ODBC Panel; see http://support.microsoft.com/kb/942976 . Second, if you are creating an User DSN, try creating a System DSN instead. Remove the old User DSN for testing this. -- Sylvain Lafontaine, ing. MVP - Windows Live Platform Blog/web site: http://coding-paparazzi.sylvainlafontaine.com Independent consultant and remote programming for Access and SQL-Server (French) "DrAvi via AccessMonster.com"