Setup: Az installed (msi) failing a check for .Net framework on machine with .Net 4.7.2 #11542
Comments
|
many MSI issues depend on environment and cannot be reproduced locally . We have to collect more information before fix. One proven workaround is copy modules from an installed machine to airgapped machine. The modules are installed under %USER_DOCUMENTS%\WindowsPowerShell\Modules for Windows PowerShell or %USER_DOCUMENTS%\PowerShell\Modules for PowerShell Core. |
|
@Manishd79, please me know your OS version. In addition, does current user have admin permission? |
|
@dingmeng-xue |
|
Hello Dingmeng
Apologies for late reply.
This was attempted on a win 2016 server with .Net 4.7.2
Yes, the logged in user is an admin on the machine.
Thx
Manish
…Sent from my iPhone
On Apr 13, 2020, at 2:52 AM, Dingmeng Xue ***@***.***> wrote:
@Manishd79, please me know your OS version. In addition, does current user have admin permission?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
=== Verbose logging started: 7/15/2020 10:09:03 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\Windows\system32\msiexec.exe === MSI (c) (24:D4) [10:09:03:923]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg MSI (c) (24:E0) [10:09:04:032]: Resetting cached policy values MSI (c) (24:E0) [10:09:10:898]: Windows Installer installed the product. Product Name: Microsoft Azure PowerShell - June 2020. Product Version: 4.3.0.55658. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603. MSI (c) (24:E0) [10:09:10:898]: Grabbed execution mutex. |
|
DON'T - I REPEAT DON'T shoot the messenger. I've got it working after installing .NET 4.6.2. and 3.5. Sigh. |
Description
Az installer (.msi) is failing to install on a machine with .Net framework 4.7.2. The installer log has following details for the failure
MSI (s) (10:4C) [17:34:00:094]: Doing action: InstallerChecks
MSI (s) (10:4C) [17:34:00:094]: Note: 1: 2205 2: 3: ActionText
Action 17:34:00: InstallerChecks.
Action start 17:34:00: InstallerChecks.
MSI (s) (10:A0) [17:34:00:094]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI36C7.tmp, Entrypoint: CheckForAzureRm
MSI (s) (10:08) [17:34:00:094]: Generating random cookie.
MSI (s) (10:08) [17:34:00:094]: Created Custom Action Server with PID 6156 (0x180C).
MSI (s) (10:18) [17:34:00:125]: Running as a service.
MSI (s) (10:18) [17:34:00:125]: Hello, I'm your 64bit Impersonated custom action server.
SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI36C7.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 element.
CustomAction InstallerChecks returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 17:34:00: InstallerChecks. Return value 3.
Action ended 17:34:00: INSTALL. Return value 3.
Steps to reproduce
Have a machine where you need to install the Az via installer option. This could be a machine where internet connection not works. Install the .Net 4.7.2 on the machine using offline installer. Then try the Az msi
Environment data
Module versions
Directory: C:\Program Files\Microsoft Monitoring Agent\Agent\PowerShell
ModuleType Version Name ExportedCommands
Binary 1.0.0.0 Microsoft.MonitoringAgent.PowerS... {Checkpoint-WebApplicationMonitoring, Get-WebApplicationMo...
Debug output
Error output
The text was updated successfully, but these errors were encountered: