SourceGear Support

Will the Full VSS Import tool import to the 64bit version of Vault?

I wish to upgrade to 5.0.4 from 5.0.3 and would like to block the older clients from accessing the vault server. Is there a method for this?

thanks

Mike

Ok, thanks for the info. We will keep it completely seperate, database and app. Will bring up in a VM environment...


thx

I wanted to test out the new Fortress 2 Beta product. However we currently run Vault 4.1.3. Can I take a backup of that and restore it to another SQL Server 2005 and then load the Fortress 2 Beta product? Will it upgrade the Vault 4.1.3 database righ there or do I have to load Vault 5 Beta and then ...

I need to verify that Vault 4.1.2 supports SQL Server 2005 running SP2.

Thanks

MIke

We imported serval VSS databases and we are using all the latest files based on the best notes from you. We have a system setup only for importing these databases. The VSS import says it completes but says there are 408 errors all related to the labels. See below. What does this mean? Label Verifica...

Is there documentation on the proper way to restore a Vault server (3.5.2)? Our plan was to just start over and reinstall the 3.5.2 server and get that all up and running and then use SQL to restore the database from the backup. I know that is very high level but anything you can think of I might be...

What binaries do you have available for Unix /Linux?

Are there any notes on the best way to set this up. How do you make the CLC in Linux remember logon information to the repo?

Thanks

Mike

I found that if you change the Vault option for Check In --> Check In unchanged files --> to Check In instead of Undo Check Out our Xilinx tool says the files haven't been changed. So my question is now what is different about this option. Setting this option takes more time and creates more version...

We use FPGA tools such as Xilinx. We used VSS in the past with Xilinx with no issues but now after migrating to Vault Xilinx is reporting files changes after checking them in to Vault 3.5.1. We did see that keyword expansion was on for the repository and the $Header was being changed. Created a new ...