u/InvisibleTextArea

▲ 14 r/SCCM

ConfigMgr 2509 + KB37864969 reporting 0x87D00314 for compliant application deployments

Hi all,

I'm running ConfigMgr Current Branch 2509 with Hotfix Rollup KB37864969 and am seeing what appears to be a site-wide application deployment reporting issue. Initially I thought this was a PatchMyPC or Client side deployment problem, but after digging into it for several hours the evidence points elsewhere.

The error being reported is:

0x87D00314 (-2016410860) CI Version Info timed out

I currently have:

ErrorCode      Records
------------   -------
-2016410860    13,784

This affects dozens of unrelated application deployments. For example:

AssignmentID   Records
------------   -------
16793680       409
16793921       409
16793667       407
16793620       406
16792258       406
16793616       406
...
16794003       361

The deployment I was investigating is a PatchMyPC Application, Microsoft Remote Help 5.2.1037.0. Client-side everything appears healthy with expected values in AppIntentEval.log, CCM_Application WMI and StateMessage.log.

The strange part is what I see when joining deployment asset details and deployment error details in SQL I get conflicting information.

MachineName      ComplianceState  EnforcementState  InstalledState  ErrorCode
--------------   ---------------  ----------------  --------------  ---------
LAPTOP01         1                1000              2               -2016410860
LAPTOP02         1                1000              2               -2016410860
LAPTOP03         1                1000              2               -2016410860
LAPTOP04         1                1000              2               -2016410860

Even stranger, the Application CI summary disagrees with the error view. For Remote Help I have 378 successful installs in the Application CI summary. However vAppDeploymentErrorAssetDetails contains 361 rows for the same deployment. The error records themselves don't contain much useful information. Most of the records are:

ExtendedInfoID = 0
ExtendedInfoDescriptionID = 0

New deployments show the same behaviour.

At this point it feels like SCCM is simultaneously recording success and failure for the same deployment instance. Any ideas appreciated.

reddit.com
u/InvisibleTextArea — 3 days ago