Odbc Sql Server Error 10054
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My an existing connection was forcibly closed by the remote host sql server Forums Answered by: odbc error SQL Server > SQL microsoft sql server error 10054 Server Data Access Question 0 Sign in to vote one of our clients is sql server error 10054 management studio trying to connect to our sql server 2000 database from one of our apps and is getting an odbc error:2009-03-31 16:18:07.971 ******************** ODBC Errors ********************2009-03-31
Provider Ssl Provider Error 0 - An Existing Connection Was Forcibly Closed By The Remote Host
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 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 an existing connection was forcibly closed by the remote host minecraft ********************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 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. Ma
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 an existing connection was forcibly closed by the remote host c# about Stack Overflow the company Business Learn more about hiring developers or posting ads
Ssis Tcp Provider An Existing Connection Was Forcibly Closed By The Remote Host
with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow
An Existing Connection Was Forcibly Closed By The Remote Host Wcf
is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Losing ODBC connection with SQL Server 2005 Database up vote 2 down https://social.msdn.microsoft.com/Forums/sqlserver/en-US/ee0a5fa8-5578-4d7b-aaeb-f4fa6aa41755/odbc-error?forum=sqldataaccess vote favorite One of our clients has an application (FoxPro 9) running on top of a SQL Server 2005 backend. Intermittently, they are losing their ODBC connection with the SQL Server database. Below is the initial error information: Err Msg: Connectivity error: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()). ODBC Err Msg: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()). SQL State: 01000 ODBC Err No: 10054 ODBC Handle: 1 FoxPro Error No: 1526 We http://stackoverflow.com/questions/425130/losing-odbc-connection-with-sql-server-2005-database cannot duplicate this error on command. We have tried any number of solutions to no avail. One such hardware base solution which we found was described in: http://support.microsoft.com/kb/942861/en-us I mention this because it almost perfectly matches what we have been seeing. However, we have implemented all the workarounds listed in that posting (and in this one http://support.microsoft.com/kb/948496 ) - and the problem still continues. This issue seems to show itself after the execution of long running queries, but we are not receiving any timeout errors, either from the application, or from SQL Server. I do not believe that this is the result of an idle timeout, because it sometimes occurs in the middle of an executing program. I am not a hardware guy, but both the network, and the server (Windows Server 2003), appear to be fast and well designed. There are times however, when the database server is under significant stress. If anyone has any suggestions on things we could try...please let us know! sql-server odbc database-connection visual-foxpro foxpro share|improve this question edited Sep 8 '15 at 11:34 camelCase 70841132 asked Jan 8 '09 at 17:23 Clinemi 49451427 add a comment| 4 Answers 4 active oldest votes up vote 1 down vote Just a s
SQL Server experts to answer whatever question you can come up with. Our new http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=102370 SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums. SQL Server Forums Profile | ActiveTopics | Members | Search | ForumFAQ Register Now and get your question answered! Username: Password: Save Password Forgot your Password? All Forums SQL Server 2000 Forums SQL Server Administration (2000) ODBC an existing problem for domain user Reply to Topic Printer Friendly Author Topic techgfx Starting Member 2 Posts Posted-05/07/2008: 08:40:23 Hi, I'm using some aplications that use ODBC to connect the aplications with the database in a windows 2003 SQL server.The problem is that when the users try to see the reports there is a an existing connection runtime error. The person who programmed the aplications says that it works prefectly with computers outside the domain using a XP Computer as a server.I wonder if the restrictions that the users have are not allowing them to access the databse and the ODBC without problems.I really could use some help in this matter. Thanks.Thanks in advanced rmiao Flowing Fount of Yak Knowledge USA 7266 Posts Posted-05/07/2008: 15:08:32 Do you have error message? techgfx Starting Member 2 Posts Posted-05/16/2008: 00:40:08 Error MessageMicrosoft SQL Server loginConnection failed:SQLstate: '01000'SQLserver Error: 10054[Microsoft][odbc sql server driver[Tcp/IP sockets]ConnectionRead (recv()).Connection failed:SQL State: '08So1'SQL Server Error: 11[Microsoft][odbc sql server driver][Tcp/IP sockets]General network error. check your network documentation.Thanks in advanced jen Flowing Fount of Yak Knowledge Sweden 4110 Posts Posted-05/16/2008: 10:01:27 when you create the odbc entry it has to be system instead of user so the credentials are carried over unless your users have individual logins to the database server--------------------keeping it simple... rmiao Flowing Fount