Agent Error 10061
Contents |
on and reload this page. All Places > Business > ePolicy Orchestrator (ePO) > Discussions Please enter a title. You can not post a blank message. Please type your message network error was 10060 and try again. This discussion is archived 3 Replies Latest reply
Failed To Connect Error 10061
on Jul 10, 2013 11:34 AM by JoeBidgood Failed to connect, error 10061 ( No connection could network error 10061 failed to connect to essbase server be made because the target machine actively refused it. ) kenobe May 30, 2013 2:30 PM I've seen this error mentioned in several places but no firm answer
Tcp Error Code 10061: No Connection Could Be Made Because The Target Machine Actively Refused It
given.While trying to push a replication to SADRs at a remote site we get this error within 30 seconds. I'm pretty sure it's a block at one of the firewalls between me and my subordinate site - but not having an easy time convincing the infrastructure folks of that. Weirder still, the SADR is talking to the EPO to get policy and DAT updates. That leads me to believe one specific port is being blocked.Quick reference, here are the ports my server is configured for:Agent-to-server communication port: 80Agent-to-server communication secure port: Enabled on port 443 Agent wake-up communication port: 591Agent broadcast communication port: 8082Console-to-application server communication port: 8005Client-to-server authenticated communication port: 8443So here's the question, when I press START REPLICATION, which of the above ports is actually being used from the server to the client, 80? 443?ThanksKen I have the same question Show 0 Likes(0) 5313Views Categories: Configuration, Other (see tags) Tags: none (add) replicationContent tagged with replication, 10061Content tagged with 10061, sadrContent tagged with sadr This content has been marked as final. Show 3 replies 1. Re: Failed to connect, error 10061 ( No connection could be made because the target machine actively refused it. ) alexn May 30, 2013 2:55 PM (in response to kenobe) Kenobe,This issue occurs when the SuperAgent is on a different subnet than the ePO server and the SuperAgen
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20122008 R2200820052000LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: SQL Server Agent won't start SQL Server > SQL Server Database Engine Question 0 Sign in to vote We have a client who is on SQL 2005 (Version 9.00.3042.00) and Windows Server 2003. They have four SQL instances on this one server that all seem to run fine, however, there is one SQL server Agent service that won't start, which is responsible for GP jobs. The service is setup to login automatically with the Local System account, but comes up with this error when started https://community.mcafee.com/thread/56965?start=0&tstart=0 from the Services window: The SQL Server Agent (DYNAMICS) service on Local Computer started and then stopped. Some services stop automatically if they have now ork to do, for example, the performance logs and alerts service. The Event Viewer description is: SQLServerAgent could not be started (reason: Unable to connect to server 'tpc-db1\dynamics':SQLServerAgent cannot start). The event ID is 103. Finally, the SQLAGENT.out file shows: 2011-07-19 15:01:30 - https://social.technet.microsoft.com/Forums/sqlserver/en-US/20d1890c-2aac-4e94-928d-8a6638e428e2/sql-server-agent-wont-start?forum=sqldatabaseengine ! [298] SQLServer Error: 10061, TCP Provider: No connection could be made because the target machine actively refused it. [SQLSTATE 08001] 2011-07-19 15:01:30 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00] 2011-07-19 15:01:30 - ! [298] SQLServer Error: 10061, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001] 2011-07-19 15:01:30 - ! [000] Unable to connect to server 'TPC-DB1\DYNAMICS'; SQLServerAgent cannot start 2011-07-19 15:01:36 - ! [298] SQLServer Error: 10061, TCP Provider: No connection could be made because the target machine actively refused it. [SQLSTATE 08001] 2011-07-19 15:01:36 - ! [165] ODBC Error: 0, Login timeout expired [SQLSTATE HYT00] 2011-07-19 15:01:36 - ! [298] SQLServer Error: 10061, An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. [SQLSTATE 08001] 2011-07-19 15:01:36 - ! [382] Logon to server 'TPC-DB1\DYNAMICS' failed (DisableAgentXPs) 2011-07-19 15:01:36 - ? [098] SQLServerAgent terminated (normally) We have tr
by CloudFlare Ray ID: 2ea4abd5279527e0