Support HomeExpressNetExpress for BrowsersExpress for WindowsMVR InformationA-Plus™, Credit, UDI/UDVCriminal History

Search

Error 3260: "Couldn't save; currently locked by User '<UserName>' on machine '<MachineName>'"


Error 3260:  "Couldn't save; currently locked by 
User '<UserName>' on machine '<MachineName>'"
 

Problem:

This error occurred in Express for Windows™ when a user was attempting to add and save new requests. It could occur at any point where a user is attempting to add, modify, purge, delete, or update data within Express for Windows.  The error may be displayed as:

Error 3260 - Couldn't save; currently locked by user '<UserName>' on machine '<MachineName>'

<UserName> was "Admin" in the case that was reported. 

<MachineName> will be the network login name, or machine name, of the user who has the data locked.
 

Solution 1:

The broad approach is to have everyone who is in Express (or has been in Express today) to exit the program, log out of the network, reboot, and log back in to the network.  That will probably resolve the issue.  If for some reason it is not practical to have all users do this, try the following alternate solutions:
 

Solution 2:

Try deleting or renaming the EXPRESS.LDB file.   This file is usually located at:

X:\EXPRESSW\DATA\EXPRESS.LDB   (where X: is the Express drive), or at:

X:\AMSEXPW\DATA\EXPRESS.LDB  (where X: is the Express drive)

  • Have all users exit Express, if possible.

  • Rename or delete EXPRESS.LDB

This solution will not work if one of the users has this file locked.  In that case, when you attempt to delete or rename you will get an error that the file is in use.  If you are trying to rename the file using Explorer or File Manager, you might try to delete or rename in DOS.

If you are unable to successfully delete or rename EXPRESS.LDB, proceed to Solution 3.
 

Solution 3:

If you are not willing to attempt Solution 1, and if Solution 2 could not be used, the following steps can be used to attempt the fix one user at a time:

  1. Have the user who is getting the error exit Express, log out of the network, reboot and log back into the network.  Then, have him/her try again.  If they still get the error, proceed to Step 2..

  2. Check the user whose network login name is shown in the <MachineName> field.  It is possible that this user has a prompt displayed that is waiting for them to click some type of response, such as <OK> or <Continue>.   If so, have them respond to the prompt and return to the Express main menu screen.   Have that user exit from Express. Proceed to Step 3.

  3. Have the user who got the error message attempt the function that gave them the error - i.e. entering new requests, deleting reports, etc.  If everything now works, stop here.

  4. However, if an error still occurs, verify that the <UserName> and <MachineName> in the error message are the same ones that appeared in the first error message. If so, proceed to Step 5 below.  If not, return to Step 2 and repeat Steps 2 and 3 with the user who network login name is now shown as <MachineName>.  

  5. If the error still occurs and  the <UserName> and <MachineName> have not changed in the message, have the user whose name is shown as <MachineName> exit all programs, log out of the network, and reboot.  Then have the user who is getting the error try again.

  6. If this procedure is not successful, you will have to attempt Solution 1.

This page has been viewed 13620 times | Document Rating is  2.00 / 5.00 | Last Updated on 4/28/2004 7:08:38 AM

This Page:  


Search:

If you have suggestions for additional information, or need further assistance, please contact us by e-mail: 
iiX Customer Support or via phone at (800) 683-8553.