views:

975

answers:

6

VSS is resuming it's sabotage of my repository again. The repair command won't let me repair, the lock VSS doesn't seem to affect currently logged in users-- and it isn't a user, its claiming the only person logged in is admin (via the VSS admin tool!) and I have already closed all instances of the VSS admin tool and client.

A: 

Write a mail to everyone:

Subject: VSS Emergency

Body: Everyone is asked to disconnect immediately from VSS. This is not a drill. I repeat: this is not a drill.

User
ha ha. I sent the email to the administrator-- the only person logged in. That was me. I told my self I didn't have the answer, so please contact the administrator. That put me into an infinite loop I may never get out of.
MatthewMartin
A: 

Reboot the machine and re-try.

Bravax
+2  A: 

In computer management, close all the sessions and open files. It's drastic, but that is the only way I found to fix it. You also might want to close the share temporarily.

Josh
A: 

Close also all Visual Studio instances since these are also (or can be) clients of Visual Source Safe.

Andrei Rinea
A: 

I had the same problem and even after following the steps in the answer above, it did not go away until I stopped the SQLWriter (Sql Server VSS Writer) and SSService (Visual SourceSafe LAN Service) services.

A: 

stopping SSService (Visual SourceSafe LAN Service) worked for me, thanks.

it saved lot of time and confusions...

Mahavir Shah