The information in this article applies to:
- Microsoft Visual SourceSafe, 16-bit and 32-bit, for Windows,
versions 4.0, 4.0a, 5.0
- Microsoft SourceSafe for Windows, versions 3.04, 3.1
SUMMARY
When checking in a File to the SourceSafe Database, SourceSafe may generate
the message:
"Error Writing to File"
MORE INFORMATION
This error may occur for several reasons:
- If there is no file listed after the error message, it may be caused by
a corrupt Status.dat.
- If it occurs three times in a row on a Novell Network, there is probably
no valid Owner for the file.
- The file may be corrupted and you may need to use FixFree, FixPrj, or
FixPar for version 3.X, or run Analyze for version 4.X or 5.0.
- The Network may not be handling file locks properly. In this case, it
may be necessary to let SourceSafe handle the File Locking. To do this,
shutdown the machine that is experiencing the error. This should force
the Network to release the lock. If this does not release the lock, the
Network administrator will have to do it from the server. Then add
Lock_Mode = Lockfile to SRCSAFE.INI file.
- If the software is not configured properly when running NFS mounting a
UNIX drive, other users may not have system rights to modify the file.
- You do not have the necessary network rights to perform the operation.
|