SOI task fails to complete in Automation.
In the console you will see this error message:
Exception has occurred in function ExecuteCommand.cpp() at Line No 1995. Type of exception is GeneralError. Error is Default Message Exception in ExecuteClassException. Error Description is Unable to create new process. Value of Windows error code = 6 and message is The handle is invalid.
In your DSTasks.log you will find that setup.exe is schedule to run (ExecuteClass::Module Name = Z:\sources\setup.exe) but then fails to, generating this error message:
File:ExecuteCommand.cpp,Line:4370 ERROR: Exception has occured in function ExecuteCommand.cpp() at Line No 1995. Type of exception is GeneralError. Error is Default Message: Exception in ExecuteClassException. Error Description is "Unable to create new process". Value of Windows error code = 6 and message is " The handle is invalid."
This occurs because the setup.exe file is not present or is a zero K file.
A bug native to Deployment Solution 8.x is causing the file importation process to create faulty GUID folder structures when copying SOI files to C:\Program Files\Altiris\Notification Server\NSCap\bin\Deployment\Packages\SOI. There are currently two known permutations of this issue.
The importation process may create two separate GUID folders in the above location, one of which contains the Source > OEM subfolders, while the other contains the rest of the Windows files.
Alternatively, the bug may cause the creation of a single GUID folder, but with the Windows files placed directly in the GUID folder instead of inside the Sources subfolder, where they belong.
Both faulty file structures prevent the SOI from recognizing or calling upon the correct resources to complete the installation process.
Deployment Solution 8.x
Solution: Issue will be addressed in 8.5 RU1 due first quarter 2019
Resolving this requires modifying the faulty GUID file structure created by the buggy importation process in C:\Program Files\Altiris\Notification Server\NSCap\bin\Deployment\Packages\SOI.
If your import created two separate folders for your SOI files:
If your import created a single GUID folder but incorrectly order the contents:
Regardless of which faulty file system you encounter, this is how it should look when you're done with the above steps: