Doing Evaluation, problems!!!

binsys · Post by **binsys** » Mon May 19, 2008 3:50 am

I have so far liked the product very much, BUT - I am having a heck of a time getting everything imported from SourceSafe which we require.

Some projects require external .DLL's in order to compile, such as AjaxControlToolkit.dll or the like. When uploading a binary like this within a project to SourceSafe, no problem, but Vault 4.1.1 is stalling or failing on these, and is therefore unusable for us.

Am I getting this wrong? Tell me there is a workaround or a DB setting to correct this...

- h.

lbauer · Post by **lbauer** » Mon May 19, 2008 6:37 am

We'd like to take a look at your logs to determine what types of errors are being generated.

Zip up the import log or on the VSS import directory, and the server log that covers the time of the import and send them to support at SourceGear.com, Attn: Linda.

The Vault server log is in %windir%\temp\sgvault on the server machine.

binsys · Post by **binsys** » Mon May 19, 2008 3:47 pm

lbauer wrote:We'd like to take a look at your logs to determine what types of errors are being generated.

Zip up the import log or on the VSS import directory, and the server log that covers the time of the import and send them to support at SourceGear.com, Attn: Linda.

The Vault server log is in %windir%\temp\sgvault on the server machine.

TWO THINGS: 1) My first conclusion is that the folder structure of our existing SourceSafe database is broken beyond repair and all the projects will have to be re-organized... no sense to it at all...

2) Both the IDE pluggin and the import tool fail to add large .DLL's, .MSI's, or whatever other nonsense the former team has stuck in VSS - over the VPN - but work properly when importing a local copy of VSS into a local SQL Server (2005) instance of VAULT.

I am working on getting log access on the remote server. The Client seems to indicate there is a timeout, and retries every ten minutes until a failure occurs...

lbauer · Post by **lbauer** » Tue May 20, 2008 3:34 pm

If things are in a bad state in VSS, you might consider getting the latest code to a local drive, reorganizing the projects, then adding that file structure to Vault. Everything would be at version 1, but you could still keep the VSS database for reference as long as you needed it.

binsys · Post by **binsys** » Tue May 20, 2008 4:25 pm

lbauer wrote:If things are in a bad state in VSS, you might consider getting the latest code to a local drive, reorganizing the projects, then adding that file structure to Vault. Everything would be at version 1, but you could still keep the VSS database for reference as long as you needed it.

That is what I have done, but still no joy uploading large binaries to VAULT over the VPN, via import or VS2005 plugin. The server logs show CRC errors, all other applications working normally.

Did you get the logs I sent?

lbauer · Post by **lbauer** » Wed May 21, 2008 10:27 am

I got the server log, but I don't have a VSS import log. It should be in the import tool directory.

binsys · Post by **binsys** » Fri May 23, 2008 4:07 am

lbauer wrote:I got the server log, but I don't have a VSS import log. It should be in the import tool directory.

Import logs sent...

lbauer · Post by **lbauer** » Thu May 29, 2008 12:06 pm

Thanks.