Problems with CruiseControl getting latest

[dragosca]

We have Vault 5.0.3 on our server and we are using CC Net 1.4.3.4023 for automated builds.

Since one developer checked in a file yesterday (from within Visual Studio 2005, on a machine with Vault Client 5.0.3 installed), CC's get latest fails with an "Invalid object version specified" message pointing to that very file. We can verify that the checkin was successful however, by checking the file's content in the Vault client.

Any help is appreciated.

Pasted below is a section from CC's log, containing the command line execution and the response from Vault.



2010-06-02 12:49:01,924 [VP:INFO] Getting source from Vault
2010-06-02 12:49:01,924 [VP:DEBUG] Starting process [C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] in working directory [E:\Deployer\Dev_Build\WorkingDirectory] with arguments [getversion 16011 $/PennyDotNet E:\Deployer\Dev_Build\WorkingDirectory -useworkingfolder -merge overwrite -makewritable -backup no -setfiletime checkin -host ah-vault-vm -user POL_CruiseControl -password pwd -repository DotNet]
2010-06-02 12:49:25,873 [1360:DEBUG] [VP C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] <vault>
2010-06-02 12:49:25,873 [1360:DEBUG] [VP C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] <!--Get latest version failed for $/PennyDotNet/RenderingEngine/Penny/Format.cs: Invalid object version specified.-->
2010-06-02 12:49:25,873 [1360:DEBUG] [VP C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] <error>
2010-06-02 12:49:25,873 [1360:DEBUG] [VP C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] <exception>VaultClientOperationsLib.GetLatestVersionFailedException: Exception of type 'VaultClientOperationsLib.GetLatestVersionFailedException' was thrown.
2010-06-02 12:49:25,873 [1360:DEBUG] [VP C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] at VaultClientIntegrationLib.GetOperations.performGetVersion(String objectPath, Int32 version, String strDestFolder, GetOptions getOptions)
2010-06-02 12:49:25,874 [1360:DEBUG] [VP C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
2010-06-02 12:49:25,874 [1360:DEBUG] [VP C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)</exception>
2010-06-02 12:49:25,874 [1360:DEBUG] [VP C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] </error>
2010-06-02 12:49:25,874 [1360:DEBUG] [VP C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] <result>
2010-06-02 12:49:25,874 [1360:DEBUG] [VP C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] <success>False</success>
2010-06-02 12:49:25,874 [1360:DEBUG] [VP C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] </result>
2010-06-02 12:49:25,877 [1360:DEBUG] [VP C:\Program Files (x86)\SourceGear\Vault Client\Vault.exe] </vault>
2010-06-02 12:49:26,583 [VP:INFO] Emailing "VP Exception in Build !" to d@d.com
2010-06-02 12:49:26,818 [VP:INFO] Integration complete: Exception - 6/2/2010 12:49:25 PM

[Beth]

Could you look in your Vault Server Log for errors happening around the same time and post them? When looking at those errors, make sure you catch the time at which the error first started appearing.