10061 Error Server Sql
Contents |
SERVER – Could not connect to TCP error code 10061: No connection could be made because the target machine actively refused it October 20, 2010Pinal DaveSQL, SQL Server, SQL Tips and Tricks22 commentsI was recently getting following error in my StreamInsight Application.Could not connect to TCP error code 10061: No connection could be sql server error 17 made because the target machine actively refused it.The solution was very simple, I had to sql server 2008 error 10061 enable exception of the my port in my windows firewall. The way I figured it out was by quickly disabling the firewall (it was sql server 2005 error 10061 not a production server). Once I disabled it, the application just worked fine; this was a sign that the firewall was the cause of the issue, I right away enabled firewall and added my port as exception. So sql server error 10061 connection refused many errors have cropped up recently due to the connectivity issue. I have started to make my routine to check firewall first before I move to next action item in my troubleshooting list.When I sent this detail to my internal technical list of the expert, I got the suggestion that this error happens due to many other reasons as well and not only due to firewall.I am interested to know when and how this error happens and
Sql Server Error 2
what is the resolution. This way, if we have complete list, we can avoid this error in future.Watch SQL in Sixty Seconds video to Resolve Connection Error: Reference: Pinal Dave (http://blog.SQLAuthority.com) Tags: SQL Error Messages1Related Articles SQL SERVER - Add failover cluster node fails with "number of cluster nodes supported for edition" January 27, 2016Pinal Dave SQL SERVER - Unique Nonclustered Index Creation with IGNORE_DUP_KEY = ON January 4, 2010Pinal Dave SQL SERVER - Fix : Error : 1326 Cannot connect to Database Server Error: 40 - Could not open a connection to SQL Server August 9, 2008Pinal Dave 22 comments. Leave new Nakul Vachhrajani October 21, 2010 10:47 pmHello!This execption/error stumps most developers/IT staff who have just recently been exposed to Windows Server 2008 R2. I belive the R2 blocks incoming transactions by default, while the vanilla-2008 did not. Therefore, all of a sudden a system/database that worked fine on a Windows 2008 Server fails to accept connections from remote machines when upgraded to run on Windows 2008 R2 Server.Reply Nishant Rapate June 6, 2012 3:15 pmI am facing the same database connetivity issue but i am connecting to local database where firewall not comes in the picture.please suggest.Reply hamza82 September 10, 2012 1:39 pmPlease share the steps you followed to solve this issue.Reply vasu June 26, 2012 4:43 pmSame to meReply vasu June 26, 2012 4:44 pmexec sp_
resources Windows Server
Sql Server Error 10060
2012 resources Programs MSDN subscriptions Overview sql server error 10061 solution Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards sql server error 53 Events Community Magazine Forums Blogs Tech Advisors Channel 9 Documentation APIs and reference Dev centers Retired http://blog.sqlauthority.com/2010/10/20/sql-server-could-not-connect-to-tcp-error-code-10061-no-connection-could-be-made-because-the-target-machine-actively-refused-it/ content Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. Errors and Events Reference Database Engine Events and Errors Cause and Resolution of Database Engine Errors https://msdn.microsoft.com/en-us/library/bb326400(v=sql.120).aspx Cause and Resolution of Database Engine Errors MSSQLSERVER_10061 MSSQLSERVER_10061 MSSQLSERVER_10061 MSSQLSERVER_-2 MSSQLSERVER_-1 MSSQLSERVER_2 MSSQLSERVER_53 MSSQLSERVER_102 MSSQLSERVER_107 MSSQLSERVER_125 MSSQLSERVER_137 MSSQLSERVER_207 MSSQLSERVER_208 MSSQLSERVER_233 MSSQLSERVER_360 MSSQLSERVER_511 MSSQLSERVER_601 MSSQLSERVER_605 MSSQLSERVER_611 MSSQLSERVER_617 MSSQLSERVER_701 MSSQLSERVER_802 MSSQLSERVER_823 MSSQLSERVER_824 MSSQLSERVER_825 MSSQLSERVER_833 MSSQLSERVER_844 MSSQLSERVER_845 MSSQLSERVER_846 MSSQLSERVER_847 MSSQLSERVER_905 MSSQLSERVER_916 MSSQLSERVER_926 MSSQLSERVER_945 MSSQLSERVER_948 MSSQLSERVER_1101 MSSQLSERVER_1105 MSSQLSERVER_1203 MSSQLSERVER_1204 MSSQLSERVER_1205 MSSQLSERVER_1222 MSSQLSERVER_1401 MSSQLSERVER_1406 MSSQLSERVER_1418 MSSQLSERVER_1457 MSSQLSERVER_1458 MSSQLSERVER_1461 MSSQLSERVER_1462 MSSQLSERVER_1505 MSSQLSERVER_1793 MSSQLSERVER_1803 MSSQLSERVER_1807 MSSQLSERVER_1904 MSSQLSERVER_2020 MSSQLSERVER_2501 MSSQLSERVER_2508 MSSQLSERVER_2511 MSSQLSERVER_2512 MSSQLSERVER_2515 MSSQLSERVER_2516 MSSQLSERVER_2518 MSSQLSERVER_2519 MSSQLSERVER_2522 MSSQLSERVER_2527 MSSQLSERVER_2530 MSSQLSERVER_2533 MSSQLSERVER_2534 MSSQLSERVER_2536 MSSQLSERVER_2537 MSSQLSERVER_2538 MSSQLSERVER_2539 MSSQLSERVER_2540 MSSQLSERVER_2546 MSSQLSERVER_2570 MSSQLSERVER_2574 MSSQLSERVER_2575 MSSQLSERVER_2576 MSSQLSERVER_2577 MSSQLSERVER_2579 MSSQLSERVER_2592 MSSQLSERVER_2593 MSSQLSERVER_2596 MSSQLSERVER_2814 MSSQLSERVER_3151 MSSQLSERVER_3156 MSSQLSERVER_3159 MSSQLSERVER_3168 MSSQLSERVER_3169 MSSQLSERVER_3176 MSSQLSERVER_3181 MSSQLSERVER_3260 MSSQLSERVER_3271 MSSQLSERVER_331
SQL Server experts to answer whatever question you can come up with. Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums. SQL http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=138045 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 2005 Forums SQL Server Administration (2005) Error 10061, connection actively refused Reply to Topic Printer Friendly Author Topic ron2112 Starting Member USA 44 Posts Posted-01/07/2010: 15:39:52 Got a strange one here. Two WinXP client machines and a third machine running SQL Server Express 2005... sql server Client A can connect to the SQL Server just fine, Client B can see the server instance in the browser but cannot connect (attempted using the sa account via SSMS). At this point, the error coming back was 26, "Error Locating Service/Instance Specified."Since Client A can connect, we know that the SQL Server is running and is configured to accept remote connections. So we set up an alias on Client B. This did not resolve the sql server error situation, but it did change the error to 10061, "No connection could be made because the target machine actively refused it."After this we tried the following:> Confirmed TCP/IP is enabled on the server.> Confirmed TCP/IP is using port 1433 and so is the alias on Client B.> Tried using the server's IP address instead of the machine name.And we're still stuck at error 10061 on Client B. I'm not sure what else there is to look at... anyone have any suggestions?Thanks!Ron Moses shan Yak Posting Veteran USA 84 Posts Posted-01/07/2010: 16:01:02 Try connecting with the IP Address, portnumber and see if it works.-Shan ron2112 Starting Member USA 44 Posts Posted-01/08/2010: 08:31:44 quote:Originally posted by shanTry connecting with the IP Address, portnumber and see if it works.Did that, same result. That's what I meant in my third bullet item, sorry if that was unclear.Ron Moses russell Pyro-ma-ni-yak USA 5072 Posts Posted-01/08/2010: 10:03:11 what OS is SQL Server on?Make sure windows firewall is not running. Make sure using TCP/IP and not named pipes.Edit: Also, see this: http://blogs.msdn.com/sql_protocols/archive/2007/07/19/tcp-provider-no-connection-could-be-made-because-the-target-machine-actively-refused-it.aspx Edited by - russell on 01/08/2010 10:06:21 ron2112 Starting Member USA 44 Posts Posted-01/08/2010: 10:42:12 quote:Originally posted by russellwhat OS is SQL Server on?Make sure windows firewall is not running. Make sure using TCP/IP and not named pipes.Edit: Also, see this: htt