SourceGear Support

Yes, our label implemenation changed for 2.0. They are now called "snapshots", as you figured out...

Yea, this is a dumb bug on our part. We plan to have a patch release out this week with an updated installer that works whether the hostname is fully qualified or not.

Yes, the VS.Net IDE will allow this. The only catch is that when you bring up the project in the IDE, it will continue to ask for you to login for each project you have in the solution, and only after you've hit cancel for each project will it bring up the dialog asking you to work disconnected. Whe...

Can each of you send me your email? I'm not able to reproduce this, and need to get more info from you.

Thanks,

Rather than zipping up the files to take home, install the Vault client on your home machine instead, and then do a Get from there. Our license allows you to login as the same user from anywhere. You would just want to make sure you check your files in before you switch locations - you can't undo a ...

There are a few things going on here, and a few mysteries: First of all, it would be good to figure out how the files got into an Unknown state. If a file exists on the local disk that Vault didn't retrieve, it is considered Unknown (we have on our TODO list to try to compare unknown files to the ac...

We are looking into this now. Each of you may want to send me contact info so I can email you to get more info (just click the "email" button below my profile to send it to me).

Thanks,

Unfortunately no - Vault itself does not. It is on our list, but didn't make 2.0. Visual Studio will allow you work off-line (and will simulate file checkouts) when integrated with Vault, but the Vault GUI client itself won't.

Jeff will have to give you the lowdown on what happens when you clear those tables - I seem to remember it not being a problem. But, I can verify that the session table does get cleared out properly in 2.0, and that a 2.0 upgrade clears out those tables. This was a bug that showed up when using the ...

The first step is to look in %temp%\vault_install.log, and see if there is anything meaningful in it.

Also, we'll need complete configuation information - which OS, what versio of IIS, whether it is the default web site, is SQL on the same machine, etc.

This sounds like a SourceOffSite question, rather than a Vault question? You should probably repost the question in the SOS forum...

Also, were you upgrading from a previous version of Vault? If so, which version? It might be the uninstall that is causing the problem...

Thanks for the report. We've had 1 other report of this since releasing Vault 1.0, but have not been able to reproduce it here. Can you send your complete server config (OS, version, service packs, etc), so we can try reproducing this again?

Thanks,

Yes, the ASPNET account shouldn't be involved, so it looks like a bug, but the workaround would be the same - choose a different account to run the Vault service under during the install. If you want to run Vault with the Network Service account, you'd have to then manually change that in IIS (and a...

Try to create/write a file in that folder from within your code, to see if it really is the permissions of the user you are running as, or whether it is something deeper in opslib.