SourceGear Support

Sometimes files get checked in or out outside of Visual Studio. In the "old" VSS-days, we would hit the "refresh status" button of the Source Control toolbar to reflect the scc-changes made outside of Visual Studio. This all worked fine with VSS. With Vault however, only the curr...

Add my vote as well, please. This used to be a heavily used feature in "old" VSS times, as the working folders normally contain a lot of irrelevant / derived files that degrade the performance and the results when searching in the working folder.

We've moved the VaultService to another machine (from XP/IIS 5.0 to win2003Srv/IIS 6.0). This worked really well and posed no greater problems. In moving to this server, the shadow folders do not reside on a network drive anymore, and thus the shadow service operates without problems now. Ofcourse t...

instead of snipping through the logfiles, I considered it better to send them to you via private mail - however either my mailfolder or yours seems to be exceeding limits. The zipped logs are 970KB. Perhaps you can tell me some other means of uploading them (anon ftp, e-Mail)? As for commenting the ...

In the meantime, we're talking about three issues here: 1. a file being shown as renegade although identical using CRC compare 2. a file being shown as renegade although identical using timestamp compare 3. pdf-files that are corrupt after vss import (a topic we did not want to raise until further i...

You shouldn't have to change this option to appease Vault. We use the CRC-option since we had one other case of renegade though identical since apparently the rounding of the filetime in vss and vault was in this case slightly different. I could try to reproduce this one as well. Over the five year...

Upon import of certain vb-resource files (*.ctx, *.frx) the result in Vault is an empty file. This happens when the binary in question consists of nothing but binary zeroes. In the underlying cases, the binaries were each 4 bytes of zero, resulting in empty files in Vault. We were able to check in t...

no, it's not beyond file limits (limit is 10MB, filesize is 27KB). we've also tried with a fresh working folder - made no difference. in the meantime we've edited the file in question and checked it in again. now everything seems to be fine. we even did a rollback to the previous version - everythin...

This effect only happens with one specific file. Nothing special about it, a simple plain old C include file. After a VSS import into Vault the file is shown as renegade . In order to avoid timezone problems the CRC -option for determining differences is active. In a folder difference the file is al...

First of all, we're still evaluating and not running with tons of users. There are in fact only two users involved in this evaluation. If we are going to use vault productively, we'll be using a "proper" windows 2003 server ofcourse. The XP-box was just handy and available. We monitor the ...

Apparently the shadow folder service works with two threads, one impersonating the sgVaultShadow user, the other impersonating no-one, thus running as aspnet . The aspnet -thread checks, whether the target directories exist, and whether the target files are out of date. The sgVaultShadow thread then...

as far as i know, you just need to delete the mssccprj.scc file(s).

Here's the web.config. Ofcourse some information has been --snipped-- or --replaced--.

We're using IIS 5.0 with XP.

Thanks! This sure explains this behaviour. We had enough trouble ourselves with this total change in threading design. Could this also be the explanation of the other issue I posted?