SourceGear Support

Using Vault Client & Server v4.12. Typical scenario: A developer needs to indicate the Vault location by email to some co-workers. He then nevigates in the Vault folder tree (using Vault client), found the solution file, right clicked on the file an happily selected "properties". Then ...

Installation SUCCESSFUL. It was the sgmaster database that I forgot to drop before simulating a a fresh Vault Server installation. This time, no more DB Error, no more HttpException. I suppose that the HttpException I encountered at the very 1st installation was an error due to the prepration of Win...

I think when I uninstalled Vault Server 4.12, I answered keep DB. Now I have dropped BOTH sgvault and sgmaster. These two DBs are now guaranteed to disappear from the server. I am currently restoring the sgvault DB from v3.53 and will reinstall Vault Server 4.12 and will tell it to re-use existing D...

Oh, I didn't notice Vault 4x now adds a new DB named sgmaster. I didn't drop it. I only restored the sgvault DB. May be this is the reason of the DB failure?

Hi, This is a second attempt to install Vault Server 4.12 before production deployment. On my first try, the installation went Ok but I got HttpException when trying to connect to the Admin Web Client. The error was reported here: http://support.sourcegear.com/viewtopic.php?f=22&t=10619 Then I u...

I am trying the Vault Web Admin 4.12. There are some differences with the former Vault Admin Tool I can't replicate: 1. How to assign permission on a specific folder to a group? 2. Group Edit: the list of the users on the left pane also show inactive users. How to display only active users? 3. User ...

Thanks for the links. Now it appear much clearer. I read through several releases notes but still missed these links. May be it would be better to mention these in a permanent section of the release note?

Hi, Excerpted from Release Notes for Vault 4.1.0: The two IDE clients have been renamed. The "Visual Studio 2003 Compatible Client", will now be know as the "Classic Client", since it offers support in more Visual Studio versions than 2003, and supports more IDEs than just Visual...

Hi, Testing Vault Server 4.12 currently. I would like to clean up some project folders by obliterating deteled items. The Web Admin only allow to see items directly within the folder. Each time I need to check EACH of the items to obliterate. It is quite time consuming to walk through to all subfold...

Thanks for all the info and also to Balthazor for bringing the DLL date change issue.

One more question: if the branched file is mergeable (text based) would that still take the same amount of DB storage space than the original file? As if it was added as new file?

I have uninstalled Vault Server and re-installed 4.12 again. This time I could open the admin page OK. So now I can continue the evaluation.

In the meantime, can you reproduce the test scenario I made above to confirm?

More info, if I open the page:
http://(ComputerName)/VaultService/Admin/Help.aspx

Then the "Vault and Fortress" help page is displayed. So is the web server working OK?

ASP.NET v2.0.50727 was already allowed in Web Service Extensions. I rebooted the server just in case. Then opened the link to Vault Web Admin (Start Menu / SourceGear Vault / Admin Web Client) The very first time: I got the error URL displayed in browser = http://(ComputerName)/VaultService/admin/ S...

Just reran the Vault 4.12 installer gain. This time there is no DB conversion dialogs. The install was completed fairly quickly and the Vault Admin Tool is available in Start Menu / SourceGear Vault. Ran the Admin Tool, login (server = localhost) and got same error message. Then I manually grant the...

Any update? Or may be can you just answer to Q3 which is pure Vault technical question. Thanks.