SOLVED Task Sequence error 0x80004005 after upgrade to 2403

[themightymrp]

Having only recently taken over our MECM system, I've updated our setup to the latest build with the September hotfix. However I now get the dreaded 0x80004005 error when trying to run a Task Sequence.

The smsts.log file makes reference to "content location request failed for xxxxxxx" and "Failed to resolve PackageID=xxxxxxx" where both ID's here refer back to the Configuration Manager Client Package. It then says "Failed to resolve selected Task Sequence dependencies Code 0x80004005". I know this is a permission error normally but how to fix?

I've tried redistributing to content of that file, and the update package, which says successful. But I still have the same problem. I'm not knowledgeable yet on MECM to know where next to check? Any advice?

 

[Prajwal Desai]

Having only recently taken over our MECM system, I've updated our setup to the latest build with the September hotfix. However I now get the dreaded 0x80004005 error when trying to run a Task Sequence.

The smsts.log file makes reference to "content location request failed for xxxxxxx" and "Failed to resolve PackageID=xxxxxxx" where both ID's here refer back to the Configuration Manager Client Package. It then says "Failed to resolve selected Task Sequence dependencies Code 0x80004005". I know this is a permission error normally but how to fix?

I've tried redistributing to content of that file, and the update package, which says successful. But I still have the same problem. I'm not knowledgeable yet on MECM to know where next to check? Any advice?

The 0x80004005 error is a generic error and could indicate that the package is corrupt. Remove it from the DP and distribute it back. Search this forum for other solutions too.

 

[themightymrp]

The 0x80004005 error is a generic error and could indicate that the package is corrupt. Remove it from the DP and distribute it back. Search this forum for other solutions too.

I don't seem to be able to remove the package for Configuration manager Client? The option to remove is greyed out, I only have validate and redistribute. Both of which I've tried

 

[Prajwal Desai]

The client package cannot be removed from the DP. It can be validated or redistributed. When you redistribute the client package, do you see any errors in the distmgr.log?. The client agent package is updated automatically when you update the latest hotfix (provided the hotfix contains the updates for the client agent).

 

[themightymrp]

The client package cannot be removed from the DP. It can be validated or redistributed. When you redistribute the client package, do you see any errors in the distmgr.log?. The client agent package is updated automatically when you update the latest hotfix (provided the hotfix contains the updates for the client agent).

Still having this problem. With the assistantce of a former member of staff (who set it up originally) we have performed a site reset, updated the ADK and checked through everything we can think of. I go through the Task Sequence selection screen, provide a name for the PC and click go and it immediately fails with error 0x80004005. Attached is the error part of the smsts.log file from the client. Any thoughts on next steps? One thing that is now working again is CCM clients are updating the version of the client they are using - I hadn't noticed that this had also stopped.

 

[themightymrp]

I've sorted it! Finally discovered that the SQL Identity certificate had expired. Generated a new one and everything kicked into life.

Is there an easy way to monitor the certificate status within the MECM console so that I could have found this quicker?