Submit a ticketCall us

WebinarUpcoming Webinar: How Help Desk and Remote Support Pays for Itself

Learn how help desk software can simplify ticketing management, allow you to track hardware and software assets, and accelerate the speed of IT support and service delivery. Gain insights on how remote support tools allow your IT team to maximize their efficiency and ticket resolution by expediting desktop troubleshooting, ultimately helping keep end-users happy and productive.

Register here.

Home > Success Center > Network Performance Monitor (NPM) > Run-time error '-2147467259 (80004005): Could not save; currently locked by another user

Run-time error '-2147467259 (80004005): Could not save; currently locked by another user

Updated March 11th, 2016


This article provides brief information on the following error:

Run-time error '-2147467259 (80004005): Could not save; currently locked by another user.


All ETS versions


This error typically is caused by back-up software that locks the Network Performance Monitor database while it is backing up the file. The Network Performance Monitor is unable to access the database while the application has the database locked.


SolarWinds recommends that you turn the lock database setting OFF within the back-up software. We also recommend that you run a compact and repair on the database after receiving this error message. For assistance with compacting and repairing, click on the following link: Compact and repair a database (© 2017 Microsoft, available at, obtained on February 13, 2017.)


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified