Highlighted

No connection could be made because the target machine actively refused it 127.0.0.1:8071

Hello,

I am facing the same issue with the Monitoring WebApp.

Need to know what am I missing.

Environment:

Windows Server 2012

EV 11.0.1 CHF5

VCS 6.1

Event:

Event code: 100001
Event message: System.Net.Sockets.SocketException - No connection could be made because the target machine actively refused it 127.0.0.1:8071
Event time: 3/15/2017 11:20:35 AM
Event time (UTC): 3/15/2017 5:50:35 AM
Event ID: 7761fcb572ab465181b16b4e01d0bdeb
Event sequence: 8
Event occurrence: 1
Event detail code: 0

Application information:
    Application domain: /LM/W3SVC/1/ROOT/MonitoringWebApp-1-131340305737117848
    Trust level: Full
    Application Virtual Path: /MonitoringWebApp
    Application Path: E:\Program Files (x86)\Enterprise Vault\MonitoringWebApp\
    Machine name: YBLPVDAKARCH01

Process information:
    Process ID: 31720
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM

Request information:
    Request URL: https://localhost:443/MonitoringWebApp/PerfCountersConfig.aspx
    Request path: /MonitoringWebApp/PerfCountersConfig.aspx
    User host address: ::1
    User: YESBANK\ESG30243
    Is authenticated: True
    Authentication Type: Negotiate
    Thread account name: YESBANK\ESG30243

Custom event details:
    
        * Application Event Information Start *
        
        Event created at: 3/15/2017 11:20:35 AM
        
        System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:8071

8 Replies
Highlighted

Re: No connection could be made because the target machine actively refused it 127.0.0.1:8071

Hi mate,

Have you tried restarting the Admin service?

If the problem persists, please provide more details about the issue.

--Virgil
Highlighted

Re: No connection could be made because the target machine actively refused it 127.0.0.1:8071

Hey!

Done that a couple of times. The problem for me is that this is a clustered environment by VCS.

Highlighted

Re: No connection could be made because the target machine actively refused it 127.0.0.1:8071

Hi, 

This could also relate to the other post https://vox.veritas.com/t5/Enterprise-Vault/ASP-Net-errors-in-Application-log/m-p/829793#M106776

A few things that you may want to check out.  Do you see EVStorageQueueBroker or StorageArchive running on the EV server?  If not, this could be an issue with .NET not being registered properly.  

Has IPv6 been enabled or firewall on the EV server?  

Have you run FileReregister.bat with the EV services stopped?  Especially the Regasm commands for .NET.

 

Regards,

Patrick 

Highlighted

Re: No connection could be made because the target machine actively refused it 127.0.0.1:8071

Hello Patrick,

Been a while since I have visited the forum and the issue. Other issues took precedence and I went on a short break.

The issue stands as is. Currently thinking of having Operations Manager installed on a different standalone server which will also have EV Reporting as well as SSRS.

As for the EV Server which had Operations Manager installed and this thread was started, FileRegister.bat has been run before and the Storage and Task Controller Services have been running on it. Currently, there is some issue on that server and hence the resources have been moved to the Spare Node. Would you suggest to run FileRegister.bat again?

Highlighted

Re: No connection could be made because the target machine actively refused it 127.0.0.1:8071

Hi, 

Is it always port 8071 in the event?   

Can you run netstat -aon | findstr 8071 to see if that port is listening?  

Does that port show on the current node?  

I would just run the regasm portion of the filereregister manually and verify they run properly. 

Regards,

Patrick 

Highlighted

Re: No connection could be made because the target machine actively refused it 127.0.0.1:8071

Try the following steps:-

1. Browse the 'Enterprise Vault\MonitoringWebApp' directory (open IIS--> expand default website-->select MonitoringWebApp and right click to explore and browse the files.

Backup web.config file and modify the original file to enable monitoring

2. check if all EV services are up. Check events if EV services are not starting.

3. netstat -ano | findstr 8071

server will listen to this port only if the EV services are up and running. Once all the above are done, reset IIS. If IIS has issues, restart the server and make sure IISreset is working ok. Try the monitoring url - http://localhost/monitoringwebapp/default.aspx

If issue still persists, try logs folder in the 'Enterprise Vault\MonitoringWebApp' directory.

Highlighted

Re: No connection could be made because the target machine actively refused it 127.0.0.1:8071

This exception message says you're trying to connect to the same host ( 127.0.0.1 ), while you're stating that your server is running on a different host. This 127.0.0.1 represents a 'loopback' . It allows the computer to communicate with itself via network protocol .

Dns.GetHostEntry(IPAddress.Loopback).HostName returns the host name of your machine. When you pass a host name to TcpClient , it will resolve it to one or more IP addresses using Dns.GetHostAddresses(hostName) . This includes the public and local IP addresses of your machine (e.g. 192.168.12.10), but not 127.0.0.1 (loopback address). So your client is trying to connect to any of the non-loopback addresses of your machine, while your server is listening only on the loopback address . So, no connection can be established. The solution to this problem is that connect to the same end point your server is listening on.

Highlighted

Re: No connection could be made because the target machine actively refused it 127.0.0.1:8071

Have you ran the MonitoringWebAppConfig.exe that is located in the EV installation folder on the EV server?