SourceGear Support

I've done some more research on this and, unfortunately, have very few answers. I am not seeing any errors in the Vault server log, the event log on the Vault server, or even the event log on the client machines. As to the virus scanner, I've checked the logs there and don't see McAfee reporting any...

Thanks for listening; I'm glad this on is on the radar. Getting back to Show non-version-controlled folders ghosted in folder tree option, is there any way for me to force the Vault Client to expand all sub-folders beneath a particular branch? If only I had this option, I could at least easily ident...

Hi -- I'm using Vault 5.0.3 on Windows 7 Enterprise / 64-bit client. Many people on my team (with similar configuration) are seeing client-side-only error when doing a Get Latest from the Vault server. Here's a sampling of such errors: [4/21/2010 1:39:53 PM] Finished get latest of $ [4/21/2010 1:33:...

Just as there is already a feature which allows you to Detect New Files to Add , I would feature like to see a similar feature for Folders. The way it would work would be to search from the specified starting location into your working folders until it found a directory that was not already under so...

Actually, in truth I did not realize that LISTFOLDER also showed the checkout status of the file (which is nice). But you're right that it actually is showing me more information than what I really want (in that I get the status of every file in that branch and down). However, it's still probably be...

It would be really nice to have a STATUS command (command-line Vault) for showing the current status and version of a specific file. And by "status" I mean it should show whether the file is checked out or not and if checked out, by whom, and whether the checkout is exclusive. LISTCHECKOUT...

I've just recently upgraded our database to version 5.0.3 and am happy to now make use of the very cool shelving feature. But like all new features, I think there's still room for improvement. A few seemingly simply changes to Client/Web-Client would include: Hide inactive users from Find Shelvesets...

Yes, as stated in my post, "an IISRESET seems to have fixed the issue."

Looks like this problem needs to be resubmitted to the defect queue.

I am using Vault 4.1.4.18402 and just ran into this same exact issue. Steps to reproduce for us are: Create new branch in root (e.g., $/Global Services 9.2.0, branched from $/Global Services 9.1.0) Check out some file under $/Global Services 9.2.0 Rename $/Global Services 9.2.0 to $/Global Services ...

Unfortunately, without "reproducible steps", I don't think we'll get far, so I'll have to pass. I know that the problem happens (even under 4.1.4), but I don't know how it happens. I would just like to see the requested change for Reset Repository Cache be implemented (a request which you ...

If you're asking if I'm able to reproduce the original issue in this post, no I am not. However, I have seen this exact same issue before and was bitten by it myself long ago (just not recently). So, perhaps renaming to a deleted name works as desired under 4.1.4. Nevertheless, even using 4.1.4, we ...

I'm not sure that it happens "regularly", but has happened and still does pop up every now and again. I'd say once or twice a month someone on the team (of 50) has a client-related problem and the only "solution" is to manually delete the cache. I would be very grateful if Reset ...

Indeed -- someone created shares and later deleted those. The deleted files/folders have since been obliterated but yet the problem persists.

Do I read you correctly to say that this is a bug and there is currently no solution?

Yes, my renamed or deleted items were listed on the Pending Change Set tab (as are all failed transactions), though by practice I always remove such entries. Even so, I often see my local cache get messed up in the process. And again, the only fix is to manually delete the repository cache. Short of...

I've seen a number of issues exactly like that where a server error is not correctly handled by the Vault client. As a result, the client caches info that does not agree with the server and future operations fail (generally because the cached client tree and the actual server tree do not match). Wor...