Mssql Error 3146
Contents |
your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link error 3146 access above to proceed. To start viewing messages, select the forum that you want error 3146 odbc call failed to visit from the selection below. Results 1 to 5 of 5 Thread: ODBC - Connection Failed Error 3146 error 3146 odbc call failed access 2010 Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 05-05-09,19:17 #1 shanmugha View Profile View
Run Time Error 3146 Odbc Call Failed Access 2010
Forum Posts Registered User Join Date May 2009 Posts 8 Unanswered: ODBC - Connection Failed Error 3146 Hi, I have a situation here.I will be glad if anyone could help. We have a Microsoft Access 2003 accessing the SQL Server 2000 database using ODBC connection.I have set the database as a System Datasource with SQL Server driver and the connection settings. When i launch the run time error 3146 odbc call failed oracle .mdb application,i am able to connect to the database and fetch results.But only while populating the data on one of the combobox,the ODBC connection failed error 3146 arises. I turned on the tracing and saw that the SetConnection Attr failed error in the log. Any help is highly appreciated. Thanks in advance. Reply With Quote 05-05-09,20:24 #2 pkstormy View Profile View Forum Posts Moderator Join Date Dec 2004 Location Madison, WI Posts 3,926 Are you able to enter data for this field directly into the table? If not, are you able to enter data in this field directly into the SQL Server table (I'm guessing yes.) You can also try refreshing (or delete and relink) the linked tables. You can also put in a msgbox me!MyProblemField in the AfterUpdate (or BeforeUpdate) event to see what value is actually being saved in the combobox and see if it matches the SQL Server field type. I'm not sure what the error exactly means but these are some things I normally do to troubleshoot. My guess is that you may not be passing the correct value type for that field (what is the fie
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: To get the detailed error for 3146: ODBC call fail error. SQL Server > SQL Server Express Question 0 access macro error 3146 Sign in to vote Hi all, I have a MSaccess front end and SQL server 2005 back end. The functionality is that in the front-end VBA code the application compares the data in the text files which are linked to the application with the data in the tables in SQL server and updates the SQL server tables. My problem is that whenever there is a key constraint violated or http://www.dbforums.com/showthread.php?1642114-ODBC-Connection-Failed-Error-3146 we try to insert duplicates into the primary key or any other error .... The message box shows only : error 3146: ODBC link Failed. There is no detailed descrition like the one we get in SQL server where the error and the cause both are shown. Is there a way to retreive the entire error??? Note: This question has not been answered in any previous post. kindly do not https://social.msdn.microsoft.com/Forums/sqlserver/en-US/7d32e8fa-9ec6-44d4-beaf-68cc7f1c855d/to-get-the-detailed-error-for-3146-odbc-call-fail-error think otherwise. Thanks in advance. Tuesday, July 05, 2011 5:54 AM Reply | Quote Answers 1 Sign in to vote I assume that you are using the ODBC DSN for communicating with the backend SQL Server 2005 DB from your front end Access Application. Can you enable ODBC logging following the instructions in : http://support.microsoft.com/kb/274551[How To Generate an ODBC Trace with ODBC Data Source Administrator] This ODBC trace can give you more details about the exceptions you see on the application.. Note: Do not forget to turn tracing off when you are done with the troubleshooting. If you keep tracing set to on, it degrades your application performance. Hope this helps.. Chaitanya( Twitter | Blogs ) Any documentation bug? Tell us about it at Connect. Please feel free to add any community comments in any of the MSDN/technet articles. This posting is provided "AS IS" with no warranties, and confers no rights. The next CTP for SQL Server Code Name "Denali" is coming soon. Sign up now to be notified of the next CTP release. Marked as answer by WeiLin QiaoModerator Wednesday, July 13, 2011 7:41 AM Tuesday, July 05, 2011 6:34 AM Reply | Quote All replies 1 Sign in to vote I assum
Join the Community! Creating your account only takes a few minutes. Join Now I am having some issues on several client machines where the receive https://community.spiceworks.com/topic/556832-odbc-error-3146-3155 an error which stops the application and requires then to use task manager to forcibly close the program. on of the errors is 3155 pfexecuteSQl passthrough-- ODBC insert on a linked table "tblprocesserrorlog" failed. this may happen to a user 4 or 5 times a day or none at all. this application has a access 2013 front end and an Sql backend. the developers are adamant the application error 3146 is fine but still we get these types of errors. for the most part a client machine is a windows 7 64bit pc running office 2013 (32bit) and this application is also 32bit. server is 2008r2 and doesn't appear to be heavily used. I would be grateful for any help or advice on trouble shooting this problem. Reply Subscribe RELATED TOPICS: General ODBC Error 1004 ODBC under WINE error odbc error 3146 odbc issue?   6 Replies Chipotle OP Stuart8129 Aug 8, 2014 at 1:41 UTC Looks like record locking on the SQL back end. It could be timing out/trying to write a record to a table that someone else is accessing at that time. I know the devs say it's not the application but I would beg to differ. It may be a setting with something between the two but still. Edit: are you able to look at the SQL processes/locks when these errors happen? Also may be able to increase the ODBC timeout value, worth looking at that. 0 Datil OP GerardMainardi Aug 8, 2014 at 1:45 UTC The error is telling you what you need to know: you're unable to insert on tblProcessErrorLog, which is a linked table in Access. Is this only happening to certain people, or is this happening to everyone who uses this Access front-end? The first thing to do would be to open the Access database and try opening tblProcessErrorLog. Are you able to open it successfully? Are you able to open it successfully from several different computers? It's possible that there may be an ODBC data source that needs to be set up