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

Error 1705 – File in Exclusive Use will happen when an attempt is made to write to a file and the action fails. This paper reviews the most common causes of the error, possible remedies, and links to related resources.

Applies To:

All Pro Series products.

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.

The error can often be corrected using the System Maintenance tools available in the System Manager module:

Clear All Flags
Re-index Application and System Files
Deleting temporary files may also correct the error. For more information see our white-paper "Clean Re-indexing and Deleting Temporary Files" available at
www.accpac.com/support/sourcesolutions/Technical_Papers/General/

If the above does not correct the error or it occurs during System Maintenance; it is an indication that the problem is outside the control of the program. The most common reasons for this will be:

A file needed by the program is marked as Read-only.
The server is holding open a file needed by the program.
The user does not have the correct privileges on the workstation and/or network to access the file.

IMPORTANT NOTE: A qualified network technician should perform the following procedures.

Read-only Files

Use the appropriate attributes command for your operating system to insure all files in the Pro directory and subdirectories are marked as Read/Write/Shareable (not Read-only). Consult your operating system documentation for details.

Files Held Open on Server

NT or 2000 Server

Make sure all users are out of the Pro Series program.
Check the users on the server and disconnect any open connections to the program. May need to use the REFRESH option from the SERVER MANAGER when complete.

If this and/or other file locking errors are a continuous problem you may want to review the following Microsoft Support Articles for more information www.microsoft.com.

93348 - Locking Error Message 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 in Windows NT

Novell 4.x/5.x/6.x

Make sure all users are out of the Pro Series program.
Check the users on the server and disconnect any open connections to the program.

If this and/or other file locking errors are a continuous problem it may be an issue with the Novell Client version you are using or how it is configured.

Download the newest client for the workstation operating system from Novell's website www.novell.com/support.

To configure the Client32 for Windows 95/98 workstations:

Open control panel
Double-click on network icon
Configuration tab-Highlight the Novell Client32
Click on Properties
Go to Advanced settings
In the dropdown box:
1. Arrow down to Auto reconnect - Value = 1 (This will restore drive mappings and printers; and close out open files)
2. Arrow down to Checksum - Value = 2
3. Arrow down to True commit - Value = On (This is set to on to ensure data integrity when using databases; it turns caching Off) ***
4. Use extended file handles - Value = On
5. Close behind ticks - Value = 0
6. Opportunistic locking - Value = Off

*** If the True commit = On appears to create a performance issue you can try the following:

Turn True commit = Off
Cache write = Off

To configure the Client32 for Windows NT 4.0/2000/XP workstations:

Open control panel
Double-click on network icon
Configuration tab-Highlight the Novell Client32
Click on Properties
Go to Advanced settings
In the dropdown box:
1. Arrow down to Auto reconnect - Value = 1 (This will restore drive mappings and printers; and close out open files)
2. Arrow down to File commit - Value = On
3. Arrow down to File caching - Value = Off

Notes: File Commit is the same as True commit for Windows 95/98. Use extended file handles is not used for NT/2000/XP since they do not have a 255 limit for file handles. File cashing replaces Close behind ticks and Opportunistic locking used for Windows 95/98.

For older Novell versions see Microsoft Support Article Q89156 "File Access Denied" Error Message When Writing to File.

User Privileges

Make sure user privileges on the network are giving proper access to needed files. May also need to check privileges on the workstation if NT/2000/XP. To test if User Privileges is the cause of the error, log into the workstation and network as an Administrator and see if it still occurs.

Products : Services : Support
Home : About : Contact : Sitemap