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

Notification

Icon
Error
2 Pages12>
ncrunch 2019 Chocolatey installer doesn't seem to detect VS 2019
Options
Previous Topic Next Topic
SeanKilleen
#1 Posted : Friday, April 5, 2019 2:28:31 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/21/2014(UTC)
Posts: 7
Location: United States of America

Thanks: 1 times
Was thanked: 1 time(s) in 1 post(s)
Hey! Thought you'd want to be aware of this.

I prefer chocolatey for installing packages and saw that NCrunch was on offer. I previously installed 2017 there but now installed 2019 as well.

I have VS 2019 Enterprise (v16.0.0) after launch, but this affected the preview as well.

I run "choco install ncrunch-vs2019" and see an error. Upon looking at the logs, I see:

Quote:
Visual Studio 2019 was not detected on this system. If this is incorrect, you will need to install this product manually using a ZIP file from the NCrunch website.


I'm fine to install the zip file, but thought you might want to know that the installer wasn't detecting VS 2019 on a machine where it definitely is installed.
Back to top
michaelkroes
#2 Posted : Friday, April 5, 2019 2:32:04 AM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 306
Location: Netherlands

Thanks: 138 times
Was thanked: 73 time(s) in 69 post(s)
Hi thanks for posting

We haven't build the chocolatey packages. Would you mind checking if you have the same issue when you try the msi from the website?
Back to top
SeanKilleen
#3 Posted : Friday, April 5, 2019 3:12:23 AM(UTC)
Rank: Newbie

Groups: Registered
Joined: 5/21/2014(UTC)
Posts: 7
Location: United States of America

Thanks: 1 times
Was thanked: 1 time(s) in 1 post(s)
Sorry, I should have been clear -- the MSI installer from the web site appears to work correctly.

I mistakenly thought this was put out by the team; I'll reach out to the chocolatey package maintainer to submit the issue. Thanks!
Back to top
MatthewSteeples
#4 Posted : Thursday, April 25, 2019 6:17:05 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 142
Location: United Kingdom

Thanks: 7 times
Was thanked: 19 time(s) in 17 post(s)
Possibly in a similar vein to this, we're having issues deploying the MSI out through InTune (Microsoft's management portal). The devs appear to be able to run the MSI locally, but installing (for the user) through the management utility fails with the following message in the event log:

Code:
Product: NCrunch for Visual Studio 2019 -- Visual Studio 2019 was not detected on this system.  If this is incorrect, you will need to install this product manually using a ZIP file from the NCrunch website.


I'm assuming there's some custom code that runs as part of the MSI to determine where VS is installed?
Back to top
Remco
#5 Posted : Thursday, April 25, 2019 6:44:36 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,161

Thanks: 964 times
Was thanked: 1296 time(s) in 1202 post(s)
MatthewSteeples;13419 wrote:

I'm assuming there's some custom code that runs as part of the MSI to determine where VS is installed?


The MSI makes a call to a COM component published by MS that is intended to help tools find installations of Visual Studio

It's been our observation that this COM component is not very reliable. We implemented a range of fallbacks into the installer to try and find the VS instance for when it fails. If you're seeing this message, it means that not only did the MS component fail, but none of our fallbacks were able to locate the instance either.

I have no experience with InTune or what its limitations are, so unfortunately I'm unable to help troubleshoot it. Is it possible this could be security related? If something in the process is blocking the MSI from interacting with the registry, file system, COM, etc .. then the experience could be different to running the MSI directly. If possible, I'd suggest trying an xcopy using the ZIP installer if InTune supports anything like this.
Back to top
MatthewSteeples
#6 Posted : Thursday, April 25, 2019 7:38:11 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 142
Location: United Kingdom

Thanks: 7 times
Was thanked: 19 time(s) in 17 post(s)
I don't know if it helps at all, but it appears to be trying to use the following folder to "install" into:

C:\Program Files (x86)\FirstInstall\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2019\

Looking in ProcessMonitor it looks to have found devenv at some point but it's then ignoring it (assuming I'm looking at the right process) - https://ledgerscope-my.sharepoint.com/:i:/p/matthew/Ec5yoVYCaEJEvOb8Gx4Vz80BjAcliDbQ03aQ1r7LNYUnQw?e=EVdAcT
Back to top
michaelkroes
#7 Posted : Thursday, April 25, 2019 10:42:46 AM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 306
Location: Netherlands

