SourceGear Support

As a long-time (and very frustrated!) SourceSafe user the transition to SourceGear Vault with its close cohesion to the SourceSafe way of doing things was remarkably simple. If "Out Of The Box" is an apt description for its ease of use and provision of an excellent transition process then ...

Screenshot. During this transaction the GUI was locked (with hourglass cursor).

I've been working with Vault for some time so I've been used to its behaviour. However something seems to have changed recently, perhaps someone can suggest a fix. When I check in files, the actual transaction uses warp speed. However the Vault GUI then shows a busy cursor, and the GUI can be locked...

I fixed this problem.

I downloaded and ran the 32bit server version. It installed flawlessly.

There is obviously a problem with the 64bit version.

I'm trying to install server v10 on a new PC. This is a Windows Server 2019 server, with SQL Server 2019. Just after starting the installation I am greeted with a failure popup, which gives no clue about what caused the failure. 20210212 1325 Image 001.png Can this be resolved? I downloaded a freshc...

Adding this keyword expansion as a feature request doesn't appear to have had a response from the developers. That's fine, I've worked in development teams long enough to know such changes might not produce the desired result so I'm not moaning :). However, as presented earlier it would entail chang...

Hi Tonya, Thanks for your reply. Problem is now resolved. One minor difference to your instructions - ASP.NET 4.6 not listed, so I used ASP.NET 4.7 and that worked fine. Also, my apologies for inclusion of materials not related to this issue - I simply did a web page save and obviously that brought ...

I have Vault installed and working well on a Windows Server 2016 system. I am currently trying to port this to a new Windows Server 2019 system. Whilst the installation goes well, when I attempt to access the Vault control panel I am met with HTTP Error 500.19 - Internal server error. The SQL Server...

I am also experiencing this exact same issue, on a new Windows Server 2019 system. I have Vault server working perfectly on a Windows Server 2016 system, which I am trying to replace.

Should I raise a call to support for this?

In any case, in your last post, I believe this suggestion is something new. Just to clarify, are you're asking for a checkbox option during the commit dialog to skip KW expansion during this commit? Please ignore that last comment, I was spouting gibberish. The ability to limit the number of histor...

No that is not available. I'll add this as a feature request. As a brute-force work around, at this time any unwanted expanded items would need to be trimmed from the file before it is committed back to the Vault server. Thanks Jeff. I tend to submit in-progress work frequently, as in daily. With h...

I'm not sure whether this is already available.

It would be useful if the history keyword had an option to limit the number of history records to report. At present it seems to be an all or nothing deal, but for most purposes only the most recent change(s) are needed.

Thanks Tonya. Problem fixed - I deselected the repository cache option on the options dialog.

I have been using Vault 9 for a long time. Yesterday I got around to replacing it with Vault 10. I have several Windows 10 PC's and a Windows 2016 server. All working as expected except on one PC (which was working fine with Vault 9). What happens is after logging onto the server and confirming the ...

I currently have Vault V9 installed. Is there anything to be wary of if I install v10?