SourceGear Support

Please add this line to the above logging setup lines:

VaultLib.SimpleLogger.Log.IncludeStackTraces = true;

This will generate a huge log file, but will help me track this down better. Thanks.

I've got a temp build which updates only the items that you're requesting in the ListChangeSet. Please email support at sourcegear.com ATTN: jeremy with a link to this thread, and I'll send it to you.

Bradley,

Our records indicate that you have 5.0 licenses for all of your users. We rewrote the method that is causing the unnecessary refreshes in 5.0, so at the moment, I think that the best advice is to have you upgrade and report back if the problem persists.

Yes, please email them to support at sourcegear.com ATTN: jeremy with a link to this thread.

Hrm...

Can you turn on client logging and Debug server logging?

Thanks.

Sorry to keep asking general questions, but does the shelve work if you try it on the server connecting to localhost?

Hi Lynn, We've had three reports of shelve upload failures so far, all with the same behavior. We haven't seen it here yet, so I need to ask some general questions. 1. What types of changes are you shelving? Add file? File edits? 2. Are other checkins and add files working? 3. Can you check your IIS...

Wow, you're right it's taking a very long time. During the long stretch of <wf> and <mutex> messages, it's scanning all of your working folders for edited files. There are a couple of things you can do to avoid this working folder scan (which happens in the background in the GUI client) 1. Set less ...

To enable logging, put this code at the start of your program: VaultLib.SimpleLogger.Log.EnableClass("all"); VaultLib.SimpleLogger.Log.Enabled = true; VaultLib.SimpleLogger.Log.LogFilePath = "c:\\logfile.txt" Looking at the log file will help determine where the slowdown is happe...

It will probably be fastest to take this offline. Please email support at sourcegear.com ATTN: jeremy with a link to this thread, and a copy of your sgvault.log.

What does your Vault server log file have to say about the errors?

The initial view of a file's history will be Vault History. To show VSS history, you click the Show VSS History button on the bottom right. That brings up a new list box, with a splitter between the two list boxes. VSS history is in the same dialog, but not mixed in with Vault history.

The only issue I really see, overall, is when you've got several versions in Vault so you sort of have two histories to look at. Then based on the version you're looking at you have to "get" that version a different way, that will be confusing to users. That's a good point, but we're work...

You want to put the VSS version into your Vault working folder? At the moment, there are two workarounds: In the Vault history dialog, diff the VSS version against your working folder. Copy the text from the VSS version and paste into the Vault version. or In the Vault history dialog, View the VSS v...

What do you mean "getting a file"? Handoff can view and diff old file versions from VSS. What operations are you looking for?