Forum Discussion

The_Dark_Knight's avatar
8 years ago

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

  • Hi mate,

    Have you tried restarting the Admin service?

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

    • The_Dark_Knight's avatar
      The_Dark_Knight
      Level 4

      Hey!

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

      • plaudone1's avatar
        plaudone1
        Level 6

        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 

  • 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.

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