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

Notification

Icon
Error

NCrunch Enabled but failing to start on VS 2019
AndyLowry
#1 Posted : Tuesday, October 29, 2019 5:24:30 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/4/2012(UTC)
Posts: 8
Location: United Kingdom

Thanks: 2 times
Was thanked: 1 time(s) in 1 post(s)
Hi,

At some point over the last few days nCrunch stopped working for me in VS 2019. The bottom right indicator is grey, and the Tests Window is telling me to enable nCrunch but it is enabled from the menu,

Turning on logging gives me this at startup:

[17:12:58.1377-UI-1] Initialising Package Integration
[17:12:58.1577-UI-1] GetServiceLocal for Microsoft.VisualStudio.Shell.Interop.SVsShell
[17:12:58.1587-UI-1] Package initialisation is complete. Running under VS2019
[17:12:58.1597-UI-1] NCrunch Package Initialisation time is 00:00:00.770 started at 17:12:57.3877
[17:12:58.1657-UI-1] GetServiceLocal for Microsoft.VisualStudio.Shell.Interop.SDTE
[17:12:58.1687-UI-1] Initialising automation integration for NCrunch
[17:12:58.2127-UI-1] Registering menu options
[17:12:58.2137-UI-1] GetServiceLocal for System.ComponentModel.Design.IMenuCommandService
[17:12:58.2157-UI-1] getWindow for nCrunch.VSIntegration2010.ComponentConfigToolWindowPane
[17:12:58.3907-UI-1] getWindow for nCrunch.VSIntegration2010.GridManagementToolWindowPane
[17:12:58.4527-UI-1] getWindow for nCrunch.VSIntegration2010.HotSpotsToolWindowPane
[17:12:58.4707-UI-1] getWindow for nCrunch.VSIntegration2010.MetricsToolWindowPane
[17:12:58.4947-UI-1] getWindow for nCrunch.VSIntegration2010.ProcessingQueueToolWindowPane
[17:12:58.5207-UI-1] getWindow for nCrunch.VSIntegration2010.TestsToolWindowPane
[17:12:58.5857-UI-1] getWindow for nCrunch.VSIntegration2010.StatusIndicatorToolWindowPane
[17:12:58.6077-UI-1] Hooking up WPF integration
[17:12:58.6117-UI-1] NCrunch Automation Initialisation time is 00:00:00.442
[17:12:58.6117-UI-1] Total startup time including initialisation took: 0:00:01.2239975
[17:12:58.6117-UI-1] Switching to UI thread took: 00:00:00.0007037
[17:12:58.6117-UI-1] Cached Initialisation message at 2019-10-29T17:12:57, message: GetServiceLocal for Microsoft.VisualStudio.Shell.Interop.IVsSolutionBuildManager
[17:13:17.4423-Core-50] ERROR (Internal): nCrunch.TaskRunner.Ipc.IpcConnectionClosedException: The connection has been closed
at nCrunch.TaskRunner.Ipc.Fast.IpcReader.Initialise()
at nCrunch.TaskRunner.Ipc.Fast.IpcStream.Connect(String ipcName, Boolean isHost)
at nCrunch.TaskRunner.Ipc.Fast.FastIpcClient.Connect(String ipcName)
at nCrunch.Core.ProcessManagement.DefaultProcessLoader.ConnectToProcess(ExternalProcess externalProcess, ProcessLoadParameters parameters, Action`1 outOfBandMessageHandler)
at nCrunch.Core.ProcessManagement.ExternalProcessManager..()
at nCrunch.Common.PerformanceTracking.PerfTracker.TryTrackActivity(String name, Action activity)
at nCrunch.Core.ProcessManagement.ExternalProcessManager.(EffectiveProcessorArchitecture , ProcessLoadParameters )

[17:13:17.4442-Core-50] ERROR (Internal): nCrunch.TaskRunner.Ipc.IpcConnectionClosedException: The connection has been closed
at nCrunch.Core.ProcessManagement.ExternalProcessManager.(EffectiveProcessorArchitecture , ProcessLoadParameters )
at nCrunch.Core.ProcessManagement.ExternalProcessManager.LoadExternalProcess(ProcessLoadParameters parameters, GridClientId client)
at nCrunch.Client.EngineHosting.HostedEngineFactory.(EngineHostingStrategy , VisualStudioVersion )
at nCrunch.Client.EngineHosting.HostedEngineFactory.CreateHostedEngine(VisualStudioVersion visualStudioVersion)
at nCrunch.Client.EngineHosting.EngineHost.(SystemEnabledEvent )

We had some anti virus and GPO updates pushed to our machine around the point it started failing so these *could* be related to that. But unfortunately I can't roll those back to test for certain.

Any pointers towards things to look at would be appreciated.

Thanks

Andy

AndyLowry
#2 Posted : Tuesday, October 29, 2019 6:13:54 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/4/2012(UTC)
Posts: 8
Location: United Kingdom

Thanks: 2 times
Was thanked: 1 time(s) in 1 post(s)
Found some more information in the event viewer, look like the EngineHost is crashing with a Data Execution Prevention Exception or buffer overflow:

Fault bucket 2081547624354767864, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: nCrunch.EngineHost462.x64.exe
P2: 3.31.0.3
P3: 5d81c6fb
P4: StackHash_7222
P5: 0.0.0.0
P6: 00000000
P7: PCH_B6_FROM_unknown+0x0000000000000000
P8: c0000005
P9: 0000000000000008
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7A94.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7AE3.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B42.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B4F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7B9E.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_nCrunch.EngineHo_2a2f8ac52df60a143f41783c38028e16ad3255a_76339fe1_6895e64a-47e3-4ddc-a7e2-38c2cc575e55

Analysis symbol:
Rechecking for solution: 0
Report Id: c89de58a-4233-43ba-be66-04ac33798625
Report Status: 268435456
Hashed bucket: 02bf4beb5cf16dc7dce324892cb963f8
Cab Guid: 0
Remco
#3 Posted : Tuesday, October 29, 2019 10:11:40 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 753 times
Was thanked: 972 time(s) in 926 post(s)
Hi, thanks for sharing this problem.

Given the unmanaged exception and the manner in which the engine process is disappearing, this looks to be either caused by interference with the .EXE (i.e. by virus scanner), or a deeper issue with the .NET platform or the state of your OS/Machine.

Do you have any options available to deactivate your virus scanner or exclude it from operating in the NCrunch installation directory?

Can you try uninstalling and reinstalling the latest version of NCrunch?
1 user thanked Remco for this useful post.
AndyLowry on 10/30/2019(UTC)
AndyLowry
#4 Posted : Wednesday, October 30, 2019 10:00:18 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 12/4/2012(UTC)
Posts: 8
Location: United Kingdom

Thanks: 2 times
Was thanked: 1 time(s) in 1 post(s)
OK, I think I've fixed it.

I'm using VS 2019 but still have VS 2017 installed.

Removing nCrunch for VS 2017 (which will be very old by now) nCrunch for VS 2019 has started working.

Feels like a combination of things going wrong, I've been thinking along the same lines as you that a virus checker is probably to blame. (e.g. We've recently had an issue with Chrome caused by our virus checker)

Thanks for you help.

Andy
1 user thanked AndyLowry for this useful post.
michaelkroes on 10/30/2019(UTC)
Remco
#5 Posted : Wednesday, October 30, 2019 10:51:27 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 753 times
Was thanked: 972 time(s) in 926 post(s)
I'm glad to hear you managed to solve this.

We tend to be targeted a bit unfairly by false positives on scanners, probably because we build runtime environments and instrument assemblies. Failures like this can be a bit problematic because they're so hard to troubleshoot. Nice work on figuring it out.
1 user thanked Remco for this useful post.
AndyLowry on 10/30/2019(UTC)
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.045 seconds.