Parsing Error - 0x87D00207 RRS feed

  • Question

  • My packager has asked a question which I'm not too sure on. When viewing the deployment status of app they are seeing a Parsing error for the evaluation - error code 0x87D00207. The application doesn't appear in Software Center for install. 

    Any pointers gratefully received. 

    Tuesday, August 22, 2017 9:52 AM

All replies

  • You have to examine client-side logs, e.g. CI*.log.

    Torsten Meringer |

    Tuesday, August 22, 2017 12:06 PM
  • You can treat it as a normal deployment issue to troubleshoot. Be sure your environment is running well for all site system role, management point, DP, etc.

    Check your client log, like locationServices.log to be sure client is able to locate MP, DP. Check PolicyAgent.log to be sure client can receive policies.

    When you say application, did you deploy it with Application mode? If so, then you can review AppIntenteval.log, Appdiscovery.log and also be sure related content has been successfully distributed to DP. 

    You can find many blogs for troubleshooting software distribution on the web and you can take a look.

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Wednesday, August 23, 2017 2:56 AM
  • Hi, if you have this error look in the CIStore for 87D00215 and 80041002.

    Also look if CIStateStore displays you some lines like : "CCIStateTransition::ExtractStateDetails - CI ModelName ScopeId_ ..../DeploymentType_....., version XY not found in store"

    In CIDownloader :

    "DCM::LanternUtils::CheckCIExists - Wmi Instance: PolicyPlatform_Policy.Name="ScopeId__DeploymentType__1_Discovery_PolicyDocument",Authority="System Center Configuration Manager",Revision=1 not found in namespace: root\microsoft\policyplatform\Documents\Local. CI not found."

    and "Compiler lPhaseError: 3, ObjectNum: 1, hRes: 80041013 FirstLine: 2 LastLine: 39" caught our attention, where the 80041013 means "Provider Load Failure", which is quite bad.

    Between last 2, in the CIDownloader we also had : 

    DCM::LanternUtils::DeleteAlreadyExistingModel - Failed to delete instance PolicyPlatform_Policy.Name="GLOBAL_Platform_Settings_Configuration_PolicyDocument",Authority="System Center Configuration Manager",Revision=5 (0x80041001).

    and DCM::LanternUtils::StoreModelDocument - Failed to submit document [#pragma namespace("\\\\.\\root\\microsoft\\PolicyPlatform\\Documents\\Local") + CCIDigestStore::PersistIntegratedCIDefinitions failed (0x87d00207).

    We did not find the cause of this happening but when we reset the policy with "Configuration Manager Support Center" and we reinitialized the policy download, no luck. Strange is that the "XY" Version for which CM looks is an older revision of the application.

    Our guess was that ConfigMgr tries to delete inapplicable/obsolete policies and when trying to get the new policies, he is hit by this 80041013 hence he cannot get his new policies.

    Guess what, when we uninstalled the CMclient with the "ccmclean.exe /q" and then reinstalled it with the client-push method, after the policy evaluations, the error was gone. All this hurdle for one "parsing error".


    P.S. the WMI repository on the clients is consistent

    • Proposed as answer by Vasile JICHIN Tuesday, April 2, 2019 2:28 PM
    Thursday, February 7, 2019 3:54 PM
  • Also a CM client-repair will solve this issue aswell. It is quite often when it appears in environments so hopefully it will be helpful for anyone who stumbles upon it.
    Friday, August 2, 2019 2:25 PM
  • In our case this error appears for Software deployments and Configuration Baseline evaluations. There were tons of errors in CI and Policy logs. Strangely client repair, uninstall+repair didnt help. 

    What resolves issue was uninstall and reinstall Microsoft PolicyPlatform msi from client install source folder. 

    Machine policy refresh and we are good again ...

    (the common for failing clients was fact that those were inplace upgraded Server OS'es) , sccm client itself repaired itself after OS upgrade, but seesm not fully ) 

    Tuesday, June 16, 2020 1:03 PM