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 > NPM error: Discovery has been interrupted by timeout

NPM error: Discovery has been interrupted by timeout

Created by Richard Casey, last modified by MindTouch on Jun 23, 2016

Views: 2,470 Votes: 0 Revisions: 3

Overview

This article provides steps to resolve the following error when discovering large or multiple subnets:

Discovery has been interrupted by timeout. Results of discovery are not completed

Environment

All NPM versions

Resolution

1. Go to Settings > Getting started with Orion> Network Sonar Discovery.

2. Click the discovery that fails and select Edit.

3. Click Next until you get to the Discovery Settings tab.

4. Adjust the discovery timeout with the slide bar.

 

 

Last modified

Tags

Classifications

Public