Oracle Connection Error 3151
Contents |
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
Odbc - Connection To Name Failed. (error 3151)
about Stack Overflow the company Business Learn more about hiring developers or posting ads run time error 3151 odbc connection failed oracle with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack
Error 3151 Odbc Connection Failed Windows 7
Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up MS Access error 3151 ODBC error --> ORACLE 11G up vote 1 runtime error 3151 odbc connection failed access 2013 down vote favorite I have an MS Access 2003 DB that was created by a contractor who has now left. The DB uses linked tables and DAO to connect to an ORACLE backend. It used to work until we recently upgraded our ORACLE version from 10g to 11g. As part of the upgrade we had to update our rather out dated "Microsoft ODBC for ORACLE" driver to "Oracle in microsoft visual basic runtime error 3151 odbc connection failed instantclient11_1" thats forms part of the ORACLE Instant Client. When we run the VBA it returns error code 3151 and says "ODBC --connection to 'MYDB' failed. I did a bit of googling and found that code 3151 is a generic code. However sometimes this works and other times(80% of the time) it doesn't. Its installed on an MS Xp SP3 32bit machine and the drivers are 32-bit. From The ODBC Manager when I run the test connection it is always successful and I can query the DB from within excel and using the "Import External data" Any idea how I can resolve this? ms-access odbc oracle11g dao share|improve this question asked Aug 14 '12 at 15:48 Alistair Laing 7961616 In my relatively limited dealings with Oracle, I have read that the Instant Clients can present their own peculiar set of problems. You might consider removing/uninstalling the Instant Client and go with the conventional client setup and see if that solves your problem. –David W Aug 14 '12 at 15:54 Are you sure the DSN name is the same as before? If not, you will need to rename to DSN to what Access is looking for, or update the linked table def
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
Kb 209855
AM #1 Insane_ai Newly Registered User Join Date: Mar 2009 Location: Cleveland, OH odbc connection to failed USA Posts: 161 Thanks: 1 Thanked 14 Times in 11 Posts Oracle ODBC Connection Error 3151 The following code works when employed
Odbc Call Failed Access 2010
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 http://stackoverflow.com/questions/11956101/ms-access-error-3151-odbc-error-oracle-11g 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 http://www.access-programmers.co.uk/forums/showthread.php?t=240995 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 Professional 64 bit You should specify what version of Access you had the application working properly with on Windows XP, and what version (including compiled architecture) you are attempting to use on Windows 7. __________________ -- Michael Lueck Lueck Data Systems To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. mdlueck View Public Profile Visit mdlueck's homepage! Find More Posts by mdlueck 01-29-
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 https://social.msdn.microsoft.com/Forums/office/en-US/620d70f1-5bca-4a51-9afc-10fcba4e866e/ms-access-runtime-2010-odbc-call-to-oracle-not-working?forum=accessdev Add-ins Changelog Microsoft Graph API Office 365 Connectors Office 365 REST APIs http://www.sqlservercentral.com/Forums/Topic446169-5-1.aspx SharePoint Add-ins Office UI Fabric Submit to the Office Store 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 Forums Asked by: MS Access Runtime 2010 ODBC call to Oracle not working Microsoft Office for Developers > Access error 3151 for Developers Question 0 Sign in to vote I have a MS Access 2010 applicaton 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 error 3151 odbc of MS Access 2010 using the ODBC connection 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? Friday, November 04, 2011 10:43 AM Reply | Quote All replies 0 Sign in to vote Does the connection itself works? Did you test the connection? How do you link the tables to your Oracle database? Also there are differences using 32bit vs. 64bit Windows 7 and Office 2010, if applicable in your situaton. Also put Error handling in place, especially when using Runtime, so you might have better idea what is causing it, see also below thread: http://social.msdn.microsoft.com/Forums/en-US/accessdev/thread/aa789d76-d946-4d96-ba0f-71ea2453a6d5/ Hope this helps, Daniel van den Berg | Washington, USA | "Anticipate the difficult by managing the easy" Sunday, November 06, 2011 2:35 AM Reply | Q
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, Septem