Catastrofic failure when changing source control

rob pemberton · Post by **rob pemberton** » Tue Nov 23, 2004 7:07 am

I'm receiveing the message "Catastrofic failure" after I have branched and tried to change source control

start:
13 project solution

from vault client select solution node from tree, click branch menu new branch is created.

from vs-ide select open solution from source control

from vs-ide select change source control - unbind and close dialog

from vs-ide select change source control - solution and all projects to new branch - select ok

after some processing i receive "Catastrophic Failure"

dan · Post by **dan** » Tue Nov 23, 2004 8:15 am

Can you post a screen shot of the message? What actions were you taking when the error came up?

Also, did you check in the solution or project file with the new bindings (which needs to be done to complete the branch).

Thanks,

rob pemberton · Post by **rob pemberton** » Tue Nov 23, 2004 8:47 am

The screen shot wouldn't do much good. Just a simple alert dialog with "Catastrophic Failure" and an OK button.

I was able to work arround the problem.. here's how.

I noticed in the original project bindings of two of the sub projects where using the solutions' bindings. I changed the bindings on those projects to use there own bindings and started again by deleting the old branch and creating a new one.

I received the same message after going through the change source control process. In this case I noticed that the solution file was not bound to the new solution, but sub projects were bound correctly. I used the vault client to check out the solution, leaving the local file. Then saved the solution and checked it in. Now all is well.

I'd like to understand this more to avoid it in the future

dan · Post by **dan** » Tue Nov 23, 2004 2:13 pm

I'm not sure if you've read our KB articles - you may have since you were following the basic steps there about what to do when branching a project and then using the IDE integration. The basic issue is that the VS solution/project doesn't know that it has been branched, so uses the same binding info it had before.

For more info, see
http://support.sourcegear.com/viewtopic.php?t=194
and
http://support.sourcegear.com/viewtopic.php?t=1917