PRB: Message "Error Writing to File" When Checking In File (155631)


The information in this article applies to:

  • Microsoft Visual SourceSafe for Windows 5.0
  • Microsoft Visual SourceSafe for Windows 6.0
  • Microsoft Visual SourceSafe, 16-bit, for Windows 4.0
  • Microsoft Visual SourceSafe, 32-bit, for Windows 4.0
  • Microsoft Visual SourceSafe, 16-bit, for Windows 4.0a
  • Microsoft Visual SourceSafe, 32-bit, for Windows 4.0a
  • Microsoft SourceSafe for Windows 3.04
  • Microsoft SourceSafe for Windows 3.1
This article was previously published under Q155631

SUMMARY

When checking in a File to the SourceSafe Database, SourceSafe might generate the message:
Error Writing to File

MORE INFORMATION

This error may occur for several reasons:

  1. If there is no file listed after the error message, it may be caused by a corrupt Status.dat.
  2. If it occurs three times in a row on a Novell Network, there is probably no valid Owner for the file.
  3. 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 later.
  4. 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.
  5. 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.
  6. You do not have the necessary network rights to perform the operation.
Modification Type:MajorLast Reviewed:5/12/2003
Keywords:kberrmsg kbprb KB155631
©2002 Microsoft Corporation. All rights reserved.