Closed Skydea777 closed 1 month ago
If you are believing it or not, after over eighty failed deployments, I found it, change the "PsExec.exe" into its 64Bit counterpart "PsExec64.exe". Thats it, that is the reason the whole thing stopped working and I am screaming in anguish.
Thank you all, wish you a great day.
Hi there,
After updating from version 2.2.8 to 2.3.0, I am encountering an issue with running a custom install script. The script never completes and just hangs indefinitely. Even when using “exit /b” or other commands within the script, it does not proceed to the next task in the task sequence, a restart with "shutdown -r -f -t 0" will also lead to a failed deployment.
I have logged the entire installation process with my script and checking manually each component installs successfully. However, the script does not advance to the next task. If I manually close the running “cmd.exe” using Task Manager, the whole deployment fails. The remaining tasks in the sequence rush by in the status bar, and then the Client restarts, presenting an empty error screen after finishing.
The error logs are not helpful as they do not show any "real" errors, only that the process where executed corretly, well and that is a fact. Exit Code: 3221225477 Return Code: 0xC0000005 The script installs multiple software components for the client using the following command:
%windir%\system32\cmd.exe /c %SCRIPTROOT%\Install\PSTools\PsExec.exe \\%COMPUTERNAME% /accepteula -u enter.yourdomain.here\ServiceUserWithAccessRights -p HereIsAMightyComplicatedPassword -i -h "%windir%\system32\cmd.exe" " /c call \\enter.yourdomain.here\storage$\PathToTheBatch\Deploy\deploy-konstruct-everything.bat"
I also tried a PowerShell variation:powershell.exe -ExecutionPolicy Bypass -NoProfile -command "& %SCRIPTROOT%\Install\PSTools\PsExec.exe \\%COMPUTERNAME% /accepteula -u enter.yourdomain.here\ServiceUserWithAccessRights -p HereIsAMightyComplicatedPassword -i -h "%windir%\system32\cmd.exe" " /c call \\enter.yourdomain.here\storage$\PathToTheBatch\Deploy\deploy-konstruct-everything.bat"
As an additional Note, there is a previous Task that also calls a .bat File, this one just fails with the Error Code 1 and gets logged:
I also renamed the batch .bat into ".cmd" interesstingly then there is no "cmd.exe" to kill. Just an Unresponsive "psexec.exe" and its Service that cannot be """killed""". PSTools are the latest Version 2.43.
I suspect it is the PSExec that is used here that is the problem, somehow something goes wrong in this context that has worked before the Update.
Environment:
Additional Information:
Steps to Reproduce: Starting a Deployment with a "Run Command Line" that calls a Batch Via PSExec (So the Access Rights are correct) Expected Behavior: After the sucessful Installation it should continue with the last steps. Actual Behavior: Just stops after the Script was started the Deployment does not continue Screenshots/Logs: Logs-After-Batch-Started.zip After-Restart-smsts.zip