I have a Windows 7 Professional deployment task sequence that has been running without problems for a number of months now. Last week we tried to deploy some new laptops and the task sequence failed when running the install software action with error 0x80002004. There have not been any changes made to the SCCM environment.

I have tried disabling the install software tasks and this run through and competed as required (minus the applications) as expected.

We have "No Apps" build and a 64bit build using the same process (copy of the initial Task Sequence) that is still running without a problem, so I have copied these task sequences changed the OS image/added the Install Software tasks and the problem reappears.

I have searched around on various websites and see a number of people that have similar issues, but nothing that seems to point to s resolution for me. All the other functionality we use of SCCM is running as expected (Software and Update Deployment, AI and Software Metering) and we have not seen any site status errors.

Here are the contents of the SMSTS.LOG covering the task in question:

Policy evaluation initiated InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
Waiting for policy to be compiled in 'root\ccm\policy\machine' namespace InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
Query path = 'CCM_SoftwareDistribution.ADV_AdvertisementID="KWS2001F",PRG_ProgramID="Install - APP00034V04R001",PKG_PackageID="KWS00608"' InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
Verified policy is compiled in 'root\ccm\policy\machine' namespace InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
content location count = 1 InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
Invoking Execution Manager to install software InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
FALSE, HRESULT=80002004 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,282) InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
Failed to invoke Execution Manager to Install Software for PackageID='KWS00608' ProgramID='Install - APP00034V04R001' AdvertID='KWS2001F' hr=0x80002004 InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
InstallSoftware failed, hr=0x80002004 InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
0, HRESULT=80002004 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,746) InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
Entering ReleaseSource() for \\SERVER1\DSP$\PACKAGES\APP00034V04R001\ InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
reference count 1 for the source \\SERVER1l\DSP$\PACKAGES\APP00034V04R001\ before releasing InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
Released the resolved source \\SERVER1\DSP$\PACKAGES\APP00034V04R001\ InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
pInstall->Install(sPackageID, sProgramName), HRESULT=80002004 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\main.cpp,374) InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
Install Software failed, hr=0x80002004 InstallSoftware 11/04/2011 11:48:01 3904 (0x0F40)
Process completed with exit code 2147491844 TSManager 11/04/2011 11:48:01 1836 (0x072C)
!--------------------------------------------------------------------------------------------! TSManager 11/04/2011 11:48:01 1836 (0x072C)
Failed to run the action: Install Symantec EndPoint Protection (32 Bit) 11.0.
Unknown error (Error: 80002004; Source: Unknown) TSManager 11/04/2011 11:48:01 1836 (0x072C)
Sending status message . . . TSManager 11/04/2011 11:48:01 1836 (0x072C)
Send a task execution status message SMS_TSExecution_ActionFailError TSManager 11/04/2011 11:48:01 1836 (0x072C)

If anyone else has seen this problem and even better has managed to resolve it I would love to know what you did.

80002004 is a custom ConfigMgr error code that means "The software distribution policy was not found".

On the programs that are failing to install, do you have the check box enabled "Allow this program to be installed from the Install Software task sequence without being advertised" on the advanced tab of the program?

Thanks for the quick response, but unfortunately this is checked.

This kind of issues can be caused by several Have you installed the hotfix mentioned in the following article?

System Center Configuration Manager 2007 does not process all advertised task sequences
http://support.microsoft.com/kb/949225

Based on the error code, it seems that the issue is caused by software distribution policy.

Troubleshooting Software Distribution Using Custom Error Codes
http://technet.microsoft.com/en-us/library/bb735865.aspx

Additionally, I suggest you check if the clocks on the server and clients are correct.

Thank you for the information.

I understand the Hotfix you reference is included in SP1. I probably should have mentioned we are running 2007 SP2 R2 so I believe this should not be an issue.

We have checked the date/time settings on the servers and the clients in question and there is no problem there.

With regards to the software distribution policy, this is where we are confused as software distrubution to existing clients works perfectly, we can push the Task Sequences we have for Windows XP, Windows 7 x64 (and these install the same applications without a problem) to existing clients and we can also push the same Windows 7 x86 Task Sequence without the application installation step and this completes. This also works with boot media on bare metal builds.

Only pushing the one Windows 7 with application task sequence do we see the failure. If we advertise it to an existing client then that client never runs the advertised TS and if we boot from media on a bare metal machine we get the error above when the install application action starts.

We have recrested the Task Sequence and the Advertisement and also done this to a new collection.

Any other suggestions?

Russell,

I am currently experiencing the same type of issue with a client that I am assisting.  The client hasn't had any issues for the longest period of time, but as soon as I have started pushing new drivers out for the customer for some new hardware models, this issue has continued to plague me.

Hi.

We are experiencing the same issue as outlined above.  Our OSD W7 deployment works fine, however it is the build and capture task sequence which is causing problems.  If any package is specified in the "install software" step then we get an error for example:

The task sequence execution engine failed executing the action (Install "K-Lite Code Pack-K-Lite Codec Pack 6.4.0 -") in the group (Install Software) with the error code 2147491844
Action output: Pack 6.4.0 -",PKG_PackageID="COL00090"'
Verified policy is compiled in 'root\ccm\policy\machine' namespace
content location count = 1
Invoking Execution Manager to install software
FALSE, HRESULT=80002004 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,282)
0, HRESULT=80002004 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\installsoftware.cpp,746)
Entering ReleaseSource() for \\VMSCCM01.CORPOFLONDON.GOV.UK\SMSPKGE$\COL00090reference count 1 for the source \\VMSCCM01.CORPOFLONDON.GOV.UK\SMSPKGE$\COL00090\ before releasing
Released the resolved source \\VMSCCM01.CORPOFLONDON.GOV.UK\SMSPKGE$\COL00090pInstall->Install(sPackageID, sProgramName), HRESULT=80002004 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\main.cpp,374)
Failed to invoke Execution Manager to Install Software for PackageID='COL00090' ProgramID='K-Lite Codec Pack 6.4.0 -' AdvertID='COL203AF' hr=0x80002004
InstallSoftware failed, hr=0x80002004
Install Software failed, hr=0x80002004. The operating system reported error 2147500037: Unspecified error

Checked package to ensure program was ticked to enable deployment via TS.  Same program can be deployed without issue if part of W7 OSD task sequence and not build and capture!!

Any suggestions gladly welcomed as hitting a brick wall.....

it seems to have just vanished for the same task sequence.

I'm not sure what would happen for a new one. if it comes back again, i'll have to try that. It's not going to help much though unless i can copy the task sequence over and deploy it.

Sorry, didn't check the timestamp. :)

I know this is an old thread, but we experienced the same issue (0x80002004) a couple of days ago.

Single machines appeared to install OK (Build Task Sequence and post-build apps) but running multiple machines would fail to install various apps both during TS and post build.

Very odd behaviour.

We initially thought there was a corrupt or missing package (we had recently pushed out a new driver pack to support new hardware) but that was not the case.

I then looked though the server Event Log and found that the server was generating very large numbers (10,000's) of network errors in the System log.

This meant that a single device was able to muddle though the build with the built-in re-try downloads and get content, but any more than that (or other machines installing apps at the same time as the build) would cause failures.

I don't know the root cause yet as it is being investigated by the server\network teams but just wanted to make the point that it is not always SCCM to blame! (Shock-horror!)