Tuesday, April 21, 2020

Error in ClientIDManagerStartup log: RegTask: Failed to get certificate. Error: 0x80004005

The SCCM Client is not working and shows like this:





The above error is logged in ClientidmanagerStartup log.

Solution:

There is a folder: C:\ProgrammData\Microsoft\Crypto\RSA   (on Windows10).
On the MachineKeys folder, check the Security permissions and fix it if required.
Then restart the ccmexec service.

Friday, September 13, 2019

Error while editing SCCM OS task sequence

Sometime back, we were facing this error while editing OS install task sequence.
"There is not enough memory available to perform the task sequence operation."

Strange, as total available memory was enough.

So, went though this link-
https://techcommunity.microsoft.com/t5/Enterprise-Mobility-Security/Task-Sequence-Editor-8220-too-many-steps-8221-Issue-and-Solution/ba-p/247122

And made these changes:

-changed memoryperhost to 629145600(600mb) from 536870912
-changed handlesperhost to 8192 from 4096


Also, did a general cleanup of SUGs for Expired/Superseded updates.Changed collection refresh schedules to less frequent one.

This fixed it for us.
 

Monday, July 1, 2019

Error 0x8024002D-A full file update could not be installed because it required the source

I was facing this error during deployment of Third Party updates through SCCM. Wanted to update Acrobat DC.

On checking the logs, it seemed the Acrobat required the original .msi for update to work. The updates are as you know .msp.
And the .msi got deleted from ccmcache.

The solution is you repair Acrobat DC, from a folder, where the .msi is present-C - :\Program Files (x86)\Adobe\Acrobat DC\Setup Files

So, run this command to repair Acrobat, open cmd and set the source to - C:\Program Files (x86)\Adobe\Acrobat DC\Setup Files. Run the below command.Then, the update works.

Command=msiexec /fomusv "C:\Program Files (x86)\Adobe\Acrobat DC\Setup Files\{AC76BA86-1033-FFFF-7760-0C0F074E4100}\AcroPro.msi"

Wednesday, December 12, 2018

0x80073712 The component store has been corrupted, During patches installation

Sometimes, during monthly patches installation, you get this error-0x80073712 The component store has been corrupted.

This can be seen in updatesdeployment.log, when content download has finished and installation is ongoing.

 Progress: Status = ciStateError, PercentComplete = 0, DownloadSize = 0, Result = 0x80073712

Solution:
Try this command: Dism.exe /Online /Cleanup-Image /Restorehealth

This  will restore the system files from the installation source at c:\winsxs

If you are lucky, it fixes it!
Note: It takes time to complete....