1
Installation end prematurely
Problem reported by Jhon Joffre - 12/6/2024 at 10:15 PM
Submitted
Hello, 

I have tried to install in our server the SmarterMail, but it has ended prematurely, I have noted in the logs an error message at MSI95B4.txt log 

I have check the commands Install-WindowsFeature and it does not run on powershell 32 bits but is fully functional on the 64x what I can do for it?

log copy:

MSI (c) (30!8C) [22:47:24:025]: PROPERTY CHANGE: Modifying CustomActionData property. Its current value is 'DoAction:AI_DATA_SETTER_18:AI_BOOTSTRAPPER|DoAction:PowerShellScriptInline:AI_BOOTSTRAPPER'. Its new value: 'ParamsScript#Requires -version 3
Param()

Install-WindowsFeature -name Web-Server -IncludeManagementToolsScriptPreambleparam(
  [alias("propFile")]      [Parameter(Mandatory=$true)] [string] $msiPropOutFilePath
 ,[alias("propSep")]       [Parameter(Mandatory=$true)] [string] $msiPropKVSeparator
 ,[alias("lineSep")]       [Parameter(Mandatory=$true)] [string] $msiPropLineSeparator
 ,[alias("scriptFile")]    [Parameter(Mandatory=$true)] [string] $userScriptFilePath
 ,[alias("scriptArgsFile")][Parameter(Mandatory=$false)][string] $userScriptArgsFilePath
 ,[Parameter(Mandatory=$true)]                          [string] $testPrefix
 ,[switch]                                                       $isTest
 )

Function AI_GetMsiProperty( [Parameter(Mandatory=$true)]  [string] $name
                          , [Parameter(Mandatory=$false)] $testValue = $null
 
Action ended 22:47:24: AI_DATA_SETTER_18. Return value 1.
MSI (c) (30!8C) [22:47:24:025]: Doing action: PowerShellScriptInline
Action start 22:47:24: PowerShellScriptInline.
MSI (c) (30:70) [22:47:24:258]: Invoking remote custom action. DLL: C:\Users\ADMINI~1\AppData\Local\Temp\MSIA53E.tmp, Entrypoint: RunPowerShellScript
[INFO] PowerShell script preferred invocation folder: 
Dumping PowerShell invoke log ...
--> Found PowerShell path: C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
--> PowerShell Script Execution Result Code: 574
--> PowerShell Script Execution log: 
ERROR: The term 'Install-WindowsFeature' 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.
MSI (c) (30!94) [22:47:28:022]: PROPERTY CHANGE: Adding POWERSHELL_EXECUTION_LOG property. Its value is 'ERROR: The term 'Install-WindowsFeature' 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.'.
CustomAction PowerShellScriptInline returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 22:47:28: PowerShellScriptInline. Return value 3.
CustomAction AI_Init_WelcomePrereqDlg returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 22:47:28: AI_Init_WelcomePrereqDlg. Return value 3.
MSI (c) (30:08) [22:47:28:031]: Doing action: FatalError

1 Reply

Reply to Thread
0
Kyle Kerst Replied
Employee Post
What version of Windows Server are you seeing this error on? I can try to replicate the issue and escalate to our development team.
Kyle Kerst IT Coordinator SmarterTools Inc. www.smartertools.com

Reply to Thread