Network Management

Unable to list resource for windows node monitored by an agent with "registered for extension 'Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior' could not be loaded

This article provides information on how to identify a problem and steps to resolve it when a Windows node monitored by an agent is unable to list resources and update statistics. In the SolarWinds.JobEngineService_v<year>_agent.log, the following message may appear "registered for extension 'Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior' could not be loaded." related to the machine.config.

First published date

9/17/2021 1:47 PM

Last published date

1/13/2026 5:25 PM

Overview

When the JobEngine plugin fails to deploy on the agent, there can be many causes. This article addresses just a single specific cause relating to machine.config file on the agent. You will need to investigate the JobEngine log file of the agent itself (agentserver\C:\ProgramData\SolarWinds\JobEngine.v2\Logs_Agent). The log file is called SolarWinds.JobEngineService_v2_XX.log. From there you may find the following startup error for JobEngine plugin.

FATAL SolarWinds.JobEngine.ServiceProcess.SolarWindsService - (null) An error happened in Start System.Configuration.ConfigurationErrorsException: The type 'Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior, Microsoft.VisualStudio.Diagnostics.ServiceModelSink, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' registered for extension 'Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior' could not be loaded. (C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config line 311)


Failure of JobEngine plugin deployment may also cause other errors to be found in the console UI. Such as `MakeDataSetResultOneTimeJob failed` when running the Real-Time Process Explorer in SAM. This goes ahead and sends a job to the JobEngine for a list of currently running processes on the machine. If JobEngine cannot start or is not deployed, it obviously will fail right away and inform you with such an error.

Product section

Orion Platform

Cause

This issue occurs when machine configuration file from Microsoft IIS was not properly updated by Web Deploy.

Resolution

To manually fix the issue, perform the following steps:
  1. Modify C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config on affeced node where Web Deploy is installed
  2. Create a backup of  C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config
  3. Edit C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config
    • (a) remove line
      <add name="Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior" type="Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior, Microsoft.VisualStudio.Diagnostics.ServiceModelSink, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
    • (b) remove lines
      <commonBehaviors> <endpointBehaviors> <Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior /></endpointBehaviors> <serviceBehaviors> <Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior /></serviceBehaviors></commonBehaviors>

If the problem persists, analyze the error stack of the machine.config line number. It will state which line number is having interference with JobEngine startup. 

  1. Take a copy/backup of the machine.config
  2. Delete the entire line that is stated in the JobEngine error as causing the issue in startup.
  3. Attempt to redeploy the JobEngine plugin from the web interface (manage agents > view installed plugins > reinstall plugin)