SourceGear Support

We are having an issue with one of our repositories. This repository has numerous branches. When one of our developers (the only one having this issue) try's to pull down one of the branches, he can check out but cannot check in a file. This occurs in both Visual Studio 2008 and the Fortress Client....

where will the diagnostic file be written out to on the desktops? Also in the Temp directory?

I just looked at the logs and nothing has posted in there since the 14th. I'll have the developers turn on the logging and see what that shows. I'm pretty much stumped on this one.

Bumping this issue again. This is starting to mushroom, now a 3rd developer is experiencing this issue.

We tried that but it still didn't work. I now have another developer that is experiencing this issue with VS 2008 and the enhanced client. Is there something I can turn on at the desktop level for additional logging?

Hi Linda,

That partially worked. His native Fotress client is now working but he is still getting that error when starting up the enhanced client in VS 2005. Any other thoughts?

Thanks,

Richard

I had a developer whose V/S instance shutdown unexpectantly. Once he restarted V/S, he is getting the following error from Fortress: There was an error generating the XML document. This is occurring with both the V/S Enhanced client and the native client. He has rebooted his dev environment and stil...

So I can go straight from 3.5 to Fortress 2.0.1 then?

Sorry, I'm just now getting back to this. I've cloned the existing Vault db to do a dry run. I've installed 4.0.6 on our test server and everything seems to go through fine. However, when I try to login through the web admin interface and use the password that I typed in, it keeps telling me that th...

I'm having an issue where I cannot get a web application bound to the repository. The web application was bound but we had to remove it from the solution to convert the site from VS2003/1.1 to VS2008/3.5 and when we add it back to the solution and rebind it, we are getting that the binding is invali...

Hi Beth,

Going through this dry run, will I need to convert my licenses from 3.5 to 4.0, to Fortress? If so, will that effect our production Vault server?

Thanks,

Richard

Thanks Beth. To make sure I understand, run the vault 4.0.6 upgrade for Vault. Then, uninstall the Vault W/S (I'm assuming that it will prompt you to keep the db like previous installs). And then install 1.1.4 of Fortress (so I assume that I won't need to install any previous versions of Fortress, I...

We are preparing to upgrade from Vault 3.5 to Fortress and I would like to know if there are more steps involved other than just running the install of Fortress? I know that in the past, we had to install all the previous versions if we were more than a couple versions off.