Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Network Performance Monitor (NPM) > Unexpected Website Error Could not load file or assembly: Infragistics2.WebUI.UltraWebNavigator

Unexpected Website Error Could not load file or assembly: Infragistics2.WebUI.UltraWebNavigator

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 353 Votes: 2 Revisions: 11

Issue:

The web console is showing an error message during upgrade for NPM or NCM:
Unexpected Website Error Could not load file or assembly 'Infragistics2.WebUI.UltraWebNavigator.v8.2, Version=8.2.20082.1000, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' or one of its dependencies.
The system cannot find the file specified. (C:\InetPub\SolarWinds\orion\ncm\web.config line 39)

 

Could not load file or asssembly 'Infragistics2.WebUI.UltraWebNavigator.v8.2, Version=8.2.20082.1000, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' or one of its dependencies. The system cannot find the file specificed. (C:\InetPub\SolarWinds\Orion\NCM\Resources\NCMSummary\web.config line 23)

Cause:

The Infragistics2.WebUI.UltraWebNavigator.v8.2 is missing in the C:\Windows\Assembly folder.

Resolution:

1. Repair the SolarWinds Core Services.
  • For Windows 2003 - Go to Control Panel > Add/Remove Programs > SolarWinds Orion Core > Repair.
  • For Windows 2008 - Go to Control Panel > Programs and Features > SolarWinds Orion Core > Repair.
2. Go to C:\Windows\Assembly.
    Check that the missing file Infragistics2.WebUI.UltraWebNavigator.v8.2 is in the Assembly folder.
3. Run the Configuration Wizard - How to Run Configuration Wizard.
4. Check that the web console is loading properly. You can do this by going back to the page where the error previously appeared.


Applies to: Core, NPM, NCM

Last modified

Tags

Classifications

Public