Backup Exec Tcp Error 10061
Contents |
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions tcp error 10061 actively refused Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as tcp error code 10061 you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Backup Exec
Tcp Error Code 10061 Wcf
2014_TCP error code 10061: no connecti... VOX : Backup and Recovery : Backup Exec : Backup Exec 2014_TCP error code 10061: no connecti... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float
Tcp Error Code 10061 No Connection Could Be Made
this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Backup Exec 2014_TCP error code 10061: no connection could be made because the target machine actively refused David_Elizabeth Level 3 08-04-2014 03:49 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi everyone I need some help. I have installed Symantec Backup Exec 2014 on a Windows Server tcp error code 10061 localhost 2012 R2 Std. I have use the local administrator account for the installation and the login. The installation have been quite easy. However, when I start Backup Exec 2014 it always give me an error msg: "Could not connect to net.tcp//[server_name]:50104/BEMService/ServerData. The connection attempt lasted for a time span of 00:00:02.0002511. TCP error code 10061: No connection could be made because the target machine actively refused it [server_ip]:50104." I have found that some users have posted this problem on the forum. I have try to have a look about the solution proposed in the forum. Like creating a new rule in the Firewall setting, I have also disable the firewall. The problem is still there. I have noticed that some services is not started. Unfortunately, I cannot start them. They always give error message like: "Error 1068: The dependancy service or group failed to start". The services are: Backup Exec Remote Agent for Windows Backup Exec Agent for Browser Backup Exec Device & Media Service Backup Exec Job Engine Backup Exec Management Service Backup Exec Server I have try tochange the services execute path using administrative command in windows environment,the problem is still the same. Can someone help me please... Thanks. Solved! Go to Solution. Labels: 2014 Backup and Recovery Backup Exec Configuring Erro
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In
Tcp Error Code 10061 No Connection Could Be Made Because The Target
CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps tcp error code 10061 wcf service you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search tcp connection error 10061 hercules instead for Do you mean VOX : Backup and Recovery : Backup Exec : Could not connect VOX : Backup and Recovery : Backup Exec : Could not connect Subscribe to https://vox.veritas.com/t5/Backup-Exec/Backup-Exec-2014-TCP-error-code-10061-no-connection-could-be/td-p/689311 RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Could not connect ilhanabi N/A 06-21-2012 07:33 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content stnd Windows Server 2008 R2. I did a new install. I'm getting the following https://vox.veritas.com/t5/Backup-Exec/Could-not-connect/td-p/505164 error from? Thank you for your help. Could not connect Backup Exec does not appear to be running on XXXXX SERVER. Could not connect to net.tcp://xxxxx-server:50104/BEMService/ServerData. The connection attempt lasted for a time span of 00:00:02.0039063. TCP error code 10061: No connection could be made because the target machine actively refused it 10.0.0.6:50104. Labels: 2012 Backup and Recovery Backup Exec Error messages 0 Kudos Reply 5 Replies Hi, Check and see if any CraigV Moderator Partner Trusted Advisor Accredited 06-21-2012 12:10 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, Check and see if any firewall isn't perhaps running on that server. If so, either drop it, or open the BE ports as per the TN below: https://www-secure.symantec.com/connect/forums/restoring-tape-backed-sun-server You should also check and make sure that no antivirus is blocking the BE services. Lastly, check the BE 2012 SCL below and make sure you have installed it on a supported operating system for media servers: http://www.symantec.com/business/support/index?page=content&id=TECH175581 Since SP1a for BE 2012 is out, also ensure that
target machine actively refused it. .NET Framework > Windows Communication Foundation, Serialization, and Networking Question 0 Sign in to vote I hosted a wcf service application using windows services. When my client (ASP.NET) tries to call the service class hosted by the windows service, I get this https://social.msdn.microsoft.com/Forums/vstudio/en-US/58e420e9-43a3-4119-b541-d18158038e36/tcp-error-code-10061-no-connection-could-be-made-because-the-target-machine-actively-refused-it?forum=wcf error "TCP error code 10061: No connection could be made because the target machine actively refused it. ". Is there a fix for this? The same code works fine if I host it using a console application. Friday, December 08, 2006 5:25 PM Reply | Quote Answers 2 Sign in to vote What port are you listening on? Is that port unblocked in your windows firewall? Monday, December 11, 2006 4:16 PM Reply | Quote All replies 2 Sign in to vote What port are you tcp error listening on? Is that port unblocked in your windows firewall? Monday, December 11, 2006 4:16 PM Reply | Quote 1 Sign in to vote Yes, my firewall was blocking it. I got around it and it fixed the problem. Proposed as answer by raucci2000 Friday, May 23, 2014 1:28 PM Monday, December 11, 2006 6:11 PM Reply | Quote 0 Sign in to vote which port ? Friday, April 06, 2007 12:45 PM Reply | Quote 0 Sign in to vote Hi, Evn i am gettin tcp error code the same error. Can u tell me wat is the fix. Friday, April 13, 2007 9:29 AM Reply | Quote 0 Sign in to vote I am getting the same error - but only when I change my return type to a cutom object. CLR types work fine - i.e. an IList of Strings, but not, say, MyResponseObj. I'm running the asp.net development server on port 1212, with a wsHttpBinding. Like I said, the problem seems to be with the return type which is marked up with the DataContract - DataMember tags, like my other custom objects that work fine as input objects. I am able to pass in an arbitrarily complex object of custom types no problem - but the server tanks with a custom return type. Any suggestion would be appreciated. Thanx - Ian Monday, May 14, 2007 4:56 PM Reply | Quote 0 Sign in to vote Regarding the custom-return-types problem, if you configure tracing http://msdn2.microsoft.com/en-us/library/ms733025.aspx are there any exceptions on the server? Monday, May 14, 2007 5:15 PM Reply | Quote 0 Sign in to vote Brian I've configured trace in the web.config file as per the article, but no output or log file is generated. Do I need to create a trace object in my test code (NUnit) to explicitly start the trace segment? Or should the web.config entry be sufficient? Thanks, Ian Monday, May 14, 2007 6:11 PM Reply | Quote 0 Sign in to vote Kenny, I've unblocked the port on the firewall and still unable to conn