Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > When editing an account, you see this error: Object reference not set to an instance of an object error

When editing an account, you see this error: Object reference not set to an instance of an object error

Table of contents
Created by Perry Ginno Casio, last modified by MindTouch on Jun 23, 2016

Views: 2,114 Votes: 2 Revisions: 3

Updated June 9, 2016

Overview

This article provides troubleshooting steps to resolve the following error when editing a specific account:

Object reference not set to an instance of an object

Environment

  • NPM 11.5 or later

Steps

Check the specific account to see if there are limitations:

 

1. Go to Database Manager.
2. Go to Accounts table.
3. Go the specific account and see the column LimatationID1,LimatationID2 and LimatationID3.
4. If there's a non-zero value, go to Limitations table, and see if the value is there.
5. If it's not there, you need to remove that value.
6. Run the query below:

 

UPDATE Accounts SET LimitationID1 = '0'
WHERE AccountID = 'AccountIDoftheSpecificAccount'

 

 

 

 

Last modified

Tags

Classifications

Public