Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > Manage Nodes times out to error - object reference not set to an instance of an object

Manage Nodes times out to error - object reference not set to an instance of an object

Created by Daniel Polaske, last modified by Mike Wethington_ret on Dec 22, 2016

Views: 1,415 Votes: 1 Revisions: 5

Overview

When a user accesses the Manage Nodes screen, the loading icon spins for a long time. The screen eventually loads, but no nodes are shown and the error object reference not set to an instance of an object is shown.

Environment

  • All Orion environments

Cause 

Despite the fact that object reference not set to an instance of an object is often caused by a missing resource or broken link, in this case (when it occurs after a long time with the Manage Nodes screen loading) the error is caused by a timeout when querying the SQL server.

Resolution

This can be resolved by simply addressing the bottleneck which is occurring either from the end to end network connection to the SQL server or the delay in response when processing the SQL query itself.

 

 

Last modified

Tags

Classifications

Public