Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Visual Studio 2017 gives an error message "nCrunch package did not load correctly" at startup
rsullivan
#1 Posted : Thursday, October 19, 2017 9:29:27 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 10/19/2017(UTC)
Posts: 2
Location: United States of America

Thanks: 1 times
I'm a trial account using NCrunch, and in the last day or two, the NCrunch addin to Visual Studio 2017 stopped loading.

I get this error popup every time that Visual Studio starts:

rsullivan's NCrunch Loan Failure in Visual Studio 2017.

After Visual Studio starts, when I click on any item in the NCrunch menu, I get the same popup. Nothing in NCrunch works.

I have looked at the ActivityLog.xml file, and it seems like NCrunch is crashing when it attempts to load its configuration information. Judge for yourself:

<entry>
<record>1047</record>
<time>2017/10/19 21:03:32.034</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Begin package load [nCrunch.VSIntegration2010.CrunchPackage, nCrunch.VSIntegration2017, Version=3.11.0.9, Culture=neutral, PublicKeyToken=01d101bf6f3e0aea]</description>
<guid>{14D2CAB3-EE7F-496E-BF5D-C67D2CBDD84D}</guid>
</entry>
<entry>
<record>1048</record>
<time>2017/10/19 21:03:32.893</time>
<type>Error</type>
<source>VisualStudio</source>
<description>LegacySitePackage failed for package [nCrunch.VSIntegration2010.CrunchPackage, nCrunch.VSIntegration2017, Version=3.11.0.9, Culture=neutral, PublicKeyToken=01d101bf6f3e0aea]Source: &apos;mscorlib&apos; Description: Input string was not in a correct format.&#x000D;&#x000A;System.FormatException: Input string was not in a correct format.&#x000D;&#x000A; at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer&amp; number, NumberFormatInfo info, Boolean parseDecimal)&#x000D;&#x000A; at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)&#x000D;&#x000A; at nCrunch.Core.Configuration.CPUCoreConfigHelper.&#x0002;.&#x0003;(String &#x0002;)&#x000D;&#x000A; at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()&#x000D;&#x000A; at nCrunch.Core.Configuration.CPUCoreConfigHelper.GetCoreMaskFromCoreDescriptor(String coreDescriptor)&#x000D;&#x000A; at nCrunch.Client.ClientThreadAffinitiser.ApplyProcessorAffinityToAllThreads()&#x000D;&#x000A; at nCrunch.VSAddIn.VsServiceInitialiser.InitialiseServiceLocator(Boolean isVSRuntimeEnvironment, Nullable`1 vsVersion)&#x000D;&#x000A; at nCrunch.WpfUI.WpfServiceInitialiser.InitialiseServiceLocator(Boolean isRuntimeEnvironment, Nullable`1 vsVersion)&#x000D;&#x000A; at nCrunch.VSIntegration2010.CrunchPackage.Initialize()&#x000D;&#x000A; at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp)</description>
<guid>{14D2CAB3-EE7F-496E-BF5D-C67D2CBDD84D}</guid>
<hr>80131537</hr>
<errorinfo></errorinfo>
</entry>
<entry>
<record>1049</record>
<time>2017/10/19 21:03:32.909</time>
<type>Error</type>
<source>VisualStudio</source>
<description>SetSite failed for package [nCrunch.VSIntegration2010.CrunchPackage, nCrunch.VSIntegration2017, Version=3.11.0.9, Culture=neutral, PublicKeyToken=01d101bf6f3e0aea](null)</description>
<guid>{14D2CAB3-EE7F-496E-BF5D-C67D2CBDD84D}</guid>
<hr>80131537</hr>
<errorinfo></errorinfo>
</entry>
<entry>
<record>1050</record>
<time>2017/10/19 21:03:32.909</time>
<type>Error</type>
<source>VisualStudio</source>
<description>End package load [nCrunch.VSIntegration2010.CrunchPackage, nCrunch.VSIntegration2017, Version=3.11.0.9, Culture=neutral, PublicKeyToken=01d101bf6f3e0aea]</description>
<guid>{14D2CAB3-EE7F-496E-BF5D-C67D2CBDD84D}</guid>
<hr>80131537</hr>
<errorinfo></errorinfo>
</entry>


I would be happy to nuke/reset the NCrunch configuration, but I don't how.

