Communication Link Error Odbc
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Asked by: [Microsoft][ODBC SQL Server Driver]Communication Link Failure SQL Server > SQL Server Data Access Question 0 communication link failure odbc Sign in to vote Several of our customers are getting a message intermitantly odbc communication link failure 0 throughout the day where the connection is closed. The message being generated is [Microsoft][ODBC SQL Server Driver]Communication Link Failure. odbc call failed communication link failure These messages started in the last two weeks. Thanks for any direction that can be thrown my way. David Tuesday, November 27, 2007 10:26 PM Reply | Quote All replies 0
Odbc Sql Server Driver Communication Link Failure
Sign in to vote Hello David. We've started to have a similar problem. Our processing center is currently not very busy, as our major load starts after the beginning of the tax season. For this first time since we switch to SQL Server, we've started seeing unexplainable network connection drops between our client applications and our SQL Server. Currently, our SQL Server is 2005, SP2 with cumulative microsoft odbc sql server driver communication link failure solution updates package 3 for SQL Server 2005 SP2 (a cumulative SP2 upgrade package). We never saw this problem on SQL Server 2005, SP1, which is what we used last year, nor on previous versions of SQL Server. We've seen the problem on both 32-bit and 64-bit SQL Server machines. And, the problem appears to ocurr only with connections that have been idle for a while. Note that we have not changed the default settings for SQL Server 2005 TCP/IP connections. The KeepAlive option is set to 30000 ms. What we WANT is for the behavior of our SQL Servers to go back to being what is was prior to SP2 or SP2 with the cumulative update package 3 (we are not sure which is the problem). That behavior was that inactive database connections were not timed out/dropped. The connection was not closed until the client closed it (either gracefully or ungracefully). We just have too much old code that depends upon this behavior. PS. to MS people -- Any help with this issue will be greatly appreciated. Katy Thursday, December 13, 2007 9:22 PM Reply | Quote 1 Sign in to vote A
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 7,2000 » Administration » [Microsoft ODBC driver] communication link failure ssis Communication link... [Microsoft ODBC driver] Communication link failure Rate Topic Display Mode Topic Options
Communication Link Failure Sql Server 2012
Author Message ninadraje_shindeninadraje_shinde Posted Friday, January 18, 2008 11:06 AM Forum Newbie Group: General Forum Members Last Login: Friday, February
Microsoft Sql Server Native Client 10.0 Communication Link Failure
1, 2008 1:30 AM Points: 4, Visits: 11 hi do any one have solution for this error..[Microsoft ODBC driver] Communication link failurei am at client side.. domain controller (OS - server 2000) is on https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b7a4c6f2-0d1b-44ba-bb55-0e7848d64198/microsoftodbc-sql-server-drivercommunication-link-failure?forum=sqldataaccess server and sql server 2000 enterprise edition (server 2003) is on another server.my client pc is always getting disconnect due to this error..... i have installed MDAC 2.8 still i am not able to solve problem.... can any one help me...... Post #445042 Jo PattynJo Pattyn Posted Friday, January 18, 2008 11:48 AM SSCommitted Group: General Forum Members Last Login: Thursday, September 29, 2016 4:01 AM Points: 1,530, Visits: http://www.sqlservercentral.com/Forums/Topic445042-5-1.aspx 9,562 Is this a intermittent error or always?1)Check if the network connection is primestable2)Check the integrity of your database. An integrity fault due corruption can cause an aborted connection.More things to check.3) The server is momentarely down4) .. Post #445066 ninadraje_shindeninadraje_shinde Posted Friday, January 18, 2008 9:11 PM Forum Newbie Group: General Forum Members Last Login: Friday, February 1, 2008 1:30 AM Points: 4, Visits: 11 -this is not intermittent error.1)Check if the network connection is primestableyes... i have checked. i have look for long time on server. everything is ok. infact when i m getting disconnected with client, i have to restart the client computer and the connection gets eshtablished again...........2)Check the integrity of your database. An integrity fault due corruption can cause an aborted connection.-can you help me in this regards.... i am not sure what exactly should do for database intigity.More things to check.3) The server is momentarely down-no, i never seen this problem..... server is running fine....4) .. Post #445187 ninadraje_shindeninadraje_shinde Posted Friday, January 18, 2008 9:13 PM Forum Newbie Group: General Forum Members Last Login: Friday, February 1, 2008 1:30 AM Points: 4, Visits: 11 one more thing, i am running my own software on client and
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta http://stackoverflow.com/questions/5032382/odbc-sql-server-driver-communication-link-failure Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us https://community.spiceworks.com/topic/499741-odbc-sql-server-driver-error-communication-link-failure Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like communication link you, helping each other. Join them; it only takes a minute: Sign up odbc sql server driver communication link failure up vote 3 down vote favorite I have an Access 2003 front-end with SQL 2005 back-end. Occasionally, users get the error below and the front-end crashes. Any pointers as to how I can resolve this? [ODBC SQL communication link failure Server Driver] Communication link failure sql sql-server ms-access odbc share|improve this question edited Dec 23 '11 at 14:43 Fionnuala 77k665110 asked Feb 17 '11 at 17:30 DarkW1nter 92222556 Have you been through the steps in say: social.msdn.microsoft.com/forums/en-US/sqldataaccess/thread/… ? –Fionnuala Feb 17 '11 at 19:34 1 Have a look at the DNS configuration. Misconfigured workstations can cause no end of mysterious problems like this. The usual problem is that an Internet DNS is being queried before the local one. You want the local DNS to be the primary (and, perhaps, only DNS), and let your local DNS pass on queries to the Intenret for everything that's not local. I've seen this fix such errors in more than one instance. –David-W-Fenton Feb 18 '11 at 2:52 1 Agree with David. At one of the places I worked our server took so long to respond to DNS queries that our workstations would use the secondary DNS server, which was off our network, to try to find local workstati
a SQL database migration to a new production server as a consultant for a former employer. Moving Deltek Vision to the cloud On-prem Vision servers and data transferring to Vision Essentials in the cloud. UPDATE - this project is DONE with 100% success! Human Resource/Payroll Management System HRMS & Payroll system was in-house developed product by a team of 5 members, with help of ASP.NET 3.0, C#.NET, MS SQL 2008 R2. IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now Dear Spiceheads, I hope i can get some helpful inputs here. We keep getting this error on a user , which has this client software that is connected to a server. I have asked for assistance from our Software support but tells us there is something wrong with our network connection. However I can ping the server from the client PC. The client PC is windows 7 64-bit. And Auto update was disabled. Appreciate any of your ideas .. Thanks in advance Reply Subscribe RELATED TOPICS: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or acces ODBC SQL Drivers ConnectionRead errors in ODBC to SQL Server   3 Replies Thai Pepper OP JCBeard May 21, 2014 at 1:03 UTC What is the Firewall configured like? Make sure that port 1433 and any other port that your sql server is using is open on the server and on the workstation. Does other users connect properly? What is the difference between them and this one if there are some that do? 1 Serrano OP tablesalt May 21, 2014 at 1:47 UTC Hi JC beard, I dont have any problems with other users. I did check the ports. Port 1433 is open on server, using advance port scanner to check open ports, But I got this weird results while checking port in the client- I just found out it displays another PC name. It was the previous name of this PC before i Had it formatted. So I can still ping this with its old name and wi