SourceGear Support

A 'blue screen of death' is never caused directly by user-mode code. It indicates that a device driver or hardware did something wrong. Windows stops the system (with an automatic restart) as MS feels it is safer to halt early rather than carry on and potentially corrupt user data. It's certainly po...

I'm also having this problem with Vault 4.1.1. It crashes both Vault GUI Client and Visual Studio at almost exactly the same time. The problem occurs when Windows Search starts indexing. I also have a fairly large number of working folders - 40 or so. Frequently changes aren't picked up by the Pendi...

We're all running 4.1.1 but I might see if I can get an update to 4.1.2 scheduled. Otherwise I'll just have to keep an eye on it. I tried various different approaches - checking out when the file has unsaved changes, in VSS mode, in CVS mode, checking out when the file isn't in the foreground, and c...

There have been persistent mumblings among my team-mates about problems with Vault for a while. I just observed a situation where it appeared that one of them had used Get Latest, then Check Out, and edited the file (extensively), only to discover that the file contents weren't actually the latest. ...

Now that Vault 4.x uses .NET Framework 2.0 on the server, it should be possible to set up Database Mirroring on SQL Server 2005. Mirroring acts at a physical level rather than the logical level of replication so I believe should not suffer from this problem (I don't currently have a mirror set up). ...

I believe WITH ENCRYPTION was added in Microsoft SQL Server 2000, so if it's not recognized, that would imply that the server is older. What's the result of running SELECT @@VERSION? WITH ENCRYPTION isn't as secure as you might think. SQL Server 2000 reuses the same key when a stored procedure is al...

Second, I'm making an assumption that .Net Framework 3.5 is installed on the computer in question (because Crypto errors in the past have usually involved 3.5). If that's the case, can you try setting the runtime version in the vault.exe.config? <configuration> <startup> <supportedRuntime version=&...

Sure, go ahead. The only other thing I would add is that for availability reasons, I would normally put my transaction log on a separate physical disk, so that if the disk or filesystem containing the data files failed you'd still have the log files available to back up. This also has the advantage ...

We keep our Vault server behind our firewall and use a VPN for remote access. In the past, before moving to a different server, it was also accessible via HTTPS but that was almost an accident; it shared a server with Exchange ActiveSync. HTTPS only protects you from disclosing passwords and source ...

Vault 4.1.1, Windows Server 2003 R2 (no SP), SQL Server 2000 SP4. Source lines not modified in the 'included versions' are not included in the Blame output. The only way to get the entire file is to set the includedversions URL parameter greater than or equal to the number of versions for the file. ...

We recently upgraded from Vault 3.1.9 to 4.1.1 and in doing so, Setup created a new sgmaster database. It created this database with doubled backslashes before the filename, so the entries in sysfiles read: D:\SqlData2000\MSSQL\Data\\sgmaster.mdf E:\SqlLogs2000\\sgmaster_log.LDF Backup Exec 11d (Bui...

Vault is presumably not designed to run under partial trust. Discuss with your colocated server host - presumably they set it up - whether they are happy to run ASP.NET under full trust. However, if you intend to run any internet-visible applications on this server I would strongly recommend leaving...

The transaction log is a fundamental part of SQL Server's operation. It records every transaction that is made, in order to redo or undo the operations in the case of a database failure. (This allows SQL Server to perform write-back caching on the actual data pages, and to support rolling back a tra...

Sorry, I forgot to mention that. Windows Server 2003 R2. We have not yet applied SP2 on this server. .NET Framework 1.1 SP1 and Framework 2.0 RTM are installed, the VaultService and VaultShadowFolder applications are configured to run in their own AppPool (that is, they share one AppPool independent...

One of my colleagues enabled IIS Compression on our Vault server (which also serves a number of test websites - yes we should definitely have independent systems!) and Blame stopped working, with a blank page in IE 7.0. Fiddler and Wireshark both show that an effectively empty response is returned (...