vaultbranch commit failed

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Stoive
Posts: 3
Joined: Wed Oct 10, 2007 5:44 am

vaultbranch commit failed

Post by Stoive » Wed Oct 10, 2007 6:26 am

I'm attempting to use the vaultbranch NAnt task, everything appears to be going fine and then I receive error message "Commitment of change set failed!"

The task is below:
<vaultbranch url="${vault.server}" username="${vault.user}" password="${vault.password}" repository="${vault.repository}" sourcepath="${settings.folderPath}" destinationpath="${settings.newFolderPath}" comment="branching ${vault.currentIteration} to ${vault.nextIteration}" />

All the other vault NAnt tasks I've run work fine using the same details - but for some reason as soon as I try and commit - it fals.

The server produces the following logs:
(3cc7e8b8-0d56-41a7-aebc-d3942668a931) BeginTx returned: FailDBInvalidObjIDVersion
(3cc7e8b8-0d56-41a7-aebc-d3942668a931) CopyBranch: $/Extensibility/Test.1D to $/Extensibility/Test.1E returned: FailDBInvalidObjIDVersion

Any help would be really appreciated!

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Wed Oct 10, 2007 12:28 pm

Let's make sure that there isn't some old information in a cache first. On the client running the NAnt tasks, there should be a Vault Cache folder. If you clear that out, including the _sgvault folder, Vault should rebuild it.

Right after that, to remove old information from the server cache, you can perform an iisreset by going to Start - Run and type iisreset. That command will disconnect all the Vault and web users from that server, so you may wish to pick a convenient time.

Then try your operation again and let me know the results.

Stoive
Posts: 3
Joined: Wed Oct 10, 2007 5:44 am

No cache

Post by Stoive » Thu Oct 11, 2007 8:29 am

OK - having removed the client cache completely I ran IISReset on the server, still get the same error I'm afraid.

Is there anything else I can try?

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Post by Beth » Thu Oct 11, 2007 3:22 pm

Do you know if you get the same error if you try making that branch in Vault?

Do you have auto-commit turned on or off?

Also, which version of Vault are you using?

Stoive
Posts: 3
Joined: Wed Oct 10, 2007 5:44 am

Vault config

Post by Stoive » Fri Oct 12, 2007 1:06 am

This is the frustrating part, I have no trouble whatsoever making the change in the normal vault client, using exactly the same details.

The client has "auto-commit after each transaction" turned on, but turning it off seems to make no difference.

I'm working with Vault 3.5.3 (used the vault 4.0 tasks on a seperate repository and they worked first time, but the ability to upgrade currently doesn't exist within the firm)

Thanks for your help with this - when I know it can work with the client it's very frustrating not to be able to replicate the transaction within NAnt.

Post Reply