Package Load Failure

If you are having a problem using Vault, post a message here.
Post Reply
baclay
Posts: 12
Joined: Mon Dec 12, 2011 1:36 pm

Package Load Failure

Post by baclay » Thu Dec 13, 2018 1:15 pm

I'm using Visual Studio 2008 with Vault Pro 10.0.2 on Windows 10 Professional

I have successfully been using the client for months and all of a sudden today when I start Visual Studio I get this error:

Package Load Failure

Package 'SourceGearLLC.VaultVsipClient, VaultVsipClient Version=10.0.2.30936, Culture=neutral, PublicKeyToken= d0dd1817f18e65b3 has failed to load properly (GUID = {7BE9CE03-56BF-4682-9C06-78C68B134B30}). Please contact package vendor for assistance. Application restart is recommended, due to possible environment corruption. Would you like to disable loading this package in the future? You may use 'devenv /resetskippkgs' to re-enable package loading.

I uninstalled the client and re-installed which did not fix it.

I uninstalled the Client, started Visual Studio and it started up fine although it prompted me about source being under source control. I re-installed the Client, started Visual Studio and the message appeared again.

Any suggestions would greatly be appreciated.

Barry

Tonya
Posts: 866
Joined: Thu Jan 20, 2005 1:47 pm
Location: SourceGear

Re: Package Load Failure

Post by Tonya » Fri Dec 14, 2018 9:42 am

Hi Barry,

Our first suggestion is to run the Visual Studio 2008 repair wizard. The error indicates there may be a potential issue with the setup of Visual Studio. If the repair wizard doesn't help, please let us know.

Thanks,

Tonya

baclay
Posts: 12
Joined: Mon Dec 12, 2011 1:36 pm

Re: Package Load Failure

Post by baclay » Fri Dec 14, 2018 3:43 pm

Actually I google'ed the error and tried one of the suggestions which was uninstall .Net 3.5 and then reinstall which fixed the problem for me.

Thanks for your reply. If it happens again, I'll try your suggestion as well.

Tonya
Posts: 866
Joined: Thu Jan 20, 2005 1:47 pm
Location: SourceGear

Re: Package Load Failure

Post by Tonya » Fri Dec 14, 2018 4:41 pm

Thank you for the update. Glad to hear that the problem is resolved.

Tonya

Post Reply