SourceGear Support

Thanks, Beth!

The work items aren't part of a repository at all. They are in a different type of container that is called a Project. They will be where they always have been. Also, the links in the Project that point back to the files modified will point to the repository location where the check-in occurred. So...

One more question:

If the import succeeds, does it bring across the work items as well? On the old repository we always checked in against a bug and it would be nice to have that history as well.

Ok so I checked out the log file and it gave me a clue: it had failed why trying to process and stated "checkin comment required." I thought back to through the history of the repository and this option was enabled at some point, although not a the very beginning but had been enabled from ...

Thanks! That sounds like it would do the trick but I'm getting an error when I try to import: --------------------------- Import Error --------------------------- An error occurred while importing a transaction for (TxID: 18 on 6/27/2007 8:46 PM by admin [1]) . The import cannot continue. ----------...

... to another?

Say I have 2 established instances of Fortress and I want take a repository from one server to the next, is that possible?

Yeah that will probably work.

Do you think it could have anything to do with the fact that my fortress db started life as a Vault 3.x db?

If I try to run the installer it tells me I have to uninstall Vault before running the installation.

The kicker is that I'm running Fortress 1.0.4. So either upgrading is not supported and the message needs to say Fortress instead of Vault or there's a bug.

I've emailed you a screenshot.

lbauer wrote:I wasn't able to reproduce this.

What is the name of your folder?

I named it after a domain name, so it would be something like my-domain.com. Also, there's a good chance it could be a line break and not a space, I'm honestly not exactly sure because I copied the text for the folder name from a webpage, specifically a hyperlink on that webpage. I wasn't able to re...

You cannot delete or rename a folder with a space on the end of the name.

You'll get the continual "Illegal Characters in Path" error message over and over again.

Fortress version 1.0.4 (15848)

Whats the logic behind the required check-in comment? If I have several files checked out, including some new files to be added to the repository, and I click check-in at the solution level, the new files will be checked in but the existing files will be rejected (if I neglect to select a work item ...

After more fiddling I was able to get the solution to branch and open. I'm not sure what happened, or if I did something differently, but here's the general timeline: 1) Solution bound with 2003 client 2) Solution unbound with 2003 and re-bound with 2005 3) Installed Fortress 1.1 4) Solution unbound...

The story gets stranger, somehow, after I told it to unbind with the 2005 client and rebind with the 2003 client, my solution decided it was bound with the 05 client after all.

We'd like to recreate the issue, but we need some more details, so I will need the one posting above this answered (OS and service pack on VS) and another question: If you branch a project/solution that does not have a web project in it, do you still have the same issue? OS: Vista Ultimate Visual S...