SourceGear Support

Over christmas, we upgraded from Vault 3.5.2 to Fortress 1.0.6. Most people installed the Fortress client alongside the Vault client and then switched when the server was upgraded. However, when the Vault client is subsequently uninstalled, we're finding that IE6 and IE7 are being broken. Sites whic...

According to http://support.sourcegear.com/viewtopic.php?t=1676 there was a bug in an early version of Vault in which an attempt to share a folder from a label failed with the error: Object reference not set to an instance of an object. In Vault 3.5.2 we could right-click a folder, select Show Label...

Just installed Fortress 1.0.6 on a test server, and it appears the web interface is missing a help file. Go to the Item tracking tab, select a project, then select Categories. Clicking Help here tries to load http://<server>/Fortress/help/categories.htm. This file doesn't exist in C:\Inetpub\wwwroot...

Is it safe to upgrade a Vault+Dragnet installation without using the Dragnet database? Our Vault database is now quite mature (37GB and counting...) but we've only really played around with Dragnet and we have nothing worth bringing across into Fortress. I did a test upgrade of Vault+Dragnet, but en...

In a normal environment, it probably would. However, we're using Vault in a way that Sourcegear probably wouldn't approve (for performance reasons... Our excuse is it's what we used on Sourcesafe, and there doesn't seem to be a better way to do it in Vault.) We have a common source code library. Mod...

We have many files which are shared across 10's or even 100's of projects. If a file is checked out to a user, the only way (it seems) they can undo the checkout is to remember the project that it was checked-out from and undo the checkout from there. For example, if I share $/TEST/FOLDER/test.c int...

We have a lot of files (3GB+) from failed Sourcesafe imports, so we wrote this tool to remove them with the minimum of fuss. This is a recursive obliterate tool, using a modified version of the Vault command line, and a python script. Attached are the changed source files, plus VaultImage.exe and Va...

Same result, unfortunately :( I can check out the file and undo the checkout, but any attempt to alter it (rename, check in a changed version) results in the error. If I change the name of the file in another location, it changes everywhere except this one location. The history shows that a change h...

The import was from a sub-project in VSS, containing our library files. These files are shared sometimes hundreds of times, among many different projects. Most of the files would have originated in other areas of VSS and then shared into the library tree. I've since done subsequent imports from othe...

One of the logs I originally posted was from the server in debug mode. It didn't seem to show much extra info

Hi Beth, Since the file has come directly from a Sourcesafe import, I assume it's just shared at file level. I can successfully remove it from another folder, and I can view the history and previous versions of the file. I ran VSS2005's analyze -c -d -fp -s -v3 a few times, but our Sourcesafe databa...

Hi, We've just started using Vault in anger, now that I have imported about 3GB from our Sourcesafe database. Sadly, we've come across a problem - we can't delete a particular file. The file is shared across 25 projects, but we just want to remove it from one project. The client logs this: [05/01/20...

Ever since the first release of Vault I've been trying to get our broken 30GB VSS database to import. I know there's not a snowball's chance of getting the whole thing across in one go, but I've finally managed to get something across for the first time :) I found a couple of the points below by sea...