SourceGear Support

You'll also want to check in the VaultShadowFolder/web.config file to make sure that the "shadowfolder_cachepath" key is NOT commented out. It should look something like this: <add key="shadowfolder_cachepath" value="c:\Program Files\Sourcegear\Vault Shadow Folder Cache"...

I've gone through several threads now and none have seemed to correct my problem. I don't know if I am missing something here. Here is a screen shot of the current error I am getting. Also, should my VaultShadowFolder Web Application be in its own Application pool? Currently I have VaultService, For...

Quick Update: I just manually put the password in the Web.config file to get this thing going. I still don't know why the password was left empty in one config file and not in the other. Anyways, I am getting the following message: "The Shadow Folder Service was unable to connect to the Fortres...

You shouldn't need to modify credentials, and those are not in plain text. I DO see that the value for the "shadowfolder_password" is encrypted (and converted to base 64) on line 142 . However, the error message indicates that the credentials on line 93 is what is causing the problem. Not...

I just tried to go to the Shadow Folders page for one of my Repositories when I got the following error: http://hutch619.googlepages.com/configError.jpg Am I supposed to directly modify the impersonation credentials in the web.config file or is there a front end provided by Fortress that I should be...

I can't figure out for the life of me how to recreate it now! I now have dual monitors going, the VMware add-in, another instance of VS running, and everything is fine now! :shock: I guess it's good that it's gone, but I'd like to know what caused it all in the first place. Oh well, I guess I'll jus...

Success! I changed a few things about the environment from which I originally had the problem(s). Here are the things I changed: - Was using dual monitors - now only using one - disabled the VMWare virtual debugger add-in (as Ian suggested) - only running one instance of VS (as opposed to three) I t...

OK, just so there is no confusion I am going to include screenshots of each step so you can try to reproduce the bug on your end. Create a new windows form project in VS2005 and add a new RDLC report file to the project. Then add solution to source control. http://hutch619.googlepages.com/FortressCr...

When VS2005 restarted itself I got the "Object reference not set to an instance of an object." pop up from Fortress Client. The only thing that had loaded was the start page (I have "Show Start Page" set at startup in VS options). l don't know if this is specifically related to m...

In Visual Studio 2005 you are allowed to edit an .rdlc file (MS Report) while your project is actually running. However, if I attempt to check-in the file (while the project is running/debugging) then Visual studio crashes. I don't recall Vault 3.5 having this issue. I am currently running Fortress ...

After looking through a few other postings it appears I should be able to upgrade straignt from 3.5. I was able to remove the Vault Server app from within "Add/Remove Programs" but can't remove "SourceGearVault Admin Tool". I am getting the warning "there are other users log...

If I am currently running Vault 3.5 do I need to upgrade to 4.1 before moving to Fortress? I tried going though the Getting Started tutorial but got stuck when trying to uninstall Vault. I'm thinking the tutorial is for users moving from vault 4.x to Fortress. Is this correct? If I can do it from 3....