Odbc Connection Error 10054
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: odbc error SQL Server > SQL 10054 an existing connection was forcibly closed by the remote host Server Data Access Question 0 Sign in to vote one of
Microsoft Sql Server Error 10054
our clients is trying to connect to our sql server 2000 database from one of our apps and is
An Existing Connection Was Forcibly Closed By The Remote Host Minecraft
getting an odbc error:2009-03-31 16:18:07.971 ******************** ODBC Errors ********************2009-03-31 16:18:07.971 Return code = -1.2009-03-31 16:18:07.971 SQLError[00] SQLState '08S01'2009-03-31 16:18:07.971 SQLError[00] NativeError 112009-03-31 16:18:07.987 SQLError[00] Message '[Microsoft][ODBC SQL Server
An Existing Connection Was Forcibly Closed By The Remote Host C#
Driver][TCP/IP Sockets]General network error. Check your network documentation.'2009-03-31 16:18:07.987 SQLError[01] SQLState '01000'2009-03-31 16:18:07.987 SQLError[01] NativeError 100542009-03-31 16:18:07.987 SQLError[01] Message '[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (recv()).'2009-03-31 16:18:07.987 ******************** ODBC Errors ********************We have lots of other clients and they are not having this problemAny ideas? Saturday, April 04, 2009 4:39 AM Reply | Quote Answers 1 Sign in to an existing connection was forcibly closed by the remote host wcf vote To be more specific, Native error 10054 is Winsock error "Connection Reset by Peer", ConnectionRead (recv()) means that the TCP connection was terminated on server when the client was reading data from the socket.1. Was server restarted when there are exisiting connection to it.2. Check SQL error log to see there was any exception thrown around the time when the client received the error, an exception in sql results in the corresponding connection being dropped.3. If this happened intermittently, sometime the error could indicate network hardware issue. You should involve your network admin to trouble shoot using netmon etc.This posting is provided "AS IS" with no warranties, and confers no rights. Marked as answer by John C GordonMicrosoft employee, Moderator Monday, April 13, 2009 8:35 PM Tuesday, April 07, 2009 6:18 AM Reply | Quote Moderator All replies 0 Sign in to vote This indicates network problems. Ask your LAN administrators to check all network equipment between the machines involved. Saturday, April 04, 2009 7:21 AM Reply | Qu
from GoogleSign inHidden fieldsSearch for groups or messages
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time https://www.experts-exchange.com/questions/20387457/ODBC-Connection-Mystery.html Help Create a Freelance Project Hire for a Full Time Job https://community.spiceworks.com/topic/543813-connectionread-errors-in-odbc-to-sql-server Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > ODBC Connection Mystery Want to Advertise Here? Solved ODBC Connection Mystery Posted on 2002-10-31 MS SQL an existing Server 1 Verified Solution 34 Comments 3,222 Views Last Modified: 2010-05-18 [TimeStamp]= On 10/7/2002 at: 4:35:31 PM [Message]= [SQLSTATE=08S01 - [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error. Check your network documentation. [Native Error=11]] [SQLSTATE=01000 - [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionRead (recv()). [Native Error=10054]] What the heck is going on???? I have an NT 4.0 with sp6a, SQL an existing connection 7.0 w/sp 4 My clients are connecting using ODBC TCP/IP connection, they will work all day long then all of a sudden they loose connection and can no longer connect, no one can, unless we change the connection to "multiprotocol". In order to connect again using TCP/IP I have to reboot the server. Is there a fix for this, and what causes this? BTW: this happens on clients running any Windows platform, i.e. 98, NT4.0, 2000, XP, XPpro. I'm between a rock and a hard place. Somebody save me! Gary 0 Question by:GlobalFax Facebook Twitter LinkedIn Google LVL 9 Best Solution bymiron Gary, Multi - protocol is very stable protocol library. If you find that its performance at the present time satisfies your needs then good. TCP/IP generally thought off as better performing, but its Go to Solution 34 Comments LVL 75 Overall: Level 75 MS SQL Server 62 Message Expert Comment by:Anthony Perkins2002-10-31 Please maintain this open question: http://www.experts-exchange.com/Databases/Microsoft_SQL_Server/Q_20282590.html Thanks, Anthony 0 LVL 1 Over
Microsoft SQL Server 2005 Join the Community! Creating your account only takes a few minutes. Join Now I have an Access database (composed of one table and some reports) that I migrated to SQL Server using the Access "Move Data" wizard. I can read/write to it just fine from the custom in-house software with no errors. It's SQL Server 2008 R2. Everything is default - since it was just one table I didn't change anything but permissions. I connect to it via ODBC in Access. If I leave the table open when viewing the data, I get the following error: ODBC - Call Failed. [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()). (#10054) [Microsoft][ODBC SQL Server Driver][DBNETLIB]General Network Error. Check your network documentation. (#11) [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()). (#10054) [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation. (#11) I then have to close and reopen Access to reconnect. There are three databases on this SQL Server - our ERP, our CRM, and this single table database. The ERP and CRM never have given this error when viewing data for a table in Access. Just this single table db. There are no network card issues in event viewer for either the workstation or the server. Any suggestions on where to start with this? I'm testing out moving this database to SQL Server. I haven't done it before, so there may be something obvious I'm missing. Edited Jul 21, 2014 at 2:51 UTC Reply Subscribe RELATED TOPICS: ODBC headaches... Cannot talk to SQL Server Unable to connect to SQL server remotely SQL Server Virtualization   5 Replies Tabasco OP IPX Dave Jul 21, 2014 at 4:57 UTC Hmm, have you checked to make sure that the account you are on has the appropriate permissions to access that db? 0 Serrano OP Marcos_Julio_ Jul 21, 2014 at 5:29 UTC - Try to create some user to that DB, using SQL Authentication. - Grant Role Members to the Db. - Connect to the DB using the SQL ODBC with this user. Sadly if this doesn't run, It would look like a network problem.. Maybe you are a client firewall and when It is set in Security to High (Internet, WAN, LAN), you get the error. Maybe putting lower the setting It didn't get the error. Also, I would check the time connection parameter from the ODBC Connection 0 Chipotle OP KMH Jul 21, 2014 at 6:16 UTC To respond to IPX Dave: The account is in the db_datawriter schema and the db_owner r