Problem: Inability to write to a file for which the individual workstation operator has read/write permission. Files are not being released upon closing. Request help indentifying the problem.
Background:We have a small group, Windows 2000 Server running 12 workstations each using Windows XP (Professional) on the individual workstations.
Symptoms: When any of our workstations are first booted up, the operator can open his network stored files with the usual read/write permission. If that file is closed or saved (then closed), any attempt to re-open the file takes an unusual amount of time to re-open. If the file is again closed, it can only be re-opened in a 'read only' status. If we check the properties of the 'problem file', it shows that we should be able to write to it (but we cannot). Files which were opened on an individual workstation's C-drive do not have this problem. Re-booting the particular workstation (or the server) eliminates the write problem but the same sequence of events start all over again. The files are not properly being checked-in upon closing. Closing the file does not release it and upon re-opening it, the system thinks the file is still in use by another user or program. The problem is not associated with any one program or workstation and is known to affect both Microsoft Office products, and our CAD software.
Background:We have a small group, Windows 2000 Server running 12 workstations each using Windows XP (Professional) on the individual workstations.
Symptoms: When any of our workstations are first booted up, the operator can open his network stored files with the usual read/write permission. If that file is closed or saved (then closed), any attempt to re-open the file takes an unusual amount of time to re-open. If the file is again closed, it can only be re-opened in a 'read only' status. If we check the properties of the 'problem file', it shows that we should be able to write to it (but we cannot). Files which were opened on an individual workstation's C-drive do not have this problem. Re-booting the particular workstation (or the server) eliminates the write problem but the same sequence of events start all over again. The files are not properly being checked-in upon closing. Closing the file does not release it and upon re-opening it, the system thinks the file is still in use by another user or program. The problem is not associated with any one program or workstation and is known to affect both Microsoft Office products, and our CAD software.
