Error 1705 – File in Exclusive Use and Related Issues
Disclaimer
This information is provided "as is" and without any warranties of any kind, whether express, implied or statutory, including, without limitation, any implied warranty of merchantability or fitness for a particular purpose. Pacific Rentals Solutions, Inc. shall not be liable for any direct, indirect, special, incidental or consequential damages which arise in connection with this information, and this limitation of liability will apply regardless of the form of action. The entire risk with respect to this information rests with you, and we suggest that you thoroughly evaluate the information before it is relied upon or used in any way.
Overview
The following message or other file locking messages appear when trying to write to a file and the action fails in Sage Pro ERP:
Error 1705: File in Exclusive Use
This article reviews the most common causes of the error and possible solutions.
Solution
If this error occurs, use the System Recovery Utilities available in System Manager:
- Clear all flags
- Reindex application and system files
- Delete temporary files
If this issue persists, it is usually an indication that the problem is outside of the program. The following list provides some common situations that may occur and solutions for resolving them:
Read-only Files
A file that is needed by the program has been marked as Read-only.
Use the appropriate attributes command for the operating system to insure that
all of the files in the Sage Pro directories and subdirectories are marked as
read, write and shareable; they should not be Read-only.
Consult the operating system documentation for more information.
User Privileges
The user does not have the correct privileges on the workstation and
network to access the file. Verify that the correct privileges have been
assigned on the network and Microsoft Windows NT, Microsoft Windows
2000/2003 and Microsoft Windows XP workstations for proper access to needed
files. To confirm whether this issue is caused by insufficient user
privileges, login to the workstation and network as an Administrator and try
the same function. If the procedure executes correctly, the issue is
privilege based
- Verify that all users are logged out of the program
- Verify the users on the server and disconnect any open connections to the program. In Windows NT, it may be necessary to use the REFRESH option from the SERVER MANAGER when complete.
- Review the following Microsoft Support Articles for
more information:
- 93348 - Locking Error Messages in a Multiuser Environment
- 126026 - Server Optimization in RFCB Caching (NT and 2000)
- 296264 - Configuring Opportunistic Locking in Windows 2000
- 129202 - Explanation of Opportunistic Locking on Windows NT
Troubleshooting the Error
All steps should be performed with users out of the system after a full backup of your program directory and subdirectories has been made.
To test for open files:
Open Windows Explorer, navigate to the folder that RCMS is installed to (usually named Pro73). Right click on this folder and choose Rename. Add a 1 to the end of the folder and press Enter. If you successfully renamed the folder there are no open files.
If you received an Access Denied prompt there are open files in the folder, continue to step ii. below to determine if there is a user logged in to RCMS.
In the root RCMS folder find a file named 'pro.fxp', rename this file to 'pro.fxp1'. If you receive an Access Denied error, someone is running RCMS, find the computer/user and have them quit out of the program.
If you are able to rename this file successfully rename the file back to pro.fxp. In this case there is another program that has files open. This other program could be Windows, RC-Commerce, Anti-Virus software, or any other third party program that reads RCMS tables. The easiest solution in this case is to reboot the server. After rebooting, run both tests again, do not begin the RCMS update until you can pass both of these tests.
Notes:
- This error can be due to not having the privileges set properly in Windows to access the files in RCMS.
- Clearing Flags in System Manager does not log users out of the program. Therefore, if the RCMS Active User List shows no users logged in to RCMS this does not mean that there are no other users logged in (the flag may have been cleared).
