SourceGear Support

When I log into Vault, it shows me the repository list in the attached picture below. How can it be that I have a negative file and folder count for XBLA? Please note that the Advanced Obliterate Client finds no deleted files/folders within this repository. According to Windows Explorer, that reposi...

Jeremy -- Happy to hear that you are also working on the memory problem. I didn’t realize that. I should let you know, however, that the memory problem apparently still exists in the updated plug-in that I just downloaded today. I'm still seeing a large memory allocation (up to 1.8 GB) when CCNet fi...

After recently branching, I too am seeing this same issue -- memory going through the roof when using the Vault plug-in for CCNet. What I don't get is why is memory calculated as tree size * number of CC.Net projects when one of the options within CCNet is to specify the SCC Folder name (which is ne...

I just completed my testing of the new plug-in and sent the result to you.

You should re-read the entire post. I think that I was clear that our build process (which is seperate from CCNet) uses command-line Vault where as our integration with CCNet uses the Vault plugin. Please note as well that we use CCNet only to trigger our build process. The CCNet and vault-plugin me...

Beth -- My understanding was that the offline discussion was for the CCNet plugin. However, I would like to keep the problem I reported originally (and just reiterated in my previous post) alive here. We are still having issues occasionally with our build process (which uses command-line Vault) with...

I will indeed follow up with the developer regarding the CCNet plugin. However, before I do so, I wanted to mention that I was able to mitigate the CCNet concurrency issue by splitting my projects into logical Queues . The way I have it configured now, there will never be more than 10 concurrent Vau...

No problem -- I should have realized that you were talking about command-line Vault. The documentation for these blocks looks so similar that I didn't even notice. Funny thing is that the Vault plugin does not complain about the existence of the superfluous options, so I'm just leaving them (as it m...

Again, I am using the CCNet Vault plugin for checking on source changes in Vault, not command-line Vault. It is our build process (often triggered by CCNet) that uses command-line Vault. When 5:00am rolls around, the Vault plugin usually does not detect any source code changes so no actual builds ar...

Every Sunday morning at 4:45am, our Vault server and Build machine reboot. But this shouldn't be a problem since we have CCNet turned off during the night until 5:00am. But once the CCNet projects started up this morning, about half of our 26 projects ended up in Exception status with the following ...

No, I missed those settings when configuring the Vault plugin for CCNet. I've since updated my configuration and am using 5 for pollRetryAttempts and 10 for pollRetryWait . Those settings look promising. I looked again in the Vault server log, and recently found the following error (which repeated s...

Yes -- when I mentioned "Vault CCNet plugin" in my previous post, that's what I was referring to. Though it does not require re-login, all CCNet projects will log in at the exact same time if restarting CCNet service. Also, some of the failures we've seen are with our build service, which ...

We've been seeing this off and on at least since we upgraded to Vault 4.x (over 6 months ago). However, we've been seeing it more frequently ever since we started using CCNet for Continuous Integration builds (using either the vault command-line and vault CCNet plugin). The issue definitely seems to...

Again, as mentioned previously, the server log does not contain this error. I've also been able to reproduce this same issue while being on the Vault server itself.

What could be causing this problem?

Which suggestion are you referring to? The one about adjusting the HKEY_CURRENT_USER\Software\SourceGear\Vault\Client\Settings\ServiceRequestTimeoutSeconds registry key or the disabling the client Use Expect: 100-Continue Headers option? I can't see how the registry key can help since, as the previo...