Forum Discussion

GertjanA's avatar
GertjanA
Moderator
14 years ago

monitoring web app on x64 w2008

I've installed the webmonitoring on a w2008x64 ev-server, having only admin and directory service.

When locally opening the page (localhost/monitoringwebapp/default.aspx), it shows an error with 'guidelines':

An error has occurred.

 

An error has occurred.

 

Health monitoring is enabled.

The error details have been updated in log.txt. Please contact the administrator or technical support with this file.

This list may help you in troubleshooting the issue.
  • Verify that AppPool Identity User is added to IIS_WPG group on the IIS server.
  • Verify that AppPool Identity User has Read access to HKLM\KVS\Enterprise Vault registry key.
  • You can enable Health Monitoring on this application by following these steps -
    1. Take a backup of current web.config file.
    2. Change the tag <healthMonitoring heartbeatInterval="0" enabled="false"> to <healthMonitoring heartbeatInterval="0" enabled="true">.
    The Health Monitoring log will be generated in log.txt.

 

There is no logfile. I've verified the above mentioned points, and all is well. Does anyone have an idea, or do I need an EV-server having ALL services running....

thx.

Gertjan

  • This morning, the page opened as expected.

    Probably some counters not updated?

5 Replies

  • This is in the log-file:

    Provider name: BufferedFileWebEventProvider
    Buffering:
    Buffering modality:
    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: 9/22/2010 2:33:14 PM
    Event time (UTC): 9/22/2010 1:33:14 PM
    Event ID: 7c1535ddb9ef450cb9c68e1a9a10e925
    Event sequence: 18
    Event occurrence: 1
    Event detail code: 0

    Application information:
        Application domain: /LM/W3SVC/1/ROOT/MonitoringWebApp-2-129296357097946727
        Trust level: Full
        Application Virtual Path: /MonitoringWebApp
        Application Path: D:\Program Files (x86)\Enterprise Vault\MonitoringWebApp\
        Machine name: REPLACED
    Process information:
        Process ID: 1812
        Process name: w3wp.exe
        Account name: DOMAIN\CORECTACCOUNT
    Request information:
        Request URL: http://localhost/monitoringwebapp/ExMonSummary.aspx
        Request path: /monitoringwebapp/ExMonSummary.aspx
        User host address: 127.0.0.1
        User: DOMAIN\VSA
        Is authenticated: True
        Authentication Type: Negotiate
        Thread account name: DOMAIN\VSA
    Custom event details:
       
            * Application Event Information Start *
           
            Event created at: 22/09/2010 14:33:14
           
            System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:8071
    Server stack trace:
       at System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32 port)
       at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(AddressFamily family)
       at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
       at System.Runtime.Remoting.Channels.RemoteConnection.GetSocket()
       at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)
       at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)
       at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
       at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Symantec.EnterpriseVault.OperationsManager.MiddleTierDataAccessLayer.IMiddleTierDataManager.GetConfiguration(ConfigurationDataSet& configurationDataSet)
       at Symantec.EnterpriseVault.OperationsManager.Web.UI.Utility.AppData.get_ConfigurationDataSet()
       at Symantec.EnterpriseVault.OperationsManager.Web.UI.SitePage.OnInit(EventArgs e)
       at System.Web.UI.Control.InitRecursive(Control namingContainer)
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
           
            Source - mscorlib
           
            * Stack Trace Start *
           
           
    Server stack trace:
       at System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32 port)
       at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(AddressFamily family)
       at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
       at System.Runtime.Remoting.Channels.RemoteConnection.GetSocket()
       at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)
       at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)
       at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
       at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Symantec.EnterpriseVault.OperationsManager.MiddleTierDataAccessLayer.IMiddleTierDataManager.GetConfiguration(ConfigurationDataSet& configurationDataSet)
       at Symantec.EnterpriseVault.OperationsManager.Web.UI.Utility.AppData.get_ConfigurationDataSet()
       at Symantec.EnterpriseVault.OperationsManager.Web.UI.SitePage.OnInit(EventArgs e)
       at System.Web.UI.Control.InitRecursive(Control namingContainer)
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
           
            * Stack Trace End *
           
            Event raised at: 22/09/2010 14:33:14
           
            * Application Event Information End *
    • The_Dark_Knight's avatar
      The_Dark_Knight
      Level 4

      Hello,

      I am also 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

      • GertjanA's avatar
        GertjanA
        Moderator

        Hello,

        YOu better open a new discussion for this. This seems to be different than what I was experiencing

  • This morning, the page opened as expected.

    Probably some counters not updated?