Thanks: 138 times
Was thanked: 73 time(s) in 69 post(s)
The FirstInstall is the default directory, that will be replaced once we find the correct path.

Can you run the setup via InTune with different parameters? Maybe like this:

msiexec /i "C:\Temp\NCrunch_VS2019_3.XX.0.0.msi" /l*v "C:\Temp\MSI_Installer.log"

This should show the choices about the paths made by the installer. Maybe that will give you some more information.
Back to top
MatthewSteeples
#8 Posted : Thursday, April 25, 2019 10:55:57 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 142
Location: United Kingdom

Thanks: 7 times
Was thanked: 19 time(s) in 17 post(s)
File is here

For reference, my VS is installed in the standard place (C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE) and I'm on 16.0.2

This is now happening on this machine _not_ under InTune, just standard installer method
Back to top
michaelkroes
#9 Posted : Thursday, April 25, 2019 11:02:45 AM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 306
Location: Netherlands

Thanks: 138 times
Was thanked: 73 time(s) in 69 post(s)
Calling custom action NCrunch.CustomInstallActions!NCrunch.CustomInstallActions.VsInstallHelper.IsVs2019Installed
Executing FindVs2019InstallPath
Found Visual Studio instance via COM: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise
Found Visual Studio instance via filesystem: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise
Found unique VS Install path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise
Using VS Install path: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise
MSI (c) (E4!6C) [11:52:45:958]: PROPERTY CHANGE: Adding VSPATH property. Its value is 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise'.
MSI (c) (E4!6C) [11:52:45:958]: PROPERTY CHANGE: Adding VSINSTALLED property. Its value is '1'.
Action ended 11:52:45: CheckVsInstalledAction. Return value 1.

So as expected we find the install location using the normal VS scheme and the fallback. This means that the system is properly configured. I'm not sure why intune can't find the install path using just the file system. I hope this gives you at least a hint to determine why running the MSI via InTune can't find the directories? Maybe reading the filesystem is somehow disabled? Maybe the same for the registry?
Back to top
MatthewSteeples
#10 Posted : Thursday, April 25, 2019 11:06:34 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 142
Location: United Kingdom

Thanks: 7 times
Was thanked: 19 time(s) in 17 post(s)
Sorry, I should have been clearer. This was me running the MSI from the command prompt and it still fails with the same error message (just after the 11:52:48:488 timestamp)
Back to top
michaelkroes
#11 Posted : Thursday, April 25, 2019 11:22:34 AM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 306
Location: Netherlands

Thanks: 138 times
Was thanked: 73 time(s) in 69 post(s)
Sorry I missed that. Would you mind checking if there's one or more NCrunch 2019 installs present under Add/Remove programs? Our beta versions accidentally didn't upgrade on the first version. Can you remove all of the 2019 installs and try again?
Back to top
MatthewSteeples
#12 Posted : Thursday, April 25, 2019 11:28:02 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 142
Location: United Kingdom

Thanks: 7 times
Was thanked: 19 time(s) in 17 post(s)
I have a 3.23.10 installed for 2017, and a 3.25.2 installed for 2019.

I don't actually have 2017 installed any more so I'm going to try and remove both of them
Back to top
MatthewSteeples
#13 Posted : Thursday, April 25, 2019 11:59:45 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 142
Location: United Kingdom

Thanks: 7 times
Was thanked: 19 time(s) in 17 post(s)
I'm unable to uninstall the 2017 version as I no longer have 2017 installed, but I suspect that it's still some InTune jiggery pokery going on. When loading the MSI, it then insists that it's going to install it from a copy that it's keeping in C:\Users\MatthewSteeples\AppData\Local\mdm.

The log for that can be found here.
Back to top
MatthewSteeples
#15 Posted : Thursday, April 25, 2019 12:59:16 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 142
Location: United Kingdom

Thanks: 7 times
Was thanked: 19 time(s) in 17 post(s)
We've definitely reached the limit of my understanding of how MSI works, but it would appear that InTune wants to install it in "Server" (headless or quiet) mode, but the checks are done in "Client" mode so are skipped. Does that mean anything to you?
Back to top
michaelkroes
#14 Posted : Saturday, April 27, 2019 5:55:01 AM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 306
Location: Netherlands

