Prepare for Image Capture or a Deploy Image tasks are failing after booting to automation because files needed to create the package are missing.

The following message is displayed:

ErrorMessage: Exception has occured in function SMPPackage.cpp() at Line No 105. Type of exception is GeneralError. Error is Package Server is not found for package with Guid 213bf299-efed-492c-9675-1713b0934343. It may be that package is just created and not ready yet or package have not synced on nearest packages server. Please try after sometime.. Error Description is utilCSMPPackageInitialiaze. Value of Windows error code = 6 and message is The handle is invalid.

ErrorMessage: Exception has  occured  in function SMPPackage.cpp() at Line No 105. Type of exception is GeneralError.  Error is Package Server is not found for package  with  Guid  213bf299- efed -492c-9675-1713b0934343. It may be that package is just created and not ready yet or package have not synced on nearest packages server. Please try after sometime ..  Error Description is utilCSMPPackageInitialiaze. Value of Windows error code = 6 and message is The handle is invalid.

Unknown. The SWDPackageCodeBase table didn't have a record of this image package, so no codebases where returned for this package.

In this particular instance, the issue was related to stuck NSEs in the Agent Queue on the Site Server. Check the following:

1. Check that the image package is set to "Ready" under the Package Server tab on the Site Server.
2. If it is set to "Ready", check if the Agent Queue folder (under ...\Program Files\Altiris\Altiris Agent\Queue\<your SMP server name\Qeueu)
3. If you have files in there, restart the Symantec Management Agent service.

With this steps, you should be able to get the right image package status sent to the SMP so the proper codebase can be generated.