After a long time, sourcesafe will cause many problems, such as data loss, link loss, and file destruction in the sourcesafe database. When we use sourcesafe in our product group for less than a month, every time we enter sourcesafe as an administrator, We will prompt you to fix it. It is annoying. Although it has been planned to migrate to team foundation, but the test work is not completed, the migration will be delayed.
When I got off work yesterday, I really couldn't help it. I decided to fix sourcesafe. After running the repair command, you will go home directly. However, when I enter sourcesafe after work today, I find that I cannot enter it. The prompt "sourcesafe database is locked by Administrator" is always displayed. "The Help means that the database will be locked during restoration. As we all know, sourcesafe is fixedProgramUse a utility named analyze.exe. But the task manager did not find any trace of the analyze.exe program, nor did it see any related processes running. After a long time, the big guy was waiting for sourcesafe to start working.
The parameter entered in analyze.exe is the data directory. Maybe it can be found in the data directory, and a lock folder is found in the data directory, but there is no content in the lock folder, find the loggedin directory and inadvertently find a name called admin. look at the suffix of the LCK file. What kind of lock file should it be? Try to delete this file and sourcesafe will be able to enter.
I think the reason is probably that the power was down last night, and it was not fixed yet. The reason for this is still Admin. LCK.