SourceGear Support

lbauer wrote: Our code does catch the exception, so we need a way of sending it back to the server.

What do you mean by "sending it back to the server"?
Just rethrowing the exception will do I think (or not catching it at all).

CCNET communicates with the Vault Plugin and the plugin uses a history command to check the latest version in the repository. If the version has been updated, CCNET triggers a build. Then the plugin does a GET. Currently, if the GET fails, we have no way to stop CCNET from continuing with the build...

I'm more interested in the fact that the plugin continues in case of exceptions.
We don't need to run two services, so that is irrelevant.

Can somebody from SourceGear respond?

FYI: the problem seems to be gone when we shut down one of the services. Running without errors now for about a week. Before the error occurred a couple of times a day. Still very curious why Vault is continuouing in case of errors (and certainly when this might be caused by other situations like gr...

In a couple of days we will shut down one of the services. I'll let you know if that solves the errors.

What can you say about the fact that the plugin continues in case of a (login) exceptions?

I think it started recently when we started running two services, but I'm not sure.

We suspect the problem might be that we have two vault services running on the same database. Seems like the service is restarting sometimes (we also get session invalid messages in vault client). Multiple times the following can be found in the Vault log: ----11/29/2012 1:21:19 PM sgvaultsystem--()...

It just happened again (plugin is spamming the eventviewer with errors). The first error is however the following: 2012-11-28 11:53:43,908 [ProjectB] ERROR CruiseControl.NET [(null)] - An exception was encountered during the get latest operation. Exception: VaultServiceAPILib.VaultSoapException: 101...

We are using CCNET for continuous integration together with Vault for source control. CCNET : 1.8.2 Vault : Standard 6.0.1 The plugin from Sourcegear is used in CCNET (ccnet.vault.plugin.dll). We experience the following problem. After CCNET is running some time the plugin starts to generate errors ...

Your scenario is not the same as mine.
In your case you should branch from $/Shared/ to for example $/Branch/Shared/
And then check the files inside $/Branch/Shared/TestFolderA/

We tested with resetting cache etc. Does not make a difference.

In our source tree we have a root folder for some solutions. All solutions have the same shared folder containing some files (only the folder is shared, not the files inside). We created a branch from that root folder. Now the solutions in the branch still have the shared folder, but also all files ...

I get the same error, however it seems to take longer. ================================================= Client log: [2-11-2011 8:36:58] Beginning transaction [2-11-2011 8:36:59] Share $/PATH2 [2-11-2011 8:36:59] Ending the transaction [2-11-2011 8:39:11] Transaction failed [2-11-2011 8:38:27] An er...

This setting is not set.

Configured for Drive 1: 2046-4092
Configured for Drive 2: 4092-8184

Currently used: 6138 total.

SQL Server is on the same machine as Vault Server.