Thanks: 138 times
Was thanked: 73 time(s) in 69 post(s)
MatthewSteeples;13428 wrote:
I'm unable to uninstall the 2017 version as I no longer have 2017 installed, but I suspect that it's still some InTune jiggery pokery going on. When loading the MSI, it then insists that it's going to install it from a copy that it's keeping in C:\Users\MatthewSteeples\AppData\Local\mdm.

The log for that can be found here.


Is this run from InTune? From what I can see it isn't executing any of the checks. These checks are executed during the UI phase of the install, so it would seem it can't be run in headless mode.
Back to top
MatthewSteeples
#16 Posted : Sunday, April 28, 2019 3:52:45 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 142
Location: United Kingdom

Thanks: 7 times
Was thanked: 19 time(s) in 17 post(s)
Yes that was run from InTune. It runs installers in "unattended" mode, so there's no UI to speak of. I'm assuming there isn't anything you can change from your side to make the checks run not in the UI?
Back to top
michaelkroes
#17 Posted : Monday, April 29, 2019 1:50:39 PM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 306
Location: Netherlands

Thanks: 138 times
Was thanked: 73 time(s) in 69 post(s)
We’ve had a closer look at this in the code. We’ve prioritized a task for the coming release where we are going to try and tackle this.
Back to top
MatthewSteeples
#18 Posted : Monday, April 29, 2019 1:53:08 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 142
Location: United Kingdom

Thanks: 7 times
Was thanked: 19 time(s) in 17 post(s)
michaelkroes;13433 wrote:
We’ve had a closer look at this in the code. We’ve prioritized a task for the coming release where we are going to try and tackle this.


That's great. You know where we are if you'd like a tester :)
Back to top
michaelkroes
#19 Posted : Tuesday, April 30, 2019 6:10:47 PM(UTC)
Rank: NCrunch Developer

Groups: Registered
Joined: 9/22/2017(UTC)
Posts: 306
Location: Netherlands

Thanks: 138 times
Was thanked: 73 time(s) in 69 post(s)
Hi,

Would you mind trying this new version?

NCrunch_Console_3.27.0.2.msi
NCrunch_Console_3.27.0.2.zip
NCrunch_GridNodeServer_3.27.0.2.msi
NCrunch_GridNodeServer_3.27.0.2.zip
NCrunch_LicenseServer_3.27.0.2.zip
NCrunch_VS2008_3.27.0.2.msi
NCrunch_VS2010_3.27.0.2.msi
NCrunch_VS2010_3.27.0.2.zip
NCrunch_VS2012_3.27.0.2.msi
NCrunch_VS2012_3.27.0.2.zip
NCrunch_VS2013_3.27.0.2.msi
NCrunch_VS2013_3.27.0.2.zip
NCrunch_VS2015_3.27.0.2.msi
NCrunch_VS2015_3.27.0.2.msi.7z
NCrunch_VS2015_3.27.0.2.zip
NCrunch_VS2017_3.27.0.2.msi
NCrunch_VS2017_3.27.0.2.msi.7z
NCrunch_VS2017_3.27.0.2.zip
NCrunch_VS2019_3.27.0.2.msi
NCrunch_VS2019_3.27.0.2.msi.7z
NCrunch_VS2019_3.27.0.2.zip

Release notes for 3.27.0.2 since version v3.26.0.4

Removed the "Break into the first failing test" context menu when only one test is available.

Added support for quiet installations with the NCrunch for Visual Studio 2019 installer

Added support for version 4.8 of the .NET Framework.

Added initial support for rendering on screens with different pixel densities

Fixed an issue where the ASP.NET MVC test host integration was feeding assembly names into the framework incorrectly for projects with an output file name different to their project name.
Back to top
MatthewSteeples
#20 Posted : Thursday, May 2, 2019 7:31:24 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 142
Location: United Kingdom

Thanks: 7 times
Was thanked: 19 time(s) in 17 post(s)
Have given that one a try and we got a bit further. It identified where VS was installed but still failed on the install. Logs are here
Back to top
Users browsing this topic
Guest
2 Pages12>
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.094 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download