After an Upgrade, getting Web Console Error "Object reference not set to an instance of an object."

Version 2

    Verified Product Versions

    Endpoint Manager 9.6


    Description
    Exception: Object reference not set to an instance of an object.
    Applies to LDMS 8.8
    Source: LANDesk.WebConsole.Common

    Stack trace:
    at LANDesk.WebConsole.Common.TestLicense..ctor(String connectionString, String sCore)
    at LANDesk.WebConsole.Common.WebConsolePage.TestSession()
    at LANDesk.WebConsole.Common.WebConsolePage.OnLoad(EventArgs e)
    at System.Web.UI.Control.LoadRecursive()
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)




    Exception: Object reference not set to an instance of an object.

    Source: LANDesk.WebConsole.Utils

    Stack trace:
    at LANDesk.WebConsole.Utils.UserRigts.IsValidProduct(String productName)
    at LANDesk.WebConsole.Common.frm_NavLink.IsValidForProduct()
    at LANDesk.WebConsole.Common.frm_NavLink.ShouldShow()
    at LANDesk.WebConsole.Common.NavItems.GetNavItems(XmlNodeList nodes, NavItemGroup& navGroup, frm_RootFile rf)
    at LANDesk.WebConsole.Common.NavItems.GetNavLinks(frm_RootFile rf)
    at LANDesk.WebConsole.Common.NavItems.ProcessRootFile(frm_RootFile rf)
    at LANDesk.WebConsole.Common.NavItems..ctor()
    at LANDesk.WebConsole.Framework.UI.frm_nav.Page_Load(Object sender, EventArgs e)
    at System.Web.UI.Control.OnLoad(EventArgs e)
    at System.Web.UI.Control.LoadRecursive()
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    <font size='2'><b>Cause</b></font><div class='indent' style='font-size:10pt'>The install or upgrade may not have fully updated the web.config found in inetpub\wwwroot\remote\</div></div><br><div><font size='2'>Resolution
    Compare the c:\inetpub\wwwroot\remote\web.config file on the affected core to that of a working core at the same patch level. If they are different then follow the steps below.

    1) Copy the web.config from a working core on the same patch level.
    2) Edit the core server name within the file and change it to the affected core server name.
    3) Restart IIS.