Start-ADTMsiProcess failing

The Toolkit Toolkit Features
1

Hey all,

I’m starting to kick the tires of v4.0.6 and I’m hitting a wall when trying to install an MSI in the toolkit; looking for a sanity check as I feel like I must be missing something simple.

I’m trying to install a simple .msi using the following:

Start-ADTMsiProcess -Action "Install" -FilePath "$($adtSession.DirFiles)\installer.msi" -ArgumentList "/qn"

It ends up failing with an exit code of 60001. I’ve triple checked my syntax with the documentation and everything looks fine. I also removed the "$($adtSession.DirFiles)" part to make sure that wasn’t causing an issue to no avail. Its being run like I would be running it in v3 in a testing circumstance - running the Invoke-AppDeployToolkit.exe elevated to verify functionality.

In the log, I’m seeing this block:

>Message               : Execution failed with exit code [1603].
 
FullyQualifiedErrorId : ProcessExitCodeError,Start-ADTMsiProcess
ScriptStackTrace      : at Start-ADTProcess<Process>, C:\Users\userAccount\Desktop\AppName\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 20256
at Start-ADTMsiProcess<Process>, C:\Users\userAccount\Desktop\AppName\PSAppDeployToolkit\PSAppDeployToolkit.psm1: line 19546
at Install-ADTDeployment, C:\Users\userAccount\Desktop\AppName\Invoke-AppDeployToolkit.ps1: line 155
at <ScriptBlock>, C:\Users\userAccount\Desktop\AppName\Invoke-AppDeployToolkit.ps1: line 313

Has anyone seen similar or have an idea on what I’m missing?

Thanks!

2

Why don`t you use only this:
Start-ADTMsiProcess -Action ‘Install’ -FilePath ‘installer.msi’ -ArgumentList “/qn”
because it should run by default what is under DirFiles

3

I’ve tried it both ways with the same result, unfortunately.
Part of the reason was to see if I got different results, the other reason is as a way to illustrate where the files were running from for the juniors on my team, if that makes sense :slight_smile:

4

Might be dumb question but does your MSI actually installs fine when you try to run it on clean device on it own because error code is related to MSI installer. Try maybe with .log file to see where it fails.

1 Like
5

Good thought, I’ll verify that. I’m pretty sure I tested that, but its been an off and on test over the past few months.
Thanks for your help!

1 Like