SourceGear Support

Since I think it's safe to say after a 1.5 years of this not changing back we aren't going to see anything can we at least get obliterate to not render tree nodes that don't have anything in them? Right now we have to click through every node in the tree. If it at least just rendered the ones with s...

Thanks.

I see that 4.0.5 is released, but the website isn't updated. What is the download link?

The KB Article that talks about the release doesn't say:
http://support.sourcegear.com/viewtopic.php?t=8848

Any update on this? This has become so frustrating I can't even describe it. We have a user check-in a bunch of large files that shouldn't be in Vault and I'm spending half the day finding and obliterating them. It's to the point I'm going to start a .NET project to do this.

Works at my place... I'm not intending to invalidate what you say, but rather that it does work at some places at least... I wish I could suggest somethign to try, though... It was not working on 100% of the machines at our office. We had an outside company try it and several employees tried at hom...

We found that an uninstall of 4.0.3 and reinstall of it got things going again.

Between having to do this and the installer saying it's 4.0.2 this version feels like a 1.0.3 release not a 4.x. I'm really starting to miss 3.5.

Everyone in our office did the upgrade from 4.0.2 to 4.0.3. None of us can open projects that were bound with the 05 specific plug-in. We get an error "Package Load Failure" for the SourceGearLLC.VAultVsipClient.VaultVsipClient

I just upgraded our server to 4.0.3. I noticed when I downloaded the client installer from our server the installers readme screen says it's 4.0.2. I let the installer keep going and checked the about box in Vault client and it says 4.0.3 so it looks like the installer really was a 4.0.3 installer.

Will this work with Server 2003 64bit? We really need our Vault working that way and I'll take it any way I can get it.

Thanks.

SG support got back to me. It turned out I was running 3.5.0 client with 3.5.1 server and this is a 3.5.0 bug. A quick client update to 3.5.1 fixed it.

I'm going to email support I guess. This is really making it hard to work in Vault. I'll post an update when support emails me so if anyone else runs into this we have a thread about it.

Beth wrote:Something could be out of sync with your cache. Try Clearing the Client Side Cache and then restart Vault.

That didn't work. But I do get to reset all of my working folders now:)

I noticed the timestamps are wrong everywhere in Vault for me. No one else at my office sees this. My computers clock is correct. The servers clock is correct. Both are in the same time zone. From comparing the times on files with co-workers it appears I'm 6 hours off from them. 6 hours is my time z...

Can I vote again? We stopped using the obliterate while we wait for the old version to come back...

The "vote" doesn't sound good... doing a search on forms I see a lot of votes for this feature over the past couple of years. I guess we will check back in another year and see how the product progresses. Thanks.