SourceGear Support

Hi, A user of vault got the following message when trying to do a get latest from a Vault client: "The working folder state information for [valid path] is incompatible with this version of Vault. Please choose a different working folder path. The specific compatibility exception was: Wait for ...

To answer some of the questions: 1) This is the Windows GUI. 2) Not sure if this existed before, but in the Win Client, I can't recall anyone having this issue. 3) The users were checking out the file, not the folder 4) No, folder security is not enabled. 5) No, the files are not shared. 6) Only the...

Hi, We recently upgraded our client and server to versions 2.0.6. So far, there have been 3 complaints that after checking in a file, the client insists that it is still exclusivly checked out. Shuting down the client and then restarted it seems to work, and then on future check out/ins, everything ...

Just to clarify, when you say that

jeremy_sg wrote:Vault hasn't added any specific support for Client Certificates.

you mean that Vault will not work with client certificates, or that it does, but Vault doesn't do anything additional with it (like notify the user about using CCs)??

Gavin.

Forgot to add our current server/Vault setup:

Vault 2.0.3 (clients and server)
Win Server 2003 Standard Edition (IIS 6.0)

We plan to upgrade to 2.0.7 within a few days.

Gavin.

Hi,

I am having trouble finding out if vault can use client certificates (via IIS making client certificates mandatory). And if Vault does support this, which version did it start to do so?

Gavin.

Hi, Does Vault 'monitor' the working directory, and temporaily lock any files? For example, our bin directories are not in Vault, but when we build a solution, VS.NET complains about binaries being locked (as we have dependencies amongst projects within our solutions). This seems to be our biggest i...

Does that imply that importing from VSS does not work if you intend to use the VS.NET IDE integration?

Gavin.

The answer to you questions: We are typically doing a 'get latest' with the Vault GUI, and then using the integration with VS.NET. We got the files into Vault by getting latest in VSS, stripping out the .vss files, and then loading via the Vault GUI into Vault. We realize that we lost our 'history' ...

also, another typical build error is:

- Could not copy temporary files to the output directory.

also, another typical build error is:

- Could not copy temporary files to the output directory.

We are using VS 2003 along with Vault 2.0.3 in a trial right now and are experiencing a number of issues when we try to build our solutions. We have several solutions each with several projects. We get quite a few build errors such as: -The type or namespace name 'xxxx' could not be found (are you m...

This is Vault version 2.03 BTW I may have answered my own question, if someone could confirm that this solution doesn't cause future problems: I noticed that the MSSCCPRJ.SCC file was not in SourceSafe, so therefore not in Vault after importing. When I added this to Vault, other developers when they...

Hi, after doing a typical import from VSS to vault, I try the following steps: -Login to vault client and 'get latest' -open from Visual Studio - at this point I get a message saying that the solution appears to look like it is under source control, but it isn't sure -I go to File/Source Control/Cha...