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