Automatic Repair of VSS errors

Company project development Source code VSS has been used for management, and vss8.0 (vss2005) has been used for vss6.0. In the past two years, we encountered some major and minor problems:
1: migrate the VSS service. This is easy to do. Just copy the entire VSS directory and add the corresponding permissions.
2: Fixed VSS errors,
Due to various reasons (vs error, vs forced termination, network error, VSS server startup exception, shutdown, etc.), the VSS service will always have some problems within one working day, open from vs after an error occurs in VSS Program Sometimes it will be slow or abnormal, so it must be fixed. Due to its superficial understanding of VSS, it has gone through several stages to solve this problem.
A. After Microsoft Visual sourcesafe administration is run, if an error occurs, you will be prompted to check and fix it. Generally, you can use this check.
Running time: Irregular
In fact, there is a problem here. It should only check the error and not fix the error.
B. Manually Run batch file repair
Every time method A needs to run manually, it is quite troublesome, and a batch of processing files is made. Click execute. The content of the batch file is as follows:

"C: \ Program Files \ Microsoft Visual sourcesafe \ analyze.exe"-f e: \ VSS \ data
You can use analyze.exe in the DOS command.

Running time: once a week. Make sure that VSS is not used by all users.
C. Automatic Repair
Automatic Running of VSS repair tasks using the automatic task execution tool (which is easy to use and powerful)
Running time: several times in a week, set to run at a.m. (depending on the actual situation)
After running for a few months, I recently found a problem. The repair failed. The error is as follows:

Visual sourcesafe analyze version 8.0
Copyright (c) Microsoft Corporation. All rights reserved.

Database Analysis in progress @ 07-10-06; 8: 11.
File E: \ VSS \ data \ status. dat is already open
Cannot rebuild the database while visual sourcesafe is being run. Make sure all users have exited sourcesafe and try again.
Analysis Complete @ 07-10-06; 8: 11

But check the user does not find a user connected to VSS. After Google, we couldn't find a good solution. We had to restart the VSS service, so we could fix it without reporting this error. It is estimated that the reason is the cache.
After finding the problem, modify the automatically running batch file content, stop the VSS service, fix the VSS, and start the VSS service. The batch content is as follows:

net stop ssservice
"C: \ Program Files \ Microsoft Visual sourcesafe \ analyze.exe"-f e: \ VSS \ data
Net start ssservice
it has been confirmed feasible. However, there is another problem. If an exception occurs during the analysis, the VSS service will not be able to start. Make all the adjustments and restart the VSS service before fixing the issue. The batch file content is as follows:
net stop ssservice
Net start ssservice
"C: \ Program Files \ Microsoft Visual sourcesafe \ analyze.exe"-f e: \ VSS \ data
the last point is that the VSS service cannot be provided when the VSS service is repaired because it must be used for idle time.

Note:
ReferencesArticle:
Http://www.cnblogs.com/kaima/archive/2007/06/26/693268.html
Http://www.cnblogs.com/LeeWenjie/archive/2006/11/24/509498.html
Http://www.cnblogs.com/RChen/archive/2006/01/12/315861.html
Http://support.microsoft.com/kb/279191/zh-cn

For the first time, I wrote a complete article related to technology. The document is not well written and the organization is unclear. Sorry.