Deleted files appeared to user and Get fails to get any file

[kadorken]

One user had not been using vault for a number of weeks keeping up to date with his GetLatestVersion with the rest of the group. When it came time to
catch up, he tried to get the entire project tree. This completed without any error messages, and without getting any files. A status search for Old files showed many files that were out of date between his working directory and the repository.

The status search also showed many files that had been deleted and obliterated from the repository. Attempting to Get these directly received an error message (sorry, can't remember exact text but something like object not found).

Repeated attempts to Get all the files failed for this one user. Worked fine
from other computers for different users.

Perusing the KB, we came across one note about deleted files that mentioned cleaning up the 'hidden' folder found under
C:\Documents and Settings\username\Application Data\SourceGear\Vault_1\Client\<GUID>

We deleted the entire SourceGear folder under ApplicationData , and the user's problems went away.

It appears that stale data in the ApplicationData hidden area was confusing Vault's attempts to get files.

During the investigation stage, we did have client logging turned on. I have attached the log file if you wish to know more. I could probably restore the 'hidden' files from the backups if you need them.

We are currently using Vault 2.0.6(2219)

[sterwill]

The log file, near the very end, contains the following line:

Code: Select all

10/22/2004 1:55:50 PM <get>: [GUIClientWorkerThread:3124] BeginDownloadFiles called, downloadID: 

Unlike other lines that include the downloadID, this one is missing. That means that the server didn't respond to the client's request to download files. This could be because an error happened in the server (check the server log file for details) or some network problem prevented the (large) request from making it to the server. This has happened to users of Microsoft ISA proxy server. Also, IIS can be configured to reject web requests larger than a certain size. This can be changed in the Web.config file in the VaultService directory, though it defaults to a very large number (102400KB, or 100MB).

[kadorken]

The only change we made to make the "Get Latest Version" work was to remove the 'hidden' vault files on the user's Documents and Settings/Applicaton Data location.

No IIS nor network nor server configurations were changed between the
time of the failure and the subsequent successful Get.

[jeremy_sg]

Another reason that we've seen this happen in the past is when hitting a Windows 2003 server. By default, the connection timeout is set to 120, which is too short when Vault has a lot of processing to do. If the begin download takes more than 2 minutes, IIS will drop the connection and the client won't get a downloadid. Setting the connection timeout higher will fix the problem.