We recently had a situation where one user (the one we use for CC.NET) had repeated GET failures. Trying to do a GET in the Vault GUI resulted in a bunch of red error messages. Other users (same Windows user, different Vault user) could do a GET with no problem.
In order to fix the problem with the one user, we had to blow away that user's cache deep down in the Documents and Settings folder. After that, everything was fine.
I don't have any information to reproduce this and it's not a problem anymore, but I wanted to let you know it happened. This is with Vault 3.1.7.
How slow would Vault be without a cache?
Corrupt cache broke Vault
Moderator: SourceGear
Thanks for the report - we'll keep an eye out for other reports.
The cache is only partially about performance. Mostly it is where the state info for client files is kept, so we can tell whether a file is edited or not, and also is used to compute deltas for files that we send back and forth to the server. It is integral to the operations of the client.
The cache is only partially about performance. Mostly it is where the state info for client files is kept, so we can tell whether a file is edited or not, and also is used to compute deltas for files that we send back and forth to the server. It is integral to the operations of the client.
Vault Server + Client = 3.16.
I would like to let you know that we also experienced the same kind of error.
We have a Windows Service running periodically to check in some files. This Windows service failed the check in with the error "FailDeltaApply". Same solution to solve the issue (deleted C:\Documents and Settings\(login)\Application Data\SourceGear\Vault_1\Client folder)
The complete error message was:
I would like to let you know that we also experienced the same kind of error.
We have a Windows Service running periodically to check in some files. This Windows service failed the check in with the error "FailDeltaApply". Same solution to solve the issue (deleted C:\Documents and Settings\(login)\Application Data\SourceGear\Vault_1\Client folder)
The complete error message was:
Code: Select all
<vault>
<changeset>
<ModifyFile id="0" repospath="$/myProject/ABC/StaticContent.en.resx" localpath="F:\Projects\ABC\StaticContent.en.resx" />
<ModifyFile id="1" repospath="$/myProject/ABC/StaticContent.fr.resx" localpath="F:\Projects\ABC\StaticContent.fr.resx" />
</changeset>
<!-- Preparing data to begin transaction -->
<!-- Beginning transaction -->
<!-- Check in $/myProject/ABC/StaticContent.en.resx -->
<!-- Check in $/myProject/ABC/StaticContent.fr.resx -->
<!-- Upload for item $/myProject/ABC/StaticContent.en.resx failed, retrying... -->
<!-- Upload for item $/myProject/ABC/StaticContent.fr.resx failed, retrying... -->
<!-- Upload for item $/myProject/ABC/StaticContent.en.resx failed, retrying... -->
<!-- Upload for item $/myProject/ABC/StaticContent.fr.resx failed, retrying... -->
<!-- Upload for item $/myProject/ABC/StaticContent.en.resx failed, retrying... -->
<!-- Ending the transaction -->
<!-- Upload for item $/myProject/ABC/StaticContent.fr.resx failed, retrying... -->
<!-- Upload for item $/myProject/ABC/StaticContent.fr.resx failed too many times, aborting transaction.
Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.
The specific error was "The server returned an unknown error header: VaultFileUpload.aspx encountered: FailDeltaApply"
An exception was encountered during the transaction. Exception: The server returned an unknown error header: VaultFileUpload.aspx encountered: FailDeltaApply at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)
at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult) -->
<!-- Upload for item $/myProject/ABC/StaticContent.en.resx failed too many times, aborting transaction.
Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.
The specific error was "The server returned an unknown error header: VaultFileUpload.aspx encountered: FailDeltaApply"
An exception was encountered during the transaction. Exception: The server returned an unknown error header: VaultFileUpload.aspx encountered: FailDeltaApply at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)
at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult) -->
<!-- Transaction failed -->
<!-- Transaction failed -->
<result success="no" />
</vault>