VSS Import Process Fails Halfway Through

cvanderheide · Post by **cvanderheide** » Thu Jul 12, 2007 1:29 pm

My company has been evaluating and testing Vault to replace our Programming department's SourceSafe database for source code. I've been attempting to perform a test conversion of a copy of our SS DB as a "dry run" to find potential issues before attemping the actual conversion of our production DB.

After running through the import and attempting to spot check a number of files using the client, I noticed that several folders & projects were empty of files that should not have been. A little poking around reveals that the files seem to be successfully converted up to a certain point - after that, the conversion seems to have stopped in its tracks, and only the only files that exist in subsequent folders are links to shared files that exist in the part that was successfully converted.

I looked into the import log and eventually found the point where it changes from "Transaction suceeded." messages to a massive, unending series of exceptions.

Code: Select all

Exception: System.Web.Services.Protocols.SoapException: Server was unable to process request.

Anyone know what might have caused this?

I'm thinking that something bad must have happened to the web service or IIS somehow, but I'm not sure what? I've been able to connect to Vault fine with the Admin tool or client UI without rebooting so nothing died completely, but after this point the rest of the log is pretty much all similar exceptions.

See attached text file for example Exception message & trace from the log. The log contains many pages of this sort of exception after the point of failure.

Has anyone else ever seen this?

cvanderheide · Post by **cvanderheide** » Thu Jul 12, 2007 1:32 pm

Other details:
1) Vault is version 3.5.2
2) Vault, SourceSafe and the Import are all run on the same test server which is not being used for any other purpose at the moment.

Beth · Post by **Beth** » Tue Jul 17, 2007 1:01 pm

Was that message from the Vault Server Log or the Import log? (Import log is located in C:\Program Files\SourceGear\SourceSafe Import Tool.)

Did you review our KB articles in importing from VSS?

Tips for a Successful VSS Import
Importing a solution or project that uses IDE Integration
Options for a VSS Import

What is most likely to help you here is to not import it all at once, but instead to import in parts. Try a small portion first and see if you get the same error.

cvanderheide · Post by **cvanderheide** » Thu Jul 19, 2007 1:37 pm

The messages appeared in the Import Tool logs.

We will consider importing in sections, but we have a lot of shares between projects, so we'll have to look into the special import tool.

Beth · Post by **Beth** » Thu Jul 19, 2007 5:25 pm

If you want, you can send me an email and I can give you a link to the tool mentioned.

Will you be going to Vault 4.x after the import? It might be worth it to consider doing the import on a newer version too. Just let me know before you make a switch.

cvanderheide · Post by **cvanderheide** » Fri Jul 20, 2007 7:58 am

Beth wrote:If you want, you can send me an email and I can give you a link to the tool mentioned.

Will you be going to Vault 4.x after the import? It might be worth it to consider doing the import on a newer version too. Just let me know before you make a switch.

Beth: Thanks. I sent the email to the support@sourcegear.com address. We will probably not be moving to 4 at this point; many of my company's customers are <ADVERTISEMENT SPAM> companies which are governed by federal regulations, which means a lot of things, but one thing it means is they have the potential to audit our company's procedures, one of which being we validate all 3rd-party software tools we use. We did the original checks and testing with 3.2, to move to another version would require re-doing all of the associated paperwork.