Submit a ticketCall us
Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Unexpected website error when editing nodes in Orion Platform

Unexpected website error when editing nodes in Orion Platform

Updated January 11th, 2019


After you install the latest Microsoft® Windows Server® updates and attempt to edit, add or unmanage your nodes assigned to a polling engine, the following website error appears:

The formatter threw an exception while trying to deserialize the message: 
There was an error while trying to deserialize parameter The InnerException message 
was ''EndElement' 'Comparer' from namespace '' is not expected. 
Expecting element '_compareInfo'.'. Please see InnerException for more details.

formatter threw an exception.jpg

unmanage now failed.PNG



  • Mismatch of .NET versions on one or more SolarWinds servers
  • Missing August 2018 or Greater .NET Rollup windows update on one or more SolarWinds servers


1. Firstly, Ensure the same .NET version is installed on all SolarWinds servers.


Active Diagnostics can be updated to 1.9.0 or Greater where this has a built-in check to look at all the SolarWinds Servers in this instance and determine if you have a mismatch of .NET




Manual Verification of this can be done through the registry on each SolarWinds Server.

You can find the .NET Framework versions by viewing the registry (.NET Framework 4.5 and later)

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full


Example of Mismatch

  • Main poller on .NET Framework 4.6.2 (394802)
  • APE poller on .NET Framework 4.7.1 (460805)
  • Example.PNG


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\1033,Release

.NET Version


.NET Framework 4.5 378389
.NET Framework 4.5.1 installed with Windows 8.1 378675
.NET Framework 4.5.1 installed on Windows 8, Windows 7 SP1, or Windows Vista SP2 378758
.NET Framework 4.5.2 379893
.NET Framework 4.6 installed with Windows 10 393295
.NET Framework 4.6 installed on all other Windows OS versions 393297
.NET Framework 4.6.1 installed on Windows 10 394254
.NET Framework 4.6.1 installed on all other Windows OS versions 394271
.NET Framework 4.6.2 installed on Windows 10 Anniversary Update 394802
.NET Framework 4.6.2 installed on all other Windows OS versions 394806
.NET Framework 4.7 installed on Windows 10 Creators Update 460798
.NET Framework 4.7 installed on all other Windows OS versions 460805
.NET Framework 4.7.1 installed on Windows 10 Fall Creators Update 461308
.NET Framework 4.7.1 installed on all other Windows OS versions 461310
.NET Framework 4.7.2 installed on Windows 10 April 2018 Update 461808
.NET Framework 4.7.2 installed on all other Windows OS versions 461814

2. SecondlyEnsure the August 2018 or greater .NET Rollup has been installed on each SolarWinds for your specific OS and specific version of .NET:



List of Microsoft .NET rollup updates after the August preview update that resolved the issue:


September 2018

October 2018

November 2018

December 2018

January 2019
(© 2019 Microsoft Corporation, available at, obtained on January 11, 2019)


3. Having the same .NET version of each SolarWinds server is required, and whilst it is not a strict requirement, the same .NET version on different OS levels across the environment may behave differently, this can also help prevent running into future issues so do consider updating your servers to the same OS version and patching the SolarWinds servers in the instance at the same time with same patch cycle. It is entirely possible Microsoft change other DLL's or add security updates in the future that prevent communication between the SolarWinds Servers if there is some mismatch.


SolarWinds Patch Manager can help you streamline this task.


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.



Last modified