SourceGear Support

Hi Jeff, Sorry if my 10/31 reply wasn't clear, but yeah, we're still mystified by the CheckSum error problem during the VSS imports. Item A) We're not importing across a network--the VSS dbs that we archive from are restored into a new separate VSS db that's also on the vault server, Analyze.exe'd, ...

Got anything for me yet guys? Been a week, and we're still in that "wary of imports" frame of mind...

Good morning! The import to a blank repository was sucessful for me as well. So that means our main repository has a problem though? Hmm...any type of diagnostics we could run other than debug mode (this hadn't revealed anything extra in the log when I first encountered the problem). Thanks, --jdavidi

Hi Jeff, I will try the import on a blank repository this evening. As for the VSS Import issue with the FileCheckSum errors, yes we would really like an explanation/workaround if possible. We're holding up our import schedule because we're afraid of what it might do to our live repository. The Impor...

Hi Jeff,

I have the vfe file available that we could start with--it's 4.5 MB. What's the best way to get that up to you guys?

If that's not enough, I could rerun the export after hours this evening and get those log sets to you.

Thanks very much!

--jdavidi

All errors mentioned in the summary section of my 10/21/06 posting above still happen after the v3.5.1 upgrade.

Please advise?

Thanks,

--jdavidi

We're planning to upgrade this weekend; I will let you know the results.

Thanks,

--jdavidi

I've thrown every trick I know of at getting this particular import to work, but I hit various roadblocks in the form of errors. I'll start at beginning; we exported part of our VSS database last week (following all recommendations) and imported it to a clean repository just fine. This has been up a...

I should add that I couldn't find anything in neither the Import/Export log nor the server log with regard to the error.

Good morning,

Using v3.5.0:
I exported a folder with the Import/Export utility (about 6700 transactions total), but when trying to import it into another repository (same server), the app crashes with an object reference error (attached). Any ideas?

About 40 hours of the following pattern of statements (I didn't have debug logging enabled at the time): Login SSL Disabled VaultFileUpload.aspx encountered: FailFileInvalidCheckSum SSL Disabled VaultFileUpload.aspx encountered: FailFileInvalidCheckSum SSL Disabled VaultFileUpload.aspx encountered: ...

Hi again, Yes, we've followed those articles' recommendations for all of the mock conversions we've performed over the past few months, but this was the first time we got any "unhandled" exceptions. We do use Visual Studio integration, but I have a script I plan to run on the imported repo...

So we ended up finding out that indeed we did not get a full import, at least history-wise. We can't find evidence of missing files, but it's more as though we get history up to a certain random point for each file (and sometimes we get all the history). Plan is to scrap the repository this evening ...

Yes, FileManager.cs (plus the other 20,000 files) are definitely now in Vault (as are his particular 9 revision's worth of history).

And our SourceSafe databases are safe, and they "passed" a run of the archaic Analyze utility before the Vault import started.

Hi Beth, I couldn't find those exported/processed files number to compare, but the import log is...interesting to say the least. It seems like it created all 1,000 or so folders that we had, but then there's one of these entries for seemingly every single file in the repository that it tried to impo...