Upgrade Has Detected The File QMap.LDB On Your System

When updating Quickmap data, you get the following error message:

Upgrade has detected the file C:\QMap\Data\QMap.LDB on your system. This usually means that either QuickMap is running on your computer, or someone sharing directory C:\QMap\Data is running QuickMap. Upgrade will not be able to copy files if they are in use.

Are you sure you want to continue?

You cannot Ignore this message. Someone is either currently running QuickMap, or was running it then crashed out. The first thing to check is whether or not someone has crashed out of quickmap. Do this by trying to manually delete the file C:\QMap\Data\QMap.LDB (or whatever LDB file was reported). If you can delete this file, then it is safe to continue with the upgrade. Note that you should be careful not to touch QMap.MDB. It is only the QMap.LDB file which is safe to delete. If you cannot delete the file, then it is locked, and you will need to proceed to step 1.

  1. Press Ctrl/Alt/Del and click on the Applications TAB. If quickmap is displayed in the list of running applications, then right mouse click on the application and select End Task off the menu. If the LDB file is still there, then go to Step 2.
  2. If you are at this step, then someone must have the file open via the QuickMap network share. You can get a list of users that have the file open using the Computer Management tool.To use the computer management too, you will need to log onto the actual server that shares the drive. To run the computer management tool, select:Start->Control Panel->Computer Management->System ToolsClick on “Open Files” to view all the files open on the network share.

    The person who has the file open is displayed in the “Accessed By” column. To view which computer the “Accessed By” person refers to, click on “Sessions” in the left hand panel.

    When you have found who has the file open, ask that person to exit quickmap, or perform Step 1 if necessary. If the LDB file still exists, then go to Step 3.

  3. Reboot your server and try again.

Comments are closed.