Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Network Performance Monitor (NPM) > Object reference not set to an instance of an object 500

Object reference not set to an instance of an object 500

Created by Alexander Aguilar, last modified by MindTouch on Jun 23, 2016

Views: 1,868 Votes: 0 Revisions: 6

Overview

This article describes the issue when the object reference is not set to an instance of an object 500 when trying to add a node into NPM.

Environment

NPM version 11.5.2

Cause 

This issue occurs because of a JavaScript error when adding a new node:
When the virtual memory allocated for the default application pool on an Orion server is limited, the Orion Web Console shows the following error:
JavaScript error:Sys.WebForms.PageRequestManagerServerErrorException Sys.WebForms.PageRequestManagerServerErrorException: Object reference not set to an instance of an object. undefined 500

Resolution

  1. Log in to your Orion server as an administrator. 
  2. Click Start > Control Panel > Administartive Tools > Internet Information Services (IIS) Manager.
  3. Click + to expand your local server.
  4. Click + to expand your Application Pools.
  5. Right-click DefaultAppPool, and then click Recycling.
  6. On the Recycling tab, in the Memory recycling group, confirm that Maximum virtual memory (in megabytes) is cleared.
  7. Click OK.

 

Last modified

Tags

Classifications

Public