SourceGear Support

I'm using Vault Professional 6.1.0.30531 with Visual Studio 2010 using the Classic Client. I needed to change the encoding of some .cs files from Western European (Windows)(1252) to Unicode (UTF-8)(65001) with BOM. So I performed the following steps: 1. Checked out the files in Visual Studio (Let's ...

In Vault Professional 5.1.1. In the web interface, when I click a button (for example when adding a new Item to a Project and clicking the "Submit" button) there isn't any feedback to let me know the button was clicked and an action is being performed. So, when the request takes more than ...

Using Fortress Client 2.0.4.18845 About a week ago I had to change the date on my computer to a future date to test something in my application. After that I forgot to set it back to the original date and during that time the Fortress client cache must have been synchronized so a future date was sto...

I'm using fortress 1.1.2. Yes the Bug ID actually existed. After i restart Visual Studio 2008 i'm able to check in the remaining items with the same Bug ID, however the bug tracking history from the first items is lost. It doesn't happen always, it happens randomly. It may be a random wireless netwo...

I found the following problem frequently while using fortress in Visual Studio 2008 (Classic Client). When the following conditions are met: 1. I modify some files 2. I add a project and/or some new files to an existing project 3. I enter a bug ID directly The following happens: After a while a wind...

HI, I'm testing if I could use branch per task with Fortress (Vault). If I create a new branch for each task in Fortress (Vault) and i'm connecting to Fortress through a slow Internet connection. Does that mean fortress downloads all the files for each branch (task) even if all the files from all th...

After trying different ways to check in the solution i discovered it was 1 project that was causing the check in to fail. After removing that project from the solution and moving the files to a new project with a different name i was able to check it in following the manual steps. I still don't know...

I'll try to send you the log file, meanwhile here are the steps to reproduce the behavior: 1. Open Visual Studio and Set the Visual Studio Plugin to Enhanced Client (VSS Style) 2. Create a new Windows Forms Project/Solution (.NET Framework 3.5) 3. Add an ASP.NET Web Service Application project to th...

I have Fortress 1.1.2 installed and have the same problem, when i add a web reference to a project and try to perform a check in it stays in the "Ending Transaction" message forever. Was the problem fixed in version 1.1.2 ?

I still can't get it to work, i tried getting the whole solution to a new folder using the Fortress Client Application and then running the automated tool from post "http://support.sourcegear.com/viewtopic.php?t=8214" however i get the following error messages: ERR: Error reading SCC file ...

I want to migrate a Visual Studio 2008 solution from Vault 3.1 to Fortress 4.1.2, i have successfully installed the fortress server choosing to keep the existing database. However i found the following problems when trying to open the solution using the new source control client (Fortress Enhanced C...

It's an error printed on a Fortress page, it has the Fortress logo on top and below on the white area it says: Error The request failed with HTTP status 404: Not Found. It only happens when i use a port different than the default 443. If i connect using port port 443 i can add projects without probl...

On Windows Vista Ultimate: Logged in as another user belonging to the Administrators group (User Account Control turned off) (Vault Client 3.1 simultaneously installed, never installed any version of Vault or Fortress server before, only the client of Vault 3.1) On Windows 2000 Professional: Logged ...

I installed Fortress 1.1.1 in the following operating systems:

Windows Vista Ultimate : Client And Server

Windows 2000 Professional : Server only

the problem happened on both computers after installation.

After installing fortress the Administrator users no longer have permission to access the folder

%ALLUSERSPROFILE%\Microsoft\Crypto\RSA\MachineKeys

This affects other applications that need to create keys such as Visual Studio when creating new keys to sign assemblies.