SourceGear Support

Thanks for this writing this final summary. I received the same error when attempting to share a file, i.e.,

"An item with the same name or object id already exists in the selected folder"

When I undid several pending operations to the target folder / file the share succeeded.

We are using the following client / server versions:

This Fortress client is version 1.1.4.18402
Your Fortress server is version 1.1.4.18402

Are they compatible with Visual Studio 2010?

Thanks,

Brett

We are a small organization using Fortress 1.1.4 backed by SQL Server 2005. I've set up one repository for our source code and a second repository for "documentation". So far I'm the only one using the documentation repository; however, we have a lot of documentation we could potentially c...

This Fortress client is version 1.1.4.18402 Your Fortress server is version 1.1.4.18402 OS: Win XP Pro SP 3 IDE: Visual Studio 2008 The Fortress enhanced client source control plug-in is very good; however, it would be nice if I could also alter the checkout behavior so that the client prompts me fo...

Hmmm. I experienced the same thing this morning. I'm running VS 2008, Win XP Pro SP3, and Fortress version 1.1.4.18402. I tried a number of fixes on the web (Perforce suggestions, Sourcegear Support suggestions) without much luck. I eventually resolved the problem by opening Visual Studio, selecting...

Well, I set the working folder association for the top-level project folder, and that seems to have done the trick. That is, I was attempting to add the following project: d:\tools\propagate which resulted in the error listed previously Using the Vault client, I set the working folder for the "...

IDE: Visual Studio 2005 (8.0.50727) Vault client: 3.5.1.4786 Vault server: 3.5.1.4786 I get exactly the same error when trying to add a *new* project into Vault from VS 2005: An error occured while accessing the source control system. Check your solution's source control bindings. Click "OK&quo...

OS: Win XP SP 2 Vault Client: 3.0.6 Lately, after about two years of use, Vault has started forgetting my working folders. The working folder associations are not lost when simply closing the client and opening it, but rather when shutting down or going to stand by and then opening the client later ...