- Scores: 0
- Joined: 6/13/2012
Issues with Task Sequences and Executing the same package
Wednesday, June 13, 2012 6:29 PM
I'm using 2 completely seperate task sequences that each reference the same package in their installation. Task Sequence A install sequence is Install App A, Install App B and Task Sequence B is Install App C, Install App B. Each App is a seperate package with it's own programs. Each task sequence runs fine on it's own but when they execute back to back the first always installs and the 2nd won't even start. SCCM gives me this error:
The program for advertisement "AGD20510" failed ("AGD00434" - "*"). A failure exit code of 16389 was returned. User context: NT AUTHORITY\SYSTEM Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of 16389 is considered a failure. Solution: For more information on the exit code, refer to the documentation for the program you are distributing.
When looking at the machine's smsts.log I get this error:
Attempting to get locations for this member program.
The location for this member program is C:\Windows\system32\CCM\Cache\AGD00430.1.System
Attempting to get cache location from C:\Windows\system32\CCM\Cache\AGD00430.1.System.
SMS Client cache path: C:\Windows\system32\CCM\Cache ncher
Client cache relative location for this member program is %_SMSTSClientCache%\AGD00430.1.System
Setting source for AGD00430 to %_SMSTSClientCache%\AGD00430.1.System
ulPrgLocationCount != 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\launcher\tslauncher.cpp,309)
There are no locations for this program
GetDownloadLocationForMemberProgram(pITSExecutionRequest, sPackageID, sProgramID), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\launcher\tslauncher.cpp,570)
Task Sequence Manager could not get active request info. code 80004005
GetExecutionRequestDetails(pIExecutionRequest), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\launcher\tslauncher.cpp,644)
Failed to get the details of the execution request. code 0x80004005
Task Sequence Launcher could not get active request info. code 80004005
GetActiveRequest(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\launcher\tslauncher.cpp,776)
Error initializing TS environment. Code 0x80004005
InitializeEnvironment(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\launcher\tslauncher.cpp,962)
Task sequence launcher advertisement failed!. Code 0x80004005
**Please cleanup TSM directory before you rerun the advert**
Finalizing logging from process 5560
Successfully finalized logs to SMS client log directory from C:\Windows\system32\CCM\Logs
I've eliminated this being a PC problem by trying it on 3 different computers. If I remove package C from the 2nd task sequence then the 2 TS can run back to back just fine. I've recreated the packages at least 3 times now and the task sequences work fine when deployed by themselves (so I don't think this is a package problem). The PC event viewer records nothing because technically nothing ever happened on the client computer
The only conclusion I can come too is that when the first TS runs it initializes a path for the shared package (Package C in my example) but when the 2nd TS runs it's not cleaned up properly (does that make sense?) so it failes trying to setup the TS to execute. Remember when the 2nd TS fails it's not just package C that doesn't run, the entire TS won't even initialize. Most installations will not run back to back so this doesn't seem like a problem until a computer is reloaded for a user. In this case multiple installations will start to fail and I don't want to be manually managing installations on re-images all the time.
I hope this isn't a confusing issue to explain. I've spent 3 days on it and I'm a loss right now.
Ok let's see if I can explain this clearly.