You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for providing this in the Powershell gallery. I really appreciate it.
I was able to import into Azure Automation using Powershell gallery. But, when i try to use in Azure Run books(powershell) to install a particular version, i get the following error.
"The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The term 'msiexec' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again."
Any help is really appreciated.
Thanks
Sam
The text was updated successfully, but these errors were encountered:
The problem you're hitting is that the tool for installing an MSI, msiexec doesn't exist on the target machine.
Given PowerShell has a built-in unzip API it might be possible to move to that rather than using msiexec. If you wanted to send a PR for that I'd be appreciative. 😊
Hello,
First of all, thanks for providing this in the Powershell gallery. I really appreciate it.
I was able to import into Azure Automation using Powershell gallery. But, when i try to use in Azure Run books(powershell) to install a particular version, i get the following error.
"The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The term 'msiexec' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again."
Any help is really appreciated.
Thanks
Sam
The text was updated successfully, but these errors were encountered: