Single Workstation Issue - Can't run a Baseline Evaluation due to Parsing Error

Kevin W. Gagel 6 Reputation points
2023-11-17T23:05:20.6366667+00:00

I have a single computer that cannot run a baseline on account of a 'Parsing Error'. As a result, the scripts in the baseline never get executed on the computer.

I have run the scripts on the computer manually and from an elevated cmd prompt using the 'nt authority\system' account as described here How to Access the Local System Account - Recast Software

All of the other computers in the device collection that this baseline is deployed to are running the baseline and scripts. The scripts run - they're not the problem.

In the MECM console, under monitoring for the deployment:CDN media

I have uninstalled the ccmclient, cleaned the disk and registry as well as deleted the computer from the CCM database. After it reappeared, installed the agent again. Once it was clear the agent was communicating correctly with the SCCM server I assigned it to the device collection which has the policy applied.

The Baseline policy appeared in Configuration Manager Properties under Configurations. I then clicked the baseline and selected the Evaluate button and waited.

Once again, the compliance column shows 'Error' and Deployment Status for the baseline shows the above error.

I've tried deleting the Configuration Items and building new, the Baseline and building new, the deployment and re-deploying.

In the CIAgent.log I can see that it has trouble finding the location the computer should in, then finds the computer is Intranet connected and then assigns the correct location.

In the CIDownloader.log the following errors are present.

CI Downloader starting up...
CCIDigestStore::Initialize succeeded.
CCIDownloader::InitializeJobState deserilalized 7 jobs.
CCIDownloader::DeleteAgedOutJobs deleted 0 old jobs.
CI Downloader job state is WaitOnCompletion, no restart required.
CI Downloader job state is WaitOnCompletion, no restart required.
CI Downloader job state is WaitOnCompletion, no restart required.
CI Downloader job state is WaitOnCompletion, no restart required.
CI Downloader job state is WaitOnCompletion, no restart required.
CI Downloader job state is WaitOnCompletion, no restart required.
CI Downloader job state is WaitOnCompletion, no restart required.
CCIDownloader::Initialize succeeded.
CI Downloader successfully started up.
CCIDigestStore::InitializeLanternInitializeLantern failed (0x80040154).
InitializeLantern failed (0x80040154).
CCIDigestStore::CancelAndStartIdleTimer Canceling existing idle time-out task
CCIDigestStore::InitializeLanternInitializeLantern failed (0x80040154).
InitializeLantern failed (0x80040154).
CLanterIdleTimerHelper::Execute Shutting down lantern
CCIDigestStore::InvalidateWbemServicesCache
CCIDigestStore::InvalidateWbemServicesCache Invalidated LPP references
CCIDigestStore::InvalidateWbemServicesCache Invalidated LPA references
CCIDigestStore::InvalidateWbemServicesCache Invalidated all references

In the CIStore.log I see these errors present.

CCIStoreTargetedCIDownloader::Download - Starting CI Agent Job {F731728D-AEC8-4E27-9F54-ABD283C09FA9} for download.
CCIStoreTargetedCIDownloader::NotifyComplete - CI Agent Job {F731728D-AEC8-4E27-9F54-ABD283C09FA9} failed due to error (0x87d00207).
CI Store starting up...
GetInstanceFromLantern failed (0x80040154).
PutInstanceToLantern failed (0x80040154).
CCIStore::CreatePolicyPriorityStrategies failed with error 0x80040154

Any ideas on how to track down what the problem is that is affecting only this one computer?

Microsoft Configuration Manager
{count} votes

1 answer

Sort by: Most helpful
  1. AllenLiu-MSFT 43,061 Reputation points Microsoft Vendor
    2023-11-20T07:45:31.9833333+00:00

    Hi,

    Thank you for posting in Microsoft Q&A forum.

    You may try the following steps:

    1. Check the logs on the affected computer for any additional errors or warnings that may provide more information about the parsing error.
    2. Verify that the affected computer has the necessary permissions to access and download the Configuration Items and Baseline.
    3. Check the logs on the Configuration Manager server for any errors or warnings related to the affected computer or the Baseline deployment.
    4. Consider opening a support case with Microsoft to get further assistance with troubleshooting this issue.

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".