Single computer's client cannot update. Has 'parsing error' 0x87d00207

[KevinWGagel]

I'm having trouble tracking down a problem with a client machine. It is one of a couple dozen machines in a device collection that a configuration baseline I've created, is deployed to. All of the other machines in the device collection are applying the settings without error and as expected. 

I've tried running the ccmrepair utility, deleting the cache and its persistent files. I can't seem to find any information on what exactly this 'parsing' error is all about. This is all I can find on it 0x87d00207. 

Direction for me to follow to get to the bottom of this would be appreciated. 

The client agent's error in Configuration Manager Properties

The CIAgent log file has these entries

CCIInfo::SetError - Setting CI level error to (0x87d00207).

CIAgentJob({3DFC13C0-C3BB-45A6-81B4-F18150443CE3}): HandleEvent failed (0x87d00207).

CIAgentJob({3DFC13C0-C3BB-45A6-81B4-F18150443CE3}): PersistCIModels failed (0x87d00207).

CCIDownloaderResult::PersistDownloadedCIModels failed (0x87d00207).

CIAgentJob({1072A64A-2B5F-451A-91D5-1F3D0E9AA2A3}): Setting failed CI ScopeId_252955F2-1434-473F-A2F5-FC4B4E2CA0B0/RequiredApplication_07d6b7a9-dad4-405b-8c27-79e97aca111c:26 to error state due to model compilation failure 0x87d00207

CCIInfo::SetError - Setting CI level error to (0x87d00207).

[#2]

@KevinWGagel  is the baseline a PowerShell script? Did you validate each item in the baseline manually? Exactly what troubleshooting have you done so far?

[#3]

The baseline is a script. The script was developed on the machine throwing the parsing error and the script runs perfectly on the same and all the other machines.
Each item in the baseline was validated and they work on all the other machines.
The parsing error seems to be pointing to something wrong with a CCM component which is why I've run the ccmrepair utility, cleared out the cache including persistent items and restarted the ccmservice.

[#4]

Do you test the script using the local system account? https://www.recastsoftware.com/resources/how-to-access-the-local-system-account/
It us unclear if running the ccmrepair solves your issue.

[#5]

ccmrepair did not resolve the issue. The scripts run on all of the computers in the device collection. The problem is that the evaluation can't happen because of the parsing error.

[#6]

Did you test the script using the local system on any failed systems?

[#7]

Yes and as stated the script runs without issue.

[#8]

This is really important for the next stage of troubleshooting. When you say you ran the script as local system, you ran it interactively as local system account and not your account or local administrator account.

If you ran it interactively using the local system account and all is good but it still failing via ConfigMgr. You need to add logging at each stage to see what exactly is failing. e.g. create a text file with results of each step/ section.

[#9]

Garth,
I followed the instructions in https://www.recastsoftware.com/resources/how-to-access-the-local-system-account/ to run it as the local system. The script runs fine. The problem is not the script. The problem is happening before the script is even tried.

[#10]

I found http://appsdep.blogspot.com/2018/11/repairing-sccm-client-wmi-issues.html which indicated examing the DcmWmiProvider.log. Sure enough my computer's (the one with the problem) has the sea of red. Which indicates that the WMI has become corrupted.

I've followed the steps in the article and am waiting for everything to settle down as it can take a few hours.

[#11]

Well, that didn't fix the issue. It seemed to fix the WMI stuff but not the component that has the parsing issue.

[#12 · Accepted solution]

UWF_Filter appears to have been key to restoring the ccmclient. I uninstalled the agent again and when I tried to install it it wouldn't. One of the errors in the ccmsetup log was "Failed to get UWF_Filter instance. HRESULT = 0x80041013]LOG"
This is for "Unified Write Filter", only after turning 'on' this feature and rebooting would the agent install again.
Furthermore, the agent now evaluates the baseline without any errors.