Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

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,059 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