I have spotted this error recently in our CC.NET logs for a specific project. When CC.NET checks for any changes in the repository code base, Vault continually throws the following errors so the latest version history cannot be obtained.
Code: Select all
Starting process [C:\Program Files\SourceGear\Vault Client\vault.exe] in working directory [D:\[PATH SNIPPED]] with arguments [versionhistory "$/[REPO SNIPPED]/" -rowlimit 1 -host src.dev -user web.dev -password [PASSWORD SNIPPED] -repository "[REPO NAME SNIPPED]"]
<vault>
<error>
<exception>System.Exception: No object was found at the repository path: $/[REPO SNIPPED]
at VaultClientIntegrationLib.RepositoryUtil.FindVaultTreeObjectAtReposOrLocalPath(String testPath)
at VaultClientIntegrationLib.RepositoryUtil.FindVaultFolderAtReposOrLocalPath(String testPath)
at VaultClientIntegrationLib.ServerOperations.ProcessCommandVersionHistory(String folderPath, Int64 versionHistoryBeginVersion, VaultDateTime beginDate, VaultDateTime endDate, Int32 rowLimit)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)</exception>
</error>
<result>
<success>False</success>
</result>
</vault>
Attempt 2 of 5: ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: . Process command: C:\Program Files\SourceGear\Vault Client\vault.exe versionhistory "$/[REPO SNIPPED]/" -rowlimit 1 -host src.dev -user web.dev -password [PASSWORD SNIPPED] -repository "[REPO NAME SNIPPED]"
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execute(ProcessInfo processInfo)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Vault3.ExecuteWithRetries(ProcessInfo processInfo)
CC.NET retries 5 times and then sleeps, which then continues all the time. Hence, the build never runs.
I cannot seem to get any other information from the logs that could lead to a solution so I was wondering what I should try next?
The repository appears to work fine with the GUI, including change history queries etc, so again this adds to the confusion.
Any assistance would be greatly appreciated.
Many thanks,
Tim Peel