Execution of Group (Install Applications) Fails - Failed to run the action Install Application (80004005)

Question

_{Wednesday, December 14, 2016 12:50 PM}

Hi All,

After discovering the problem with initiating the task sequence, I've run into a secondary problem.

My task sequence is successful up until the fourth app is installed via my Install Applications group. We currently have two sites, our main office and our secondary satellite group. Our main office houses the primary SCCM management/distribution server, while the secondary site holds a pull distribution point to alleviate link load. The task sequence has been tested at our main offices, but has given me no amount of grief at the satellite location.

I have verified the files at the pull DP, and have re-distributed as well to no avail. The problem occurs only around the fourth app install, eventually terminating the sequence with the generic error:

Failed to run the action: Install Endpoint Security. Unspecified error (Error:800040005; Source: Windows

All previous applications install as intended, but I have yet to try continuing the sequence even if an install fails. The task sequence has been tested at both sites on the same machine. I've checked through smsts.log and this was the only real information that stuck out, as previous apps share the same general procedure in the logs.

If there's a general step procedure I should follow to troubleshoot this that would be useful.

Thanks,

Dusty.

All replies (5)

_{Wednesday, December 21, 2016 9:08 AM ✅Answered}

Hi all,

We collectively decided to simply disable the step of the task sequence and push out the security client with group policies. This was primarily down to the fact that any future computers that were placed on the domain that weren't built with the task sequence would lack the client, so it would just be easier and in best interests to ensure all devices were pushed the client.

Thanks for your help.

Dusty.

_{Wednesday, December 14, 2016 1:04 PM}

Does AppEnforce.log tell that the installation was attempted at all?

Torsten Meringer | http://www.mssccmfaq.de

_{Wednesday, December 14, 2016 2:16 PM}

I don't have appenforce.log available to me currently as I'm not on site, though I find most logs are unavailable unless pulled directly during the task sequence via the console.

I do however show from the smsts.log that I pulled during the task sequence that the application install was attempted with "Install application "Endpoint Security", followed by the usual log entries.

Start executing an instruction. Instruction name: Install Endpoint Security. Instruction Pointer:20
Installing application 'Endpoint Security'

It's only later that the issue arises, in the form of the "failed to run action" with error 80004005.

_{Wednesday, December 14, 2016 2:29 PM}

0x80004005 is a generic error message thus posting that single log line doesn't help. When posting from a log file, you need to post entire relevant snippets that show what happened before and after the error as well as the error itself.

Also, app enforce.log (as Torsten noted) is also needed. These are client side logs. app enforce.log is located in the \Windows\ccm\logs folder.

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Wednesday, December 14, 2016 2:37 PM}

OK, thanks. I'll update tomorrow when I'm on site.