Error 1705: File access denied

These errors indicate that a needed file is currently locked or not available to the program. This may be due to a file locking problem between the network and the workstation(s), a network rights issue (the user in question has insufficient rights to the drive or directory), insufficient file handles, or the attributes of a needed file are set read-only. We will examine each of these situations.

File Locks
The first thing to check is if a user has an "exclusive lock" on a file. This can usually be done through your network software, so check the network documentation for more information. One way that a file can be locked open is if someone exits TeleMagic abruptly (such as their machine locks up while TeleMagic is open, and they just shut off their machine and leave for the day). Their machine may be off, but the network software is maintaining their lock on a file. Something similar may happen if the server crashes while TeleMagic is open. The server's lock on a TeleMagic file may not have been cleared, or the damaged system files from the crash will continue locking the data files incorrectly upon restarting the server.

We recommended that the system administrator instruct all users to close all Windows applications and log off the network before turning off the workstation. You may also want to consider purchasing a program that will automatically log users off the network at a specific time (if it is not already provided with your network software). One advantage to an automatic log off program is that your backups and rebuilds are assured of operating properly since there will be no one accessing the files.

Note: Version 3.5 includes a feature which can be used to automatically log users out of TeleMagic in order to perform rebuilds or other maintenance. Contact Telemagic.ca for information on upgrading to the latest version.

Another cause of file locking problems is having too many programs locking records and files in TeleMagic. This may occur on a Windows for Workgroups machine which is connected to a Novell Netware or similar Client/Server network. On the workstation, the user might have the SHARE program (included with DOS) loaded. Windows for Workgroups has a similar program called VSHARE, which performs the same task as the SHARE program for Windows applications. The network software will also have its own locking program. That means there are now three separate programs trying to lock the same files. What usually happens in this case is that the user will exit TeleMagic, which clears the network and VSHARE locks, but the DOS SHARE locks are still in place. If they then attempt to run TeleMagic again, they may receive the error. The solution in this case is to remove the SHARE program, which may be loading in either the AUTOEXEC.BAT or CONFIG.SYS files on the workstation. Check with the documentation of other software installed on that system to insure that none of these other applications require SHARE.

On a peer-to-peer network, the lack of a locking program may also cause the error. Many peer-to-peer networks, such as Windows for Workgroups, Windows 95, and Lantastic V6.0 already include a file and record locking routine. This should be loaded according to the instructions provided with the software. However, if SHARE is loaded along with the network's file locking program, you may see problems similar to those detailed above for Client/Server networks. Other peer-to-peer networks may need SHARE loaded on each workstation.

Note: On a Windows for Workgroups network, the error can also be generated by failing to load the IFSHELP.SYS file in the CONFIG.SYS. If it isn't already there, add the following line to that file: DEVICE=C:\WINDOWS\IFSHLP.SYS Be sure to change the drive and directory to the correct location for your system. This line is only required by Windows for Workgroups.

Network Rights
In order for TeleMagic to operate properly on a network, full rights to the TeleMagic global directory, the user directory, and any database directories the user will need to access is required. For a Novell Netware network, these rights would be Read, Write, Create, Erase, Modify and File Scan. For a Windows NT network, this would be Change (RXWD)(RXWD). Check the documentation for your particular network software for the equivalent to these rights. The error would typically occur if the user does not have modify or delete rights.

File Handles
The 108 and 1705 errors will rarely occur due to insufficient file handles (normally you would receive a "Multi-user conflict 6: too many files open" error), but it has happened.

File Attributes
These errors may also occur if a database file is set read-only through the operating system. Make sure all database files (files with an extension of DBF, FPT and CDX) are set read-write. Only program and library files (APP, DLL, ESL, EXE and FLL) should be set read-only.

 

-- End of FAQ #534

FAQ ID #534

Product Related: Telemagic 3.5x

Last Updated:
March 20, 2000