So here is an interesting little bug. I am deploying round about 3000 Adobe Acrobat installs and i have like 160 deployment fails.
The clients will keep failing to launch the install skript with the error above as long as it runs from Config Manager. (i cant even run PS-session from sccm client center that runs in my admin context …)
If i lets say open a fresh PS session towards the client as my admin user the script works just fine …
Anyone stumbled upon this one?
App enforcement environment:
Command line: "Deploy-Application.exe" "Deploy-Application - Adobe Acrobat DC.ps1" INSTALL
Allow user interaction: No
UI mode: 1
User token: null
Session Id: 4294967295
Content path: C:\WINDOWS\ccmcache\n1
Working directory: AppEnforce 22.06.2023 16:04:33 688 (0x02B0)
Prepared working directory: C:\WINDOWS\ccmcache\n1 AppEnforce 22.06.2023 16:04:33 688 (0x02B0)
Prepared command line: "C:\WINDOWS\ccmcache\n1\Deploy-Application.exe" "Deploy-Application - Adobe Acrobat DC.ps1" INSTALL AppEnforce 22.06.2023 16:04:33 688 (0x02B0)
Executing Command line: "C:\WINDOWS\ccmcache\n1\Deploy-Application.exe" "Deploy-Application - Adobe Acrobat DC.ps1" INSTALL with system context AppEnforce 22.06.2023 16:04:33 688 (0x02B0)
Working directory C:\WINDOWS\ccmcache\n1 AppEnforce 22.06.2023 16:04:33 688 (0x02B0)
Post install behavior is NoAction AppEnforce 22.06.2023 16:04:33 688 (0x02B0)
Waiting for process 4744 to finish. Timeout = 30 minutes. AppEnforce 22.06.2023 16:04:33 688 (0x02B0)
Process 4744 terminated with exitcode: 4294901760 AppEnforce 22.06.2023 16:04:34 688 (0x02B0)
Looking for exit code -65536 in exit codes table... AppEnforce 22.06.2023 16:04:34 688 (0x02B0)
Unmatched exit code (4294901760) is considered an execution failure. AppEnforce 22.06.2023 16:04:34 688 (0x02B0)
This is not a PSADT error code.
according to this: Powershell terminating with exit code 4294901760 - Stack Overflow
you might have old Windows 10 1809 machines.
Google doesn’t pan out, try DDG: Error 4294901760 at DuckDuckGo
I agree its not a PSADT error in itself. But none the less it’s a relevant issue as it is directly tied to application deployments using PSADT (PowerShell)
Not a case of outdated Winver 10.0.19045.3086 sadly
Found som PS events as well
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<Provider Name="PowerShell" />
<TimeCreated SystemTime="2023-06-23T15:43:48.424844800Z" />
<Execution ProcessID="0" ThreadID="0" />
<Data>Nøyaktig baneinformasjon er nødvendig.</Data>
<Data>ExceptionClass=ArgumentException ErrorCategory= ErrorId= ErrorMessage=Nøyaktig baneinformasjon er nødvendig. Severity=Error SequenceNumber= HostName=ConsoleHost HostVersion=5.1.19041.3031 HostId=0b408e79-7b6f-4244-9b68-2597896df4cd HostApplication= EngineVersion=5.1.19041.3031 RunspaceId=1869358e-37aa-42d9-a955-6247b7a3b37d PipelineId= CommandName= CommandType= ScriptName= CommandPath= CommandLine= AdditionalInfo: Name=;Value= Name=;Value= Name=;Value=</Data>
What does the PSADT log file say on those failed installs?
BTW: no PSADT log file = Not a PSADT issue.
I am not arguing wheter it is a toolkit issue. (its not) If you are here to start something then just keep scrolling.
Your install command is wrong. it should be:
Deploy-Application.exe -DeploymentType 'Install'
Are you using a custom Deploy-Application.ps1? What is the content of the Deploy-Application.ps1 script? Maybe the path is not defined correctly on those systems and it can’t build the full path from the relative script name.
You need to give more details.
Not everyone knows Norwegian. But if we translate the message it says “Exact path information is required.” So most likely powershell or the Deploy-Application.exe can’t find the full path of the script.
His Deploy-Application.ps1 has a different name for each script.
Meanwhile I know the Deploy-Application.exe is a bit flaky / nitpicky with launching scripts not called Deploy-Application.ps1
Maybe if the PowerShell script didn’t have spaces, DanOne could drop the double quotes and Deploy-Application.exewould let it work.
Sadly the naming back to Depploy-Application.ps1 had no effect.
The troubleshooting continues