Applications Systems

"Type is not resolved for member 'SolarWinds.APM.Logging.Log4net.SwLogicalPropertiesContext,SolarWinds.APM.Logging" error in HTTP form monitor on Agent nodes

This article discusses an issue with HTTP Form Monitor in SolarWinds SAM which fails when using the Agent polling method, displaying the error: "Type is not resolved for member 'SolarWinds.APM.Logging.Log4net.SwLogicalPropertiesContext,SolarWinds.APM.Logging'."

First published date

7/9/2025 4:24 PM

Last published date

10/21/2025 9:09 PM

Overview

This article addresses the issue where the HTTP Form Monitor in SolarWinds Server & Application Monitor (SAM) fails when using the Agent polling method, resulting in the error: "Type is not resolved for member 'SolarWinds.APM.Logging.Log4net.SwLogicalPropertiesContext,SolarWinds.APM.Logging'."

This error typically indicates a problem with the SolarWinds APM (Application Performance Monitor) component, specifically related to the Log4net logging framework used by the agent.

Product section

Application Centric Monitor

Cause

This is a known issue in SAM 2025.1 and 2025.2.

Resolution

This issue is fixed in SAM 2025.4. Consider upgrading your environment. If you can't upgrade, please use an agentless polling method as a workaround.

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.