Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Failed to lock map, map is in use for Network Atlas

Failed to lock map, map is in use for Network Atlas

Updated October 24, 2016

Overview

This article addresses the following error:

Error < Failed to lock map, map is in use by [username] on computer [server] since 9/28/2016 >

 

 

Environment

NPM 12.0

Cause 

This occurs in environments where migrations have occurred. Often times these maps will get locked and are still registered to the old server.

 

Resolution

  1. Open the Database Manager.
  2. Select Add Default Server and expand your database.
  3. Locate and right click MapStudioFiles.
  4. Select Query Table.
  5. Locate the LockUser and ComputerName columns. 
  6. Verify that it says NULL for LockUser and that the ComputerName column matches your current correct server.
  7. Close the database and try to edit the map again.
 

 

Last modified

Tags

Classifications

Public