Error registering project

[Gary_Berg]

I've got a solution consisting of 16 projects. I had to crash my development machine while this solution was open. When I try to open the solution, for each project I get a message:

Code: Select all

Failed to register project XXXX with SourceGear Vault Visual Studio Enhanced Client.

The type initializer for 'SourceGearLLC.VaultVSIPClient.RepositorySettings' threw an exception.

Once I get the solution open, all the projects are listed but say they are unavailable, that the project cannot be opened.

I can use the Vault client and log in to the repository without a problem, it is only the VS2010 IDE that is giving me trouble.

I'm running Vault v6.1.0.531

How do I correct this problem?

Thanks,

[Beth]

Try removing one of the projects that won't load from the solution and add that project back to the solution. What happens to that project?

[Gary_Berg]

Beth,

Well, that didn't work. I tried removing one project from the Solution; I couldn't add it back in as it thought there was a project with that name in the solution. So I tried to save the Solution to disk, and it couldn't as it was R/O.

Project and solution files are all R/O as they are under Vault control.

I saved the solution under a different name and was able to re-add the project, but it got the same error.

The solution shows a tree under it, but also at the right of the solution name it shows (0 projects).

I'm wondering if the saved Vault access information (credentials) is corrupt, or if the programmed interface to VS2010 is messed up?

I did some checking, the solution and project files on disk are identical to what is in the Vault.

[Gary_Berg]

Found the problem in the support forum:
http://support.sourcegear.com/viewtopic ... er+project

As Rob Goodridge stated, "VsipClientProjectSettings.xml in the VsipSccClient folder in the cache directory was full of blanks". Looked to be full of nulls from what I could tell. I'm guessing this is where the Vault client stores the login credentials if you store them. Looks like the password is stored scrambled, too - GOOD!

So any way, I too suffered a lockup of the VM when this problem happened. Must have corrupted this file.

Gary Berg

[Beth]

Thanks for the update. I'm happy to hear you are working again.