I have attempted to reinstall and fix using the reinstall instructions, with no luck. In the reinstall instructions, it says to "Using windows explorer, browse to the directory: \Program Files (x86)\Microsoft Visual Studio\2017\{VERSION}\Common7\IDE\Extensions\Remco Software". I found the Extensions folder, but the "Remco Software" folder didn't exist after uninstalling NCrunch. I have verified that it gets created after installation, so I'm 100% sure that the uninstalling NCrunch removes this folder for me (leaving no remnants that need to be deleted).

I have even uninstall NCrunch and uninstalled Visual Studio 2017, and still get the same error.

If I cannot get this to run, I'll have to report to my group that I cannot get NCrunch working without wiping out my computer and re-installing everything. I'm evaluating this software (with another developer), so I recommend that you help me out, or else this will be a black mark in our report. Prior to this problem, I was really impressed!

Please help!
Remco
#2 Posted : Thursday, October 19, 2017 11:37:47 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 5,234

Thanks: 691 times
Was thanked: 843 time(s) in 803 post(s)
Hi, thanks for sharing this problem.

You are correct in your understanding that this is caused by a configuration corruption issue. We have a fix pending for this issue in the next release, though it still isn't clear how it's possible for the config to get into this state.

To reset your configuration, delete the config file at C:\Users\USER\AppData\Roaming\NCrunch
1 user thanked Remco for this useful post.
rsullivan on 10/20/2017(UTC)
rsullivan
#3 Posted : Friday, October 20, 2017 12:11:50 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 10/19/2017(UTC)
Posts: 2
Location: United States of America

Thanks: 1 times
Remco;11382 wrote:
Hi, thanks for sharing this problem.

You are correct in your understanding that this is caused by a configuration corruption issue. We have a fix pending for this issue in the next release, though it still isn't clear how it's possible for the config to get into this state.

To reset your configuration, delete the config file at C:\Users\USER\AppData\Roaming\NCrunch


That worked! My NCrunch is working again!

Thank you!
dwallace
#4 Posted : Thursday, November 30, 2017 9:10:24 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/16/2017(UTC)
Posts: 3
Location: United States of America

Was thanked: 1 time(s) in 1 post(s)
I also encountered this issue after installing the latest NCrunch Update (3.12.0.15). After following the advice above as well as doing a full reinstall and devenv setup as described in the NCrunch docs, I had additional problems. While the installation wizard completed every time I ran the msi installer, the NCrunch extension did not appear in Visual Studio.

Finally, I figured out that the NCrunch installer was putting the files into the preview version of VS that was installed on my machine (parallel to the production release version of VS).

I uninstalled the preview version of VS. Then I installed the latest NCrunch update. After several hours of chasing my tail, everything seems to be working again.

Two lessons learned:

1. The NCrunch installer selects the preview version of VS to install the extension in. (Since running parallel production and preview versions of VS is supported by Microsoft, could the installer be given the intelligence to install for both? Or at least default to production?)

2. I still can’t be certain of what triggered the initial error (as identified at the top of this forum thread), but I suspect it may be related to the parallel VS installations. I’m certain this was the cause of the second issue.

Hopefully this will help someone.
Remco
#5 Posted : Thursday, November 30, 2017 11:02:51 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 5,234

Thanks: 691 times
Was thanked: 843 time(s) in 803 post(s)
Thanks for sharing this.

dwallace;11588 wrote:

1. The NCrunch installer selects the preview version of VS to install the extension in. (Since running parallel production and preview versions of VS is supported by Microsoft, could the installer be given the intelligence to install for both? Or at least default to production?)


Right now the installer does not work with multiple installations of the same version of VS. This is due to the limitations of MSIs in general, which just aren't sophisticated enough to be able to handle this scenario. We're aware of the problem and are trying to find a solution.

dwallace;11588 wrote:

2. I still can’t be certain of what triggered the initial error (as identified at the top of this forum thread), but I suspect it may be related to the parallel VS installations. I’m certain this was the cause of the second issue.


VS2017 seems to be having some problems at the moment with the package cache not being refreshed when it should be. This looks to be a new thing, and it seems to be inconsistent. I'm not sure what we can do about this from the NCrunch side other than forcing the installation to run /setup every time, which is something I would prefer to avoid (as we then get other problems).
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.072 seconds.