Help, vault completly broken

sschaem · Post by **sschaem** » Fri Jul 02, 2004 5:02 pm

- ProjectA was branched to a few project tree (Its a core library)
- ProjectA was shared to another location for convinience
- ProjectA was branched again by another project

At that point, the share was lost, each file in ProjectA show a "branched from share" on all files, and no rollback is possible.

We tried and tried and couldnt find a way out of this mess.

We endedup deleting every reference to projectA...
Yet we have 2 instance in that just cant be obliterated saying

".... This Item has branches at: "

No reference is given... I'm concern the database is going to blow in our face at any momment

Anyway to repair the database?

Can we export everything and re-import?

Stephan

sschaem · Post by **sschaem** » Fri Jul 02, 2004 6:19 pm

Something I just realized too...

The admin tool let us obliterate a branch that was labeled.

Its a confusing situation.

The main thing I'm curious about now is

- What should happne when you branch, share and branch a folder?
- And this ".... This Item has branches at: " with No reference given...

Thanks for help/clarification,

Stephan

dan · Post by **dan** » Mon Jul 05, 2004 3:50 pm

The problem is that the term "branch" is overloaded, since we followed the SourceSafe terminology. On a shared folder, branch means "break the share", and it ends up being another branch of the folder. So, your first branch operation was a regular branch operation, then you shared the folder, and then the 2nd branch was a breaking of the share.

So, it looks like it did what it was supposed to, and there shouldn't be anything to worry about.

I'm not sure what the problem is with not being able to obliterate one of the branches - we'd probably need to get more info, or be able to reproduce it.