SourceGear Support

Any ideas yet? I'm getting by for now by doing all admin on the server, would like the remote access back. The bug has been found and fixed, so things should be working in Fortress 1.1.2 when it is released. In the meantime, a workaround could probably be put in place in order to give you access to...

How do I get groups in the public and public/private groups dialog for project tracking to show up? Global groups cannot be used to set Public Access Only permissions. Only project groups for that specific project can. This is by design. If you'd like, i can log a feature request that other groups ...

This state has been caused by the following bug. In versions prior to 1.0.5 it was possible to set the external-user to active rather than inactive. This should have been harmless (except for the fact that they now use an extra license, which is unnecessary). In versions after 1.0.5, however, it can...

Vault 4.0.5 introduces the Change Vault Bindings dialog for binding projects, unbinding projects, and correcting binding errors. If you are binding multiple projects, or a solution which contains multiple projects, you will be asked to map a working folder for the Deepest Common Ancestor of all of t...

[quote="lassevk"]I'd very much like to know what to look for so that I can upgrade.[/quote] To re-bind the solution, we now have a recomended set of steps at the following KB article: http://support.sourcegear.com/viewtopic.php?t=7937 Please try re-binding using those steps and let us know...

For re-binding the solution, we have a recomended set of steps at the following KB article: http://support.sourcegear.com/viewtopic.php?t=7937 Please try re-binding using those steps and let us know if you still get the same error message. Your error is one that we had not yet seen in-house, but ano...

The solution needs to be re-bound for use with the 2005 Client. Unfortunately, this process is not automatic and needs to be performed manually. The steps at the following KB article will guide you through the process.

http://support.sourcegear.com/viewtopic.php?t=7937

Thanks for your patience.

Please try out the steps listed on this new KB article and let us know how it turns out:

http://support.sourcegear.com/viewtopic.php?t=7937

For users who have projects that were bound to Vault using the SourceGear Vault Classic Client and now wish to use the SourceGear Vault Visual Studio Enhanced Client, the solution will need to be un-bound using the Classic Client and then re-bound using the Visual Studio Enhanced Client (note, these...

I'm guessing that since the existing solution was originally bound using the 2003 compatible client, that's the only client that can open it. It will probably be a matter of Unbinding the solution and then Binding it again using the 2005 client.