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

11/1/2018 9:43 PM

12/13/2021 7:38 AM

This article addresses the following error:

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

 

Because of a previous migration, some of the maps had got stuck and were still listed under the old server's name not the current server.

Network Performance Monitor

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

 

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.

SQL Method:
Same as above method, executed with SQL query instead of GUI:

-- Scripts are not supported under any SolarWinds support program or service. -- Scripts are provided AS IS without warranty of any kind. SolarWinds further -- disclaims all warranties including, without limitation, any implied warranties -- of merchantability or of fitness for a particular purpose. The risk arising -- out of the use or performance of the scripts and documentation stays with you. -- In no event shall SolarWinds or anyone else involved in the creation, -- production, or delivery of the scripts be liable for any damages whatsoever -- (including, without limitation, damages for loss of business profits, business -- interruption, loss of business information, or other pecuniary loss) arising -- out of the use of or inability to use the scripts or documentation. UPDATE[dbo].[MapStudioFiles] SET computername = NULL UPDATE[dbo].[MapStudioFiles] SET LockUser = NULL