Failed to register project with Vault Enhanced Client

[robe070]

Hi,

We have a machine that now throws this exception everytime any project is opened in Visual Studio:

Failed to register project <project> with SourceGear Vault Visual Studio Enhanced Client.
The type initializer for 'SourceGearLC.VaultVsipClient.RepositorySettings' threw an exception.

The server log does not contain an exception.

Do you have any idea how to fix this?

It first occurred with 4.1.3 on Friday. We have since upgraded to 5.0.3. We have uninstalled and re-installed Vault. We have repaired Visua Studio 2008. We are right now uninstalling Visual Studio and re-installing it.

[Beth]

This is specifically a client-side error.

Which OS are you installing on?

After you reinstall VS 2008, you will want to reinstall Vault again. Vault has to be installed after VS in order for the IDE integration to work.

On the other machines, which client is the project bound to? Is it the Vault Classic or the Vault Enhanced Client?

[robe070]

There is nothing at a high level about this machine that is special! But of course something is different. Same OS as others, same hardware, same VS, all using Enhanced Client, etc.

VS Install has now finished. Vault has been re-installed. It still has the same error.

[Beth]

Still, knowing the OS might help narrow the issue down.

There should be an install log in %username\local settings\temp called vault_client_install.log. Could you either post that log here (you will be able to delete it after we troubleshoot) or send it in an email to support at sourcegear.com (attn: Beth) with a link to this forum thread?

[robe070]

Hi Beth,

We've fixed it.

VsipClientProjectSettings.xml in the VsipSccClient folder in the cache directory was full of blanks. No legible text.

We deleted the file and it now works fine.

Thanks for your help

[robe070]

Note that there was a blue-screen of death immediately preceeding the onset of this issue. So we presume that that caused the corruption of the file.

It was almost the very first thing done on Monday morning after a re-boot. Opened up email, spent 10 mins reading the email. Started Visual Studio 2008, maybe opened a solution, and within no more than 60 seconds the blue screen occurred. Presumably the ABEND of Windows corrupted the file.

[Beth]

I could see a blue screen messing up a file. Thanks for the update.

[obrion]

I ran into this exact same issue and deleting the file for for me as well. Thank you for posting the solution! My issue was caused by the laptop locking up and requiring a forced power off, so it is understandable that the file was invalid. Very helpful to know WHICH file needed to be removed.

[Beth]

Thank you for confirming the behavior. This will help other users.

[mchargue]

Having some trouble locating the 'XML' file under windows 7. Can you post the directory, please?

[Beth]

The folder called VsipSccClient resides in %username%\appdata\local\SourceGear\ or possibly one folder lower in the Vault_1 folder.

[mmorris]

We ran into this problem too.

1) A possible solution for SourceGear to consider implementing is below. ('Possible solution')
2) This was challenging to debug as VS produced so many red herring error messages. I've included the error messages which we saw for future reference.
3) The solution worked perfectly, but only after finding it on this forum. We tried many other things first due to the VS red herring error messages. Vault itself was not producing any error messages (as only its interaction with Visual Studio was a problem).

Images Error_1, Error_2, Error_3: The first three error message showed up after installing the VS 2012 (with the current upgrades from Tools and Extensions, etc.)... and likely 2 were appearing after the initial crash.

Error_1.png (5.62 KiB) Viewed 52852 times

Error_2.png (8.31 KiB) Viewed 52852 times

Error_3.png (7.47 KiB) Viewed 52852 times

Images Error_4, Error_5: After the initial re-install of VS 2012 (no updates) we were also getting the error messages 4 & 5.

Error_4.png (13.23 KiB) Viewed 52852 times

Error_5.png (7.59 KiB) Viewed 52852 times

Using Visual Studio 2012
Using ASP.NET 4.5
Windows 10
Reinstalled Vault and VS multiple times.

Also this error message was appearing in Visual Studio:
"Some of the properties associated with the solution could not be read. ...*.csproj : error : Error HRESULT E_FAIL has been returned from a call to a COM component."

Turns out you can temporarily solve the last bit by removing .suo file. A fun fact, but not really a solution.
You can also temporarily load the project be removing 4 lines of data in the project file.
But, the actual solution is the one above.

Please note that in our case too this error occurred after the computer crashed due to overheating.

Possible solution: Perhaps a future version of vault can check for blank copies of this xml file when access by a user? Is there any reason for Vault to keep blank version of this file?

For the rare cases when this occurs, such a solution might save users a considerable amount of time and effort.

Thank you.

[Beth]

Thank you for the additional information. I have this logged for the developers.

[mmorris]

I'm not sure if this needs to be different subject, but the same solution (plus one step) solved a completely different error.

Error: Microsoft.VisualStudio.Web.Application.pdb not loaded

On one of our computers, Visual Studio 2012 (with Vault Standard 10.0) just stopped working. This only occurred on Projects which were connected to Vault. Several other computers with similar installations were fine.

By changing the file (really just the inner lines) of
username/AppData/Local/SourceGear/VsipSccClient/VsipClientProjectSettings
<ProjectSettings Version="1">
REMOVING THE LINES IN HERE
</ProjectSettings>,

and then restarting the computer solved the issue.

Strangely removing the file alone didn't help because it seemed like the bad file info was in memory... and still being used until the computer was restarted.

The issue gave the following error among others:

VS2012_Vault_bug.png (45.58 KiB) Viewed 52481 times

Another clue it was Vault-related was that the Project load (for VS projects that used Vault) would stop about the time that Visual Studio tried to connect with Vault.

The error message (as shown in the screen) of Microsoft.VisualStudio.Web.Application.pdb not loaded leads to very scary corners of the internet in which answers are hidden behind arcane doors not meant for mortal's prying eyes. Perhaps the answer would have shown up with additional searching, but it wasn't looking promising.

[Beth]

Thank you for posting the additional information.