SourceGear Support

I found another post about sgmaster being in single user mode. I stopped the sgvault web site I started SQL server management studio and opened the object expolorer I noted sgmaster was in single user mode I followed these instructions: https://docs.microsoft.com/en-us/sql/relational-databases/datab...

Platform: - Windows server 2016 standard, 10.0.14393 - SQL Server 2017 Everything was working fine since 2019. This weekend I took a backup of the database through the Vault web UI and now all logins fail with "The username or password supplied is invalid." Checked c:\windows\temp\sgvault\...

It is grayed out, I assume because bug tracking integration is not enabled (see attached). The application is one Yaskawa sells to its customers. We are looking to recommend SGVault to our customers that need a source control solution. Our product name is "MotionWorksIEC" A full version wi...

We are using Vault standard 10.0.2 (936) The repository settings have "Bug tracking Application" set to "none" and the "Require check in comments" checked. We are using an application with SCC integration. On operations that create a new folder, we get the dialog "...

Ok, I followed my procedure with the install of VSS 2005 on Windows server 2016 and there were no problems. I have brought the smallest VSS database over and analyze found no problems.

Next I have to decide between Import or handoff. I will need to do some more reading.

Ok looks like I need VSS 2005. I found posts saying that VSS 2005 can run on Windows10 64 bit with WOW and the VSS 2005 update. I think the following install procedure will work: Install windows feature .NET framework 3.5 (including .NET 2.0 and 3.0) Be sure that WOW is enabled if a 64 bit OS Instal...

I am wanting to move from, and decommission, a windows server 2003 R2 machine with VSS 6.0d (build 9848) and SourceOffSite 4.2. I want to move to Windows server 2016, 64 bit, running Vault 10 Standard. I understand I can create new repos with Get, import the VSS repo, or use Handoff. The developers ...

I think this is some sort of permissions issue. Installed Vault standard on Windows server 2016, 64 bit with IIS Navigation to host/vaultservice/admin results in the page: HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the p...

Turns out I had to rename a registry key name, but not the value. I changed reg key name: HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders\SourceGear Vault Classic Client to HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders\SourceGear Vault and th...

We have an older application that supports SCC integration and works with SourceOffSite 4.2.x (yes this is an ancient version). I am attempting to use this application with the latest version of Vault. The application allows me to select a "Source Code Control (SCC) system". The drop down ...