Forum Replies Created
BusterParticipantMarch 14, 2016 at 9:30 pmPost count: 19
BusterParticipantMarch 14, 2016 at 9:19 pmPost count: 19
BusterParticipantMay 28, 2015 at 12:08 amPost count: 19
Turns out even though they looked ok the registry entry was a REG_SZ entry instead of a REG_EXPAND_SZ somehow. I fixed that reboot and pushed the install again and it succeeded like normal.
Thanks for helping me look down the right path (no pun intended) Muhammad!
BusterParticipantMay 28, 2015 at 12:06 amPost count: 19
BusterParticipantMay 27, 2015 at 7:32 pmPost count: 19
For my appllication Avaya One-X 6.2.6.03 it was extracting the files to $envWinDir\System32\config\systemprofile\AppData\Local\Downloaded Installations\ as the system account. Then the installer was looking in $envWinDir\SysWOW64\config\systemprofile\AppData\Local\Downloaded Installations\ to run and since it was not there the installer would fail.
My work around was to grab the extracted files and in the script I copy them to the location that the installer is looking for them during the Pre-Installation section and then delete the files as part of the Post-Installation section.
BusterParticipantMay 27, 2015 at 7:10 pmPost count: 19
If you try to run using PsExec as the system account with just the installer does the process also fail? I had one application that extracted to one location then tried to install from a different path causing the failures.
With testing with PsExec you can atleast find out if that is the issue you are facing. The command is psexec.exe -s \\localhost “PathToYourExe”
BusterParticipantMay 27, 2015 at 6:57 pmPost count: 19
That is the path I started looking into also. The odd thing is I’m not seeing any obvious issues on the first machine.
<code>[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment] C:\ProgramData\Oracle\Java\javapath; %SystemRoot%\system32; %SystemRoot%; %SystemRoot%\System32\Wbem; %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\; C:\Program Files (x86)\Common Files\LaserFiche\System; C:\Program Files\SunGard\bin .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC</code>
BusterParticipantMay 27, 2015 at 4:16 pmPost count: 19
When using a variable in the parameters section you need to change the quote style like this -Parameters “/s /f1^”$dirFiles\desktop.iss^”” The ^ are actually the ` key left of the 1 key it formats it out on the post.
- This reply was modified 3 years, 1 month ago by Buster. Reason: Formatting
BusterParticipantMay 27, 2015 at 4:08 pmPost count: 19
This script started off using 3.6.3 once I ran into this issue I created it again using 3.6.4 to see if the issue followed. So right now I am using 3.6.4. I did as you suggested and it looks like it is an msiexec issue
I am trying to find one of the failing machines to see what I can figure out. Last night I remoted to one of the failed machines and when deploy-application.exe was ran locally it ran successfully.
[Installation] :: Function failed, setting exit code to .
Message : The term ‘msiexec.exe’ is not recognized as the name of a cmdl
et, function, script file, or operable program. Check the spel
ling of the name, or if a path was included, verify that the p
ath is correct and try again.
FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Commands.
+ [string]$FullyQualifiedPath = Get-Command <
<<< -Name $Path -CommandType ‘Application’ -TotalCount 1 -Sy
ntax -ErrorAction ‘Stop’
BusterParticipantMay 16, 2015 at 6:52 pmPost count: 19
You can save the file to eithere Files or SupportFiles. The variable for supportfiles is $dirSupportFiles The PSAppDeploymentToolkitAdminGuide.docx included is a great read about all of the available options. The AppDeployToolkitMain.ps1 in AppDeployToolkit contains all of the base variables.
BusterParticipantDecember 3, 2015 at 5:40 pmPost count: 19
Hopefully this displays right, basically wrapping $dirFiles\silent.ini with the tick mark before the double quotes.
Execute-process -Path “Setup.exe” -Parameters “-f