SourceGear Support

We are getting an error running the command line client version 5.0.3.18802. Can you tell us why it may be occurring? Below is the client output and attached is the server log. <vault> <!--An error occurred reading from the download stream ("The operation has timed out."), retrying...--> <...

We are using the Vault Command line client version 5.0.3.18802. We are getting an error when running it but the result is still successful. Please can you make it return the correct error status? Here is a snippet of the output: <vault> <!--An error occurred reading from the download stream ("T...

Jeff, Thanks for the candid response. As a software developer I totally understand the process of managing software change. To get a little clearer on our need for Copy Label... Its not so much a perpetual label, though thats a view that fits how we use it to some extent - the labels are required to...

Jeff, This thread has been going a long time - 6 years I think. So VS 2010 issues are not whats in the way of providing this feature. It just hasn't been considered important enough. And its only a part of what I consider the missing features in Vault to make it a top class industrial strength VCS. ...

We are using Vault 5.0.3. We cannot find a way to copy a label. Is this truly still not in Vault after all these years? The alternative suggested is branching and merging back. Branching is messy because its not a linked branch. It becomes a completely separate development stream - separate history,...

Thanks Jeff for that clear response and indication of applying some resource soon to make the Merge Tool enhancements. If you would like a beta customer my hand is up!

From our perspective version 5 had few useful enhancements, and the main one - ShelveSets - has major useability issues. I presume that ShelveSets were very difficult to implement and thus sucked too much resource. Also the suggestions in this thread would be extremely useful for ANYONE using the me...

Visual Studio 2008 SP1 all latest Windows Updates
C/C++ native project

No it was not. No dialogs. Thats the whole point. This is how it was: 4.1.3 offline behaviour had the follow characteristics: 1. When a file with state NotCheckedOut+ReadOnlyAttribute was opened in Visual Studio, Visual Studio’s titlebar highlighted the file’s state as (ReadOnly). 2. Visual Studio d...

We are using the Vault Enhanced Client. Its not an option to make them writeable. The fact they are made writeable by Vault, in 4.1.3, was how the developer distinguished the files that needed to be checked in. In general we use the Check Out, edit , Commit development style and its a policy to make...

In 4.1.3 when offline, but bound to Vault, a read-only file was editable and when you built a solution, it wrote it to the disk. In 5.0.3 when offline or online, bound to Vault, a read-only file is editable and when you build a solution, it writes it to the disk. Then you GetLatestVersion on a file ...

Note that there was a blue-screen of death immediately preceeding the onset of this issue. So we presume that that caused the corruption of the file. It was almost the very first thing done on Monday morning after a re-boot. Opened up email, spent 10 mins reading the email. Started Visual Studio 200...

Hi Beth,

We've fixed it.

VsipClientProjectSettings.xml in the VsipSccClient folder in the cache directory was full of blanks. No legible text.

We deleted the file and it now works fine.

Thanks for your help

There is nothing at a high level about this machine that is special! But of course something is different. Same OS as others, same hardware, same VS, all using Enhanced Client, etc.

VS Install has now finished. Vault has been re-installed. It still has the same error.

Hi, We have a machine that now throws this exception everytime any project is opened in Visual Studio: Failed to register project <project> with SourceGear Vault Visual Studio Enhanced Client. The type initializer for 'SourceGearLC.VaultVsipClient.RepositorySettings' threw an exception. The server l...