SourceGear Support

Unfortunately no...

I don't get error messages from the admin page.. but the setting is not saved and when I view the log, I get that error I posted earlier

Thank you for your quick response. Yesterday I re-installed Vault server and proceeded with steps per your number TWO (2) I selected Windows Authentication for connecting to SQL Server. During the installation I was logged into the server as the active directory service account I needed the process ...

Hi, This error is occurring when I try to save my Find In Files flag to on. I've already referred to several of the other threads related to this feature. I've already upgraded my instance of vault server to 6.1 and verified my plug in urls are pointing to the right location. Sql Server DB is on ano...

I was able to work around this issue by adding these additional lines of code: WorkingFolder currentWorkingFolder = null; //Verify working folder exist for the file VaultClientFolder vaultFolder = ServerOperations.ProcessCommandListFolder(projectRepositoryPathWithoutCodeLine + "/branches/"...

I did my troubleshooting on the machines which were causing the exception to be thrown. I was able to checkout successfully on these machines using the Vault GUI client, Visual Studio 2010, and the command line tool. All test were performed with the machine users log in credentials to connect to the...

is anyone looking at this?

Just a bit of additional information.

I was able to successfully check out the offending file via the vault client as well as via visual studio with no issues.

I also used the command line to perform the checkout with no errors. No exceptions related to working folder settings

Beth, Yes, we're using the Fortress Visual Studio Enhanced Client integration. Here is the call I'm making in code. It's a very simple checkout on a .sln file log.Debug("Checking out the solution file started"); log.Debug("Vault Server Login"); GetOptions getOptions2 = new GetOpt...

We're encountering exceptions intermittently when the following code is executed: GetOptions getOptions2 = new GetOptions(); getOptions2.Recursive = true; log.Debug("Checking out : " + solutionfilePath); ServerOperations.ProcessCommandCheckout(new string[] { solutionfilePath }, true, true,...

Yes, I see the branch in the web client

Let me clarify, I mistyped the code... ServerOperations.ProcessCommandBranch(projectRepositoryPathTrunk, projectRepositoryPathBranch); VaultClientFolder vaultDirectory = ServerOperations.ProcessCommandListFolder(TopLeveBranchFolder, true); var _branchVersionID = vaultDirectory.Version; The branch is...

what should I call post branch to ensure that I get a Commit.

When I perform the ServerLogin operations I set

ServerOperations.client.AutoCommit = true;

before I call my processcommandbranch()

When I use the API to branch a directory, I'd then like to label that branch... I'm attempting to accomplish this by doing the following ServerOperations.ProcessCommandBranch(projectRepositoryPathWithCodeLine, targetBranchName); VaultClientFolder vaultDirectory = ServerOperations.ProcessCommandListF...

I'm having an issue with this as well. I really have no need for the customized fields and would like a more intuitive process of customizing the item tracking form in general.