Setup ncrunch v3.2 ends real quick

Visual Studio 2017RC on Windows 10, all up to date
Resharper latest version

Tried to install ncrunch, but it ends before it starts copying files, real quick after pressing Install with following error.

NCrunch for Visual Studio 2017 Setup Wizard ended prematurely because of an error.
Your system has not been modified.
To install this program at a later time, run Setup Wizard again.
Click the Finish button to exit the Setup Wizard.

It does not specify the error.

What should I do ?

Hi,

Thanks for sharing this issue.

A manual installation is always an option here, but I'm wondering if we can get a log of the MSI itself to find out why it's failing.

This stack overflow article shows how to obtain a log from an MSI installation: https://stackoverflow.com/questions/7126077/create-an-msi-log-file#7130758.

If you're able to get hold of this log for me and post it here (or submit it via the support->contact form), I should be able to analyse this problem further.

Thanks!

Thanks for sending through the log.

Can you confirm which versions of the .NET framework you have installed on your machine?

I find in Windows\Microsoft.net\Framework the following directories
v1.0
v1.1
v2.0
v3.5
v4.0

in Windows\Microsoft.net\Framework64
v4.0

Looking in installed programs:

a bunch of Microsoft .Net related stuff only for 4.5 and 4.6. But they all say Multi-Targeting Pack or SDK . Nothing comprehensible for me here.

Interesting. The error from the MSI is as follows:

SFXCA: Extracting custom action to temporary directory: C:\Users\Dirk\AppData\Local\Temp\MSIDD25.tmp-\
SFXCA: Failed to get requested CLR info. Error code 0x80131700
SFXCA: Ensure that the proper version of the .NET Framework is installed, or that there is a matching supportedRuntime element in CustomAction.config. If you are binding to .NET 4 or greater add useLegacyV2RuntimeActivationPolicy=true to the <startup> element.
CustomAction FindVsInstallPathAction returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 8:49:42: FindVsInstallPathAction. Return value 3.
Action ended 8:49:42: INSTALL. Return value 3.

The custom action used to find the VS installation is compiled for .NET 3.5. Since it's an installer, I would have expected this would be forwards compatible, but it's possible that .NET 3.5 must be specifically installed on the machine. Is there any chance you could try an installer for .NET 3.5 to see if this solves the problem? If it does, we'll have identified with certainty that this is the cause of the problem .. and I can then evaluate compile options.

On Windows 10, .Net 3.5 is a Windows feature, so I switched it on.
After installation, I tried again and the installation ran fine.

A big thanks to you and great warm year ending wishes to you !

Great! Thanks for all your help. I'll see what I can do about improving this.

Same error here, but most likely a different cause. I already have the .NET Framework 3.5 pack installed (this is a Windows 10 64 bit install). Looking at the logs it's failing to find VS2017. I've emailed you the full log in case that error is normal.

My VS2017 is installed in a non-standard place (as I have a small C drive and a big D drive): "D:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\devenv.exe"

Calling custom action NCrunch.CustomInstallActions!NCrunch.CustomInstallActions.VsInstallHelper.FindVs2017InstallPath
Executing FindVs2017InstallPath
Exception thrown by custom action:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Deployment.WindowsInstaller.InstallCanceledException: Unable to find an installation of VS2017. You may need to install this product manually.
at NCrunch.CustomInstallActions.VsInstallHelper.getInstallPath(Int32 vsMajorVersion)
at NCrunch.CustomInstallActions.VsInstallHelper.FindVs2017InstallPath(Session session)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture)
at Microsoft.Deployment.WindowsInstaller.CustomActionProxy.InvokeCustomAction(Int32 sessionHandle, String entryPoint, IntPtr remotingDelegatePtr)
CustomAction FindVsInstallPathAction returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 22:54:46: FindVsInstallPathAction. Return value 3.
Action ended 22:54:46: INSTALL. Return value 3.

Hi Matthew,

This looks to be caused by a failing VS2017 component. It's the same problem as reported by Thomas here - http://forum.ncrunch.net/yaf_postsm9662_ncrunch-menu-missing-from-vs2017.aspx#post9662.

I'll try to troubleshoot these problems together.

I just tried a new NCrunch install to a fresh copy of Win10 and VS2017 RC.

The MSI would start, accept EULA and click ok, and then Error Dialog stating the installed failed and no changes made.
Manual install failed as well with an constant error on VS2017 startup.

Did an install log using:
msiexec /i "NCrunch_VS2017_3.2.0.3.msi" /l*v "log.log"

I got this error down in the middle of the log where it exited (bolded):

MSI (s) (D0:10) [14:11:01:314]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI9FC1.tmp, Entrypoint: FindVs2017InstallPath
MSI (s) (D0:08) [14:11:01:315]: Generating random cookie.
MSI (s) (D0:08) [14:11:01:316]: Created Custom Action Server with PID 4760 (0x1298).
MSI (s) (D0:68) [14:11:01:342]: Running as a service.
MSI (s) (D0:68) [14:11:01:344]: Hello, I'm your 32bit Impersonated custom action server.
SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI9FC1.tmp-\
SFXCA: Failed to get requested CLR info. Error code 0x80131700
SFXCA: Ensure that the proper version of the .NET Framework is installed, or that there is a matching supportedRuntime element in CustomAction.config. If you are binding to .NET 4 or greater add useLegacyV2RuntimeActivationPolicy=true to the <startup> element.
CustomAction FindVsInstallPathAction returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 14:11:01: FindVsInstallPathAction. Return value 3.
Action ended 14:11:01: INSTALL. Return value 3.


Reading above about .NET 3.5, I went into Programs / Turn Windows features on and off and .NET 3.5 was NOT installed.
Selected .NET 3.5 and installed.
The MSI now runs to completion, and VS2017 starts up with NCrunch in the menu.

Thanks Smobley. Sorry for the trouble here. The v3.2 VS2017 installer has a dependency on .NET 3.5. There is a fix coming for this in the next release.

NCrunch v3.3 is now available including a fix for this issue - https://www.ncrunch.net/download.