Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > 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