Potentially serious errors or inconsistencies were found.

Dhominator · Post by **Dhominator** » Fri May 26, 2006 1:51 pm

Have run analyze /f twice and get the following output. Ran a test import, which seemed to work. Do get several interactive prompts with the same message during import "File or project not found".

Suggestions?

Analyze Visual SourceSafe Version 6.0d (Build 9848)
Database analysis in progress @ 5/26/06; 2:00p.
File or project not found
Analysis complete @ 5/26/06; 2:42p
Potentially serious errors or inconsistencies were found.

[edit]
above message is from the production vss server. have the hotfix installed on the vault server where i'm doing the imports.

/jhd

lbauer · Post by **lbauer** » Fri May 26, 2006 2:23 pm

Potentially serious errors or inconsistencies were found.

This indicates SourceSafe database corruption, which may or may not cause problems with the import. Ideally, we'd like a clean report from Analyze. The VSS Import Tool communicates with the VSS database via the SourceSafe automation component, and the automation component is sensitive to database corruption.

Were there any other errors regarding the import? I think there should be an Analyze log in the VSS directory. Here's information about Analyze errors:
http://support.microsoft.com/kb/152807/en-us

You could run analyze again, using -f and -c parameters.

Sometimes if Analyze doesn't clean things up satisfactorily, a VSS database archive and restore operation will.

Dhominator · Post by **Dhominator** » Sat May 27, 2006 1:52 pm

Sorry for the confusion... that is the entire contents of the analyze.log file.

I'll try the -c (compress) flag and see if it makes any difference.

[update]
same result with -f -c

/jhd

lbauer · Post by **lbauer** » Tue May 30, 2006 7:06 am

Thanks for the update. As I said earlier, "Potentially serious errors" may cause a problem with the import. An archive and restore may clean up some of the problems, or check with Microsoft SourceSafe support for other ways to deal with this error.

Dhominator · Post by **Dhominator** » Tue May 30, 2006 9:16 am

Ok, there are 2 vss dbs: 1) production, 2) import (export from production). The reports I've posted are for the production vss db. I ran analyze against the import vss db and it's clean.

If the import db is clean, should the import work?

Best,
/jhd

lbauer · Post by **lbauer** » Wed May 31, 2006 7:46 am

It has a better chance than if there is definitely database corruption in the VSS database.