Vault.exe with cc.net fails with 1502 : FailFileStreamError

[wwiser]

We have a CruiseControl.NET 1.4.4 SP1 server which is running the Vault 3.1.9 client and connects to a Vault 3.1.9 server. I have occasionaly noticed that CruiseControl seems to skip some checkins. Looking through the server log I noticed this error coming from Vault: 1502 : FailFileStreamError.
Here is the Log entry:

2009-12-28 11:09:41,323 [2876:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] <vault>
2009-12-28 11:09:41,323 [2876:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] <error>
2009-12-28 11:09:41,323 [2876:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] 1502 : FailFileStreamError
2009-12-28 11:09:41,323 [2876:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] </error>
2009-12-28 11:09:41,323 [2876:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] <exception>
2009-12-28 11:09:41,353 [2876:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] System.Web.Services.Protocols.SoapException: 1502 : FailFileStreamError
2009-12-28 11:09:41,373 [124:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
2009-12-28 11:09:41,373 [124:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
2009-12-28 11:09:41,393 [124:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] at VaultClientNetLib.ClientService.VaultService.BeginVersionHistoryQuery(Int32 nRepID, Int32 nRowLimit, Int64 nObjID, DateTime dtBeginRange, DateTime dtEndRange, Int64 nStartVersion, Int32& nRowsRetrieved, String& strQryToken)
2009-12-28 11:09:41,413 [124:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] at VaultClientNetLib.VaultConnection.VersionHistoryBegin(Int32 nRowLimit, Int32 nRepID, Int64 nObjID, DateTime dtBeginRange, DateTime dtEndRange, Int64 nStartVersion, Int32& nRowsRetrieved, String& strQryToken)
2009-12-28 11:09:41,413 [124:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandVersionHistory(String strReposPath)
2009-12-28 11:09:41,433 [124:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
2009-12-28 11:09:41,433 [124:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
2009-12-28 11:09:41,433 [124:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] </exception>
2009-12-28 11:09:41,433 [124:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] <result success="no" />
2009-12-28 11:09:41,433 [124:DEBUG] [*** C:\Program Files\SourceGear\Vault Client\vault.exe] </vault>
2009-12-28 11:09:41,433 [***:WARN] Attempt 1 of 5: ThoughtWorks.CruiseControl.Core.CruiseControlException: Source control operation failed: . Process command: C:\Program Files\SourceGear\Vault Client\vault.exe versionhistory $/*** -beginversion 13949 -rowlimit 1 -host ***.com -user *** -password *** -repository ***

This particular instance happened around the time a developer was checking in code. Any thoughts about what's causing the error\how to avoid it?

[Beth]

Is the developer that is checking in code, checking in the same materials that are being checked in by Cruise Control?

Can you verify that all clients are on Vault 3.1.9 and not Vault 3.1.7? The FailFileStreamError was seen a few times in Vault 3.1.7 and a fix was written for that.

[wwiser]

The developer was checking in code that was in the Vault directory that CruiseControl.net monitored. According to the build log, it began a check for modifications at 11:09:30
2009-12-28 11:09:30,842 [***:DEBUG] Starting process [C:\Program Files\SourceGear\Vault Client\vault.exe] in working directory [C:\***\Build\Build] with arguments [versionhistory $/*** -beginversion 13949 -rowlimit 1 -host ***.com -user *** -password *** -repository ***]
and according to the Vault server, the developer checked in the changed files at 11:09:36.
Could this be a concurrency issue?
I'll check with the team and see if everyone is on 3.1.9

Thanks for the fast response.

[wwiser]

I've checked with the developer and he is running Vault Client 3.1.9

[Beth]

Could you start up Client Side Logging for the Vault command-line client? Instructions are in the link, and it talks about the command-line client about half-way down the page.

Also, can you check your Vault Server Log for any errors that could be occurring at the same time?

Run the scenario again to get the errors and then check both the client log and server log. Please post the errors or the logs. Any attachments can be deleted from this forum thread when we are finished troubleshooting.