Microsoft KB Archive/167290

= How To Enable Visual SourceSafe Locking =

Article ID: 167290

Article Last Modified on 7/1/2004

-

APPLIES TO


 * Microsoft Visual SourceSafe 5.0 Standard Edition
 * Microsoft Visual SourceSafe 6.0 Standard Edition
 * Microsoft Visual SourceSafe 4.0 Standard Edition
 * Microsoft Visual SourceSafe 4.0 Standard Edition
 * Microsoft Visual SourceSafe 4.0a
 * Microsoft Visual SourceSafe 4.0a

-



This article was previously published under Q167290



SUMMARY
Normally, Visual SourceSafe allows the Operating System to handle the file locking. However, if there is a lot of network traffic or high latency, file errors can occur. You can also use the Visual SourceSafe application to handle file locking. When Visual SourceSafe locking is enabled, Visual SourceSafe handles all of the file locking for itself.



MORE INFORMATION
You can use the Visual SourceSafe program called TESTLOCK to check to see if you need to enable Visual SourceSafe locking. TESTLOCK is located in the Dos and Win32 directories under the Visual SourceSafe directory on the server.

After you start TESTLOCK on multiple computers, it will tell you whether it is safe to use native locking. To run TESTLOCK you must give it a parameter of a shared directory on a server or some other computer, however, all the machines that will run TESTLOCK must have full access to the shared location. The command might look like the following:

TESTLOCK F:\VSS\TEMP

If TESTLOCK reports that you must enable Visual SourceSafe locking, you may do so by adding the following to your Visual SourceSafe database's Srcsafe.ini file:

Lock_Mode=Lockfile

Make sure that there is a LOCKS directory in the DATA subdirectory and have all the Visual SourceSafe users restart Visual SourceSafe after you make the change.

It is recommended that if you are using Macintosh and Unix clients and/or servers that you enable Visual SourceSafe locking.

