- Visual SourceSafe reports a broken chain and recommends running a fix.
- But, the backup folder is not empty (because it just wrote an analysis log to it) so the fix won’t run.
- So, you delete the contents of the backup folder and re-run the fix.
- But, the database is in use (users are logged in) so the fix won’t run.
- So, you politely ask all the users to stop being productive for 5 minutes, while you run the fix.
- But, even with all users logged out, the stupid Analyzer still reports that files are locked and the fix won’t run.
- No (Owen, Mindscape, et al), you don’t have to upgrade/delete Visual SourceSafe!
- Go to Computer Management, System Tools, Shared Folders, Open Files
- Find and delete these three locks (being held open by Windows):
- Here’s the command line to run the fix:
- "C:\Program Files\Microsoft Visual SourceSafe\analyze.exe" -F -V3 -D "e:\vss\data"
Other related posts:
Teach Yourself Azure in 4 hours
Geek Post Monthly Newsletter Volume 2 Issue 10
Add a comment
Please note: comments that are inappropriate or promotional in nature will be deleted.
E-mail addresses are not displayed, but you must enter a valid e-mail address to confirm your comments.
Are you a registered Geekzone user? Login to have the fields below automatically filled in for you and to enable links in comments. If you have (or qualify to have) a Geekzone Blog then your comment will be automatically confirmed and shown in this blog post.