VS2005 & Vault Problem

[ncage1974]

Sorry if this has already been discussed but i have tried to search and find a topic similar to this with no luck.
Version info:
SourceGear 4.0.4
Windows XP
VS 2005 SP1

OK i have rebuilt my main machine that i code on (my sourcegear server piece resides on another machine). Before i rebuilt i was able to work with my projects just fine. After i rebuilt i reinstalled the client piece and set up my working folder and got the latest version of everything. Now every time i try to open a project i get an error. When i try to open a project from the file system i get the following error:
"The project <ProjectName> is under source control. An error occurred registering this project with source control. It is recommended that you do not make any changes to this project."
"the operation could not be completed. Unspecified error"

When i try to "open from vault" then nothing happens. It opens the sourcegear client window where i select the project file and then click ok but it does not error out and it never opens the project.

OK i have checked the current source control system and it does in fact say "SourceGear Vault Visual Studio 2005 client". I have tried to reinstall the sourcegear client thinking the integration piece might be screwed up. I have deleted my working directory and recreated it numerous times.

Please tell me someone knows whats going on ?

thanks
ncage

[lbauer]

Were you using Vault 4.0.4 prior to rebuilding your machine? If not, you may have been using a different integration client. You could either change back to the previous integration client (VS 2003) or unbind and rebind your projects to the VS 2005 style integration.

Some links that might be helpful:


http://support.sourcegear.com/viewtopic.php?t=8535

http://support.sourcegear.com/viewtopic.php?t=8214

If you were using 4.0.4 before, what happens when you do a fresh open from source control?

This means
1 ) closing the Vault GUI client and Visual Studio,
2) deleting the client side cache, http://support.sourcegear.com/viewtopic.php?t=6

3 ) deleting or backing up your projects on the local machine,
4) then re-launching Visual Studio and using the File->Open from Vault command.

[ncage1974]

First of all thanks linda for you time and for the reply. I will try to give you as much information as i can't. If you have any other questions then just let me know. I originally started using sourcegear in th 3.5 revision. I then upgraded my server/client to 4.0.4 revision. The server piece is hosted on Windows Server 2003 R2 x86. The client piece was using Vista x64. When i upgraded everything worked perfectly. In fact, most of the projects im trying to work on now were added to sourcegear after i upgraded. I got sick of a lot of poor support in Vista for drivers/apps so i decided to go back to xp until things looked better then reinstalled 4.0.4 client. I set my working directory with sourcegear and told it to force all subfolders "C:\Programming". I then simply just get the latest version of everything.

Ok i tried your suggestion and tried to close sourcegear client & vs 2005 and then clear out my cache. I then deleted my working folders. I then opened vs2005 and used open sourcegear project. I got the same exact error as before. I tried a couple different things also
I cleared the cache again and tried to both open from the file system and using "open source gear project" after i got the latest versions of the files and it did not work. Do you have anything else i can try ? I wanted to do a lot of work over the weekend and was stopped dead cold in my tracks

thanks,
ncage

[lbauer]

When you first added these projects, were they added with the VS 2003 integration client?

[ncage1974]

When you first added these projects, were they added with the VS 2003 integration client?

No unless maybe SourceGear 3.5 used VS 2003 integration client with VS2005? I have not used VS 2003 for a very very long time.

Ncage

[ncage1974]

Is there anyway i can unbind/rebind to take care of this problem?

thanks,
ncage

[lbauer]

Yes, previous versions of Vault used only VS 2003-style integration (called MSSCCI). It was used with both VS 2003 and VS 2005.

You could try closing your projects, then in VS 2005 under Tool->Options->SourceControl->Plugin, change to the Vault VS 2003 client for integration.

Then close VS 2005. In the Vault GUI Client on the same machine, under Tools-Options-General, check "Make Vault my default source control provider."

Open VS 2005 again, make sure the VS 2003 plugin is still selected, then try a fresh open from Source Control to a new working directory, using the File->Source Control->Open from Source Control menu.

If you continue to experience difficulty, we could schedule a remote session so we can see what's going on. Let me know.