SourceGear Support

We are migrating from Vault 8 to Vault 10.2 and have successfully installed 10.2 (server and client) on a new server with its own SQL Server instance. We have upgraded and migrated the Vault 8 database and mounted it on the new server, and the Vault 10 client works correctly when installed on the ne...

Adding these roles appears to have solved the problem. I was able to log in, enter the new license key, and add a desktop shortcut. Also, the client app is now installed and works as expected.

Thanks!

While we already have a running instance of Vault Server 8 on one machine (a VM running Server 2012R2) with SQL Server 2014...I am basically starting over with installing this Vault Server 10.2 on a new Windows Server 2022 VM and a restored database (backed up from the old machine) into SQL Server 2...

I've completed the Vault Server installation...shows install was successful, including a successful upgrade of a database....and then says a web browser will be launched to log in and supply license key info. No browser is launched, and there is no shortcut created on the desktop for Vault Server lo...

Please disregard...it appears I was supplied a new server *without* IIS activated. Now that it's on, installation is proceeding.

Attempting first installation of Vault Standard Server (VaultServer64_10_2_0_1222.msi) on a new Windows Server 2022 system with IIS version 10. I immediately get this message and cannot continue at all... "SourceGear Vault Standard server 64-bit cannot be installed on systems with Internet Info...

I am logged in to a newly installed vault 8 Server as Admin. It is actually the second time for the install after completely uninstalling and removing the vault databases once. The 2nd install completed without any issues, but this time the Add Repository button appears to be disabled.

Turns out we had permissions issues with the SA login on the new SQL Server 2014 instance. Hopefully these are resolved now, as I was able to complete the first upgrade from 5.0.4 to 6.1.0. If I am ultimately upgrading to version 8, and if we have a current Vault Standard Maintenance plan in place, ...

I am continuing to have problems upgrading the Vault database. I have backed up the sgVault and sgMaster databases from the old (SQL2005) server and have now restored them to the new (SQL2014) server. Next I'm attempting to perform the upgrades by running the installations of Vault Server 6.1.0, the...

We are making progress with this process, and realize that a separate step here will be upgrading our Vault 5.0.4 database (multiple repositories) to Vault 8. Here are our sources and targets: Vault 5.0.4 pointing to SQL Server 2005 instance running on Windows Server 2003. Vault 8 pointing to SQL Se...

Same exact results. If you would like to see a copy of the error log, please advise on how to send it.

I'm upgrading from Vault 5.0.4 to 8.0 and need to have both versions of the client active on the same machine (Windows 8.1) while pointed to their respective servers (on different machines). Following guidance from other posts, I've moved all the files from the Vault 5.0.4 folder to a new folder to ...