Issue: Unexpected Behavior On Core with Incompatible .NET Versions

Version 17

    Verified Product Versions

    LANDESK Management Suite 9.5LANDESK Management Suite 9.6LANDESK Management Suite 2016.xLANDESK Endpoint Manager 2017.x

    Issue

     

    When .NET is updated to an incompatible version on a Core Server, you may have any of these issues:

     

    • Unable to launch core server activation utility
    • Queries do not expand when starting tasks that target queries or scopes
    • Unresponsiveness on the console
    • Inventory Scans not processing
    • Other issues

     

    The most efficient and accurate way to determine which version of .NET is installed Navigate to the following registry keys:

     

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client\Version

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

     

     

     

    Compatibility

     

    SupportedSupported: Ivanti has validated the .NET version with Ivanti Software. Ivanti provides full technical support for the corresponding .NET version running on the Core server.
    LegacyUnsupported: The version of .NET has exhibited unstable and intermittent behaviors when installed on the corresponding Core version.

     

    Core Version.NET 4.5NET 4.6.NET 4.7

    LDMS 9.5

    SupportedLegacyLegacy
    LDMS 9.6SupportedLegacyLegacy
    LDMS 2016.0SupportedLegacy

    Legacy

    LDMS 2016.3SupportedLegacy

    Legacy

    EPM 2017.1SupportedSupportedLegacy
    EPM 2017.3SupportedSupportedLegacy

     

     

    Cause

     

    If you are experiencing the activation issue, you may see:

    "Unhandled exception has occurred in your application. "

     

    Click details and you see the below errors:

     

    "See the end of this message for details on invoking

    just-in-time (JIT) debugging instead of this dialog box.

     

    ************** Exception Text **************

    System.OutOfMemoryException: Array dimensions exceeded supported range.

    at System.Diagnostics.TraceUtils.GetRuntimeObject(String className, Type baseType, String initializeData)

    at System.Diagnostics.TypedElement.BaseGetRuntimeObject()

    at System.Diagnostics.ListenerElement.GetRuntimeObject()

    at System.Diagnostics.ListenerElementsCollection.GetRuntimeObject()

    at System.Diagnostics.TraceInternal.get_Listeners()

    at System.Diagnostics.TraceInternal.WriteLine(String message)

    at LANDesk.ManagementSuite.Diagnostics.LogForNet.Init()

    at LANDesk.ManagementSuite.Diagnostics.LogForNet.GetLogger(String loggerName)

    at LANDesk.ManagementSuite.Licensing.ActivateCore.ActivateCoreForm.get_Log()

    at LANDesk.ManagementSuite.Licensing.ActivateCore.ActivateCoreForm.ActivateCoreForm_Load(Object sender, EventArgs e)

    at System.Windows.Forms.Form.OnLoad(EventArgs e)

    at System.Windows.Forms.Form.OnCreateControl()

    at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

    at System.Windows.Forms.Control.CreateControl()

    at System.Windows.Forms.Control.WmShowWindow(Message& m)

    at System.Windows.Forms.Control.WndProc(Message& m)

    at System.Windows.Forms.Form.WmShowWindow(Message& m)

    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

     

     

    ************** Loaded Assemblies **************

    mscorlib

    Assembly Version: 4.0.0.0

    Win32 Version: 4.6.1055.0 built by: NETFXREL2

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll

    ----------------------------------------

    LANDesk.ManagementSuite.Licensing.ActivateCore

    Assembly Version: 9.60.0.0

    Win32 Version: 9.60.3.64

    CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.Licensing.ActivateCore.exe

    ----------------------------------------

    System.Windows.Forms

    Assembly Version: 4.0.0.0

    Win32 Version: 4.6.1055.0 built by: NETFXREL2

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

    ----------------------------------------

    System

    Assembly Version: 4.0.0.0

    Win32 Version: 4.6.1055.0 built by: NETFXREL2

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

    ----------------------------------------

    System.Drawing

    Assembly Version: 4.0.0.0

    Win32 Version: 4.6.1068.2 built by: NETFXREL3STAGE

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

    ----------------------------------------

    LANDesk.ManagementSuite.Licensing.Activation

    Assembly Version: 9.60.0.0

    Win32 Version: 9.60.3.71

    CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.Licensing.Activation.DLL

    ----------------------------------------

    LANDesk.ManagementSuite.Database

    Assembly Version: 9.60.0.0

    Win32 Version: 9.60.3.68

    CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.Database.DLL

    ----------------------------------------

    LANDesk.ManagementSuite.Diagnostics

    Assembly Version: 9.60.0.0

    Win32 Version: 9.60.2.105

    CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.Diagnostics.DLL

    ----------------------------------------

    System.Configuration

    Assembly Version: 4.0.0.0

    Win32 Version: 4.6.1055.0 built by: NETFXREL2

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

    ----------------------------------------

    System.Core

    Assembly Version: 4.0.0.0

    Win32 Version: 4.6.1055.0 built by: NETFXREL2

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

    ----------------------------------------

    System.Xml

    Assembly Version: 4.0.0.0

    Win32 Version: 4.6.1064.2 built by: NETFXREL3STAGE

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

    ----------------------------------------

    System.Web

    Assembly Version: 4.0.0.0

    Win32 Version: 4.6.1069.1 built by: NETFXREL3STAGE

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll

    ----------------------------------------

    LANDesk.ManagementSuite.KeyValue

    Assembly Version: 9.60.0.0

    Win32 Version: 9.60.2.48

    CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.KeyValue.DLL

    ----------------------------------------

    System.Data

    Assembly Version: 4.0.0.0

    Win32 Version: 4.6.1055.0 built by: NETFXREL2

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll

    ----------------------------------------

    LANDesk.ManagementSuite.Data

    Assembly Version: 9.60.0.0

    Win32 Version: 9.60.3.59

    CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.Data.DLL

    ----------------------------------------

    LANDesk.DataServices

    Assembly Version: 9.60.0.0

    Win32 Version: 9.60.3.50

    CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.DataServices.DLL

    ----------------------------------------

    LANDesk.ManagementSuite.Information

    Assembly Version: 9.60.0.0

    Win32 Version: 9.60.3.72

    CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.Information.DLL

    ----------------------------------------

    log4net

    Assembly Version: 1.2.10.0

    Win32 Version: 1.2.10.0

    CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/log4net.DLL

    ----------------------------------------

     

    ************** JIT Debugging **************

    To enable just-in-time (JIT) debugging, the .config file for this

    application or computer (machine.config) must have the

    jitDebugging value set in the system.windows.forms section.

    The application must also be compiled with debugging

    enabled.

     

    For example:

     

    <configuration>

    <system.windows.forms jitDebugging="true" />

    </configuration>

     

    When JIT debugging is enabled, any unhandled exception

    will be sent to the JIT debugger registered on the computer

    rather than be handled by this dialog box."

               

    Resolution

     

    This problem is caused by .NET  You can remove .NET:

     

    The .NET 4.6 update can often be found as KB 3045560 - https://support.microsoft.com/en-us/kb/3045560

    • On Windows Vista SP2, Windows 7 SP1, Windows Server 2008 SP2, or Windows Server 2008 R2 SP1, Microsoft.NET Framework 4.6 is installed under Programs and Features in Control Panel.
    • On Windows 8 or Windows Server 2012, Update for Microsoft Windows (KB3045562) is displayed under Installed Updates in Control Panel. (KB is for .Net Framework 4.6)
    • On Windows 8.1 or Windows Server 2012 R2, Update for Microsoft Windows (KB3045563) is displayed under Installed Updates in Control Panel. (KB is for .Net Framework 4.6)

     

    • On Windows 8 or Windows Server 2012, Update for Microsoft Windows (KB3045562) is displayed under Installed Updates in Control Panel. (KB is for .Net Framework 4.6.1)
    • On Windows 8.1 and Windows Server 2012 R2, it's listed as Update for Microsoft Windows (KB3102467) Or KB4014510 under the Installed Updates in Control Panel (KB is for .Net Framework 4.6.1)
    • On Windows 10 you can find this as Update for Microsoft Windows (KB3102495) under the Installed Updates in Control Panel (KB is for .Net Framework 4.6.1)

     

    • On Windows Server 2012 you can find this as Update for Microsoft Windows (KB3151804) under Installed Updates in Control Panel. (KB is for .Net Framework 4.6.2)
    • On Windows 8.1 / Windows Server 2012 R2 you can find this as Update for Microsoft Windows (KB3151864) under Installed Updates in Control Panel. (KB is for .Net Framework 4.6.2)
    • On Windows 10 you can find this as Update for Microsoft Windows (KB3151900) under Installed Updates in Control Panel. (KB is for .Net Framework 4.6.2)

     

     

    .NET 4.7 Redistributable:

    • .NET Framework 4.7 for Windows 7/Windows Server 2008 R2: KB3186497
    • .NET Framework 4.7 for Windows Server 2012: KB3186505
    • .NET Framework 4.7 for Windows 8.1/Windows Server 2012 R2: KB3186539
    • .NET Framework 4.7 for Windows 10 Version 1607/Windows Server 2016: KB3186568
    • .NET Framework 4.7 Language Packs for Windows Server 2012: KB4015882
    • .NET Framework 4.7 Language Packs for Windows 8.1/Windows Server 2012 R2: KB3186606
    • .NET Framework 4.7 Language Packs for Windows 10 Version 1607/Windows Server 2016: KB3186607

     

    In addition, the removal of a .NET version may cause configuration issues for IIS, so it is recommended to check the following:

     

    • Verify and re-enable services (run services.msc)
      • Set the World Wide Publishing Service to Automatic, then start IIS manager to verify
      • Applicable SQL services, depending on your configuration
      • Applicable LANDESK, Intel and Managed Planet services, depending on your configuration
    • Verify IIS configuration affected by .NET
      • Application Pools should look like this:  (unless you have built custom app pools)

              ApplicationPools.png

                *** If you have made any of the above adjustments, reboot your server ***

      • Verify that the https binding on the Default Web Site has the appropriate certificate
      • Check for ISAPI and CGI restrictions (set all to allow)

     

     

     

    • We do not recommend the following registry tweak. This will fix the activation but doesn't fix the other issues known with .Net 4.6

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework

    You'll probably find a useRyuJIT DWORD value of 1 there. Set it to 0.

    Then, create a useLegacyJIT DWORD value into the same registry key and set it to 1.