- 0 minutes to read

Release Notes

Troubleshooting the Windows Server Monitoring Agent

If you have any issues that you can not solve, contact our Support or send us an email at support@nodinite.com

Access denied

In the diagnostic files, if you get System.UnauthorizedAccessException: Access is denied, on the target server, please review the WMI Access rights.

  1. Run wmimgmt.msc
  2. Connect to target server (or do the operation locally on the target server).
    wmimgmt.msc MMC
  3. Right-Click | Properties.
    Properties
  4. Select the Security tab.
    Security tab
  5. Click on the Security button and make sure the account in use for the Nodinite Windows Server Monitoring Agent is present with appropriate permissions according to your needs and current configuration.
    Assign permissions

Invalid Class

Please review this specific user guide.

Invalid Namespace

Please review this specific user guide.

IIS Monitoring on Windows 2016 or earlier

Note

This section does NOT apply if you are using version 6.2.2.0 or later.

To Monitor the IIS, ensure the agent has all the Prerequisites installed.

On Windows Server 2016 or earlier, the system has Microsoft.Web.Administration in Assembly version 7.0.0.0 which in turned uses .NET Framework 2.0. The Agent ship with a much newer version.

In a Monitor View, the IIS resource is in the Unavailable state.

To solve this, follow the steps below:

Note

These steps are Manual and must be applied each time the Agent is updated.

  1. Stop the Agent.
  2. Remove the Microsoft.Web.Administration.dll file in the installation folder of the agent.
  3. Copy the Microsoft.Web.Administration.dll from C:\Windows\assembly\GAC_MSIL\Microsoft.Web.Administration\7.0.0.0__31bf3856ad364e35 folder to the installation folder of the Agent.
  4. Edit the Nodinite.MonitoringAgent.WindowsServerHost.exe.config file using Notepad++ and add the following assembly redirect section:
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
            <assemblyIdentity name="Microsoft.Web.Administration" publicKeyToken="31bf3856ad364e35" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-10.0.0.0" newVersion="7.0.0.0" />
        </dependentAssembly>
    </assemblyBinding>

Diagnostics file entry example

In the Diagnostics file you probably see any of the following entries:

{"date":"2025-03-04T13:26:30.7430533+01:00","level":"ERROR","appname":"Nodinite.MonitoringAgent.WindowsServerHost.exe","logger":"IISHelper","thread":"16","ndc":"(null)","message":"An error occurred while getting Application pools on Server: 127.0.0.1","exception":"System.AggregateException: Cannot retrieve application pools. Exception: 'Object reference not set to an instance of an object.' ---> System.NullReferenceException: Object reference not set to an instance of an object.\r\n   at Microsoft.Web.Administration.ConfigurationManager.CreateWritableAdminManager(WebConfigurationMap webConfigMap, String configPathToEdit, Boolean isAdminConfig, Boolean isRedirectionConfig)\r\n   at Microsoft.Web.Administration.ConfigurationManager.CreateConfiguration(WebConfigurationMap configMap, String configPathToEdit, Boolean isAdminConfig, Boolean isRedirectionConfig)\r\n   at Microsoft.Web.Administration.ConfigurationManager.GetConfiguration(String rawConfigurationPath, String cacheKey, Boolean isAdminConfig, Boolean isRedirectionConfig)\r\n   at Microsoft.Web.Administration.ConfigurationManager.GetApplicationHostConfiguration()\r\n   at Microsoft.Web.Administration.ServerManager.ApplicationPoolsSectionCreator()\r\n   at Microsoft.Web.Administration.Lazy.Initialize[T](T& target, CreateInstanceDelegate`1 valueFactory)\r\n   at Microsoft.Web.Administration.ServerManager.ApplicationPoolCollectionCreator()\r\n   at Microsoft.Web.Administration.Lazy.Initialize[T](T& target, CreateInstanceDelegate`1
  • and/or
{"date":"2025-03-05T11:55:53.8845728+01:00","level":"ERROR","appname":"Nodinite.MonitoringAgent.WindowsServerHost.exe","logger":"IISHelper","thread":"14","ndc":"(null)","message":"Failed to get details about the Application Pools from the IIS Server: BizTalk 2016 Server- SERVERNAME","exception":"System.AggregateException: One or more errors occurred. ---> System.IO.FileLoadException: Could not load file or assembly 'Microsoft.Web.Administration, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)\r\n   at Nodinite.MonitoringAgent.WindowsServer.Helpers.IISHelper.GetInternetInformationService(String address)\r\n   at System.Threading.Tasks.Task`1.InnerInvoke()\r\n   at System.Threading.Tasks.Task.Execute()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Nodinite.MonitoringAgent.WindowsServer.Helpers.IISHelper.<GetInternetInformationServiceAsync>d__12.MoveNext()\r\n   --- End of inner exception stack trace ---\r\n   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)\r\n   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)\r\n   at Nodinite.MonitoringAgent.WindowsServer.Helpers.IISHelper.GetApplicationPoolsAndsites(Task`1 iisTask, WindowsServerEntry windowsServer, DateTime startTime, List`1& appPools, List`1& WebSites, List`1& ftpSites)\r\n---> (Inner Exception #0) System.IO.FileLoadException: Could not load file or assembly 'Microsoft.Web.Administration, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)\r\nFile name: 'Microsoft.Web.Administration, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'\r\n   at Nodinite.MonitoringAgent.WindowsServer.Helpers.IISHelper.GetInternetInformationService(String address)\r\n   at System.Threading.Tasks.Task`1.InnerInvoke()\r\n   at System.Threading.Tasks.Task.Execute()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Nodinite.MonitoringAgent.WindowsServer.Helpers.IISHelper.<GetInternetInformationServiceAsync>d__12.MoveNext()\r\n\r\nWRN: Assembly binding logging is turned OFF.\r\nTo enable assembly bind failure logging, set the registry value [HKLM\\Software\\Microsoft\\Fusion!EnableLog] (DWORD) to 1.\r\nNote: There is some performance penalty associated with assembly bind failure logging.\r\nTo turn this feature off, remove the registry value [HKLM\\Software\\Microsoft\\Fusion!EnableLog].\r\n<---\r\n"}

If this is the case, you should try the assembly redirect option as documented on this page.

  1. Start the Agent.

Important

If you are reading this article, you are most likely no longer supported by Microsoft and must update your run-time environment.

FAQ

How do I add Windows Server to monitor with Nodinite?

Adding an arbitrary number of Windows Servers for Nodinite to monitor is a straightforward process and requires only proper access rights. Simply follow the steps detailed in the Configuration user guide.

Info

You must be part of the Administrators role