question

WimGoeminne-6637 avatar image
0 Votes"
WimGoeminne-6637 asked Amandayou-MSFT commented

Updates Compliance state unknown

We have a number of servers in our environment which are showing "compliance state unknown" in SCCM reporting.
When checking the report "Computers failing with a specific scan error", they all have the same error:

11426 -2145123271 The data received does not meet the data contract expectations.

All servers (except two fileservers) have the RD session host role installed, no clue if it related to some policies we have applied on that type of machine.
Number of servers reporting this error is 14 out of +2000.
All servers are in the same domain as the site server. Environment is SCCM CB 2006, single primary site.

Anyone have a clue about the meaning of this error?

Thanks,
WiM






windows-server-update-servicesmem-cm-updates
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Amandayou-MSFT avatar image
0 Votes"
Amandayou-MSFT answered

Hi @WimGoeminne-6637,

Please check if there is error between MP and client by CcmMessaging.log, which records activities related to communication between the client and management points, and check if any error in ScanAgent.log.



If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

WimGoeminne-6637 avatar image
0 Votes"
WimGoeminne-6637 answered Amandayou-MSFT commented

@Amandayou-MSFT,

Thanks for your reply. I don't see any errors in the logfiles. Agent is able to communicate with MP, as inventories are working fine.

  • -Evaluating Update Status... ScanAgent 21/09/2021 14:48:18 11492 (0x2CE4)

  • Calling back to client on Scan request complete... ScanAgent 21/09/2021 14:48:18 11492 (0x2CE4)
    Policy Change notification received for ToolUniqueID={70143F13-E570-482E-9EC7-80F50C525966} ScanAgent 22/09/2021 1:35:09 31592 (0x7B68)
    Message received: '<?xml version='1.0' ?> <UpdateSourceMessage MessageType='ScanByUpdateSource'>
    <ForceScan>TRUE</ForceScan>
    <UpdateSourceIDs>
    <ID>{70143F13-E570-482E-9EC7-80F50C525966} </ID>
    </UpdateSourceIDs>
    </UpdateSourceMessage>'
    ScanAgent 22/09/2021 4:02:00 46152 (0xB448)
    ScanByUpdateSource request received with ForceReScan=2, ScanOptions=0x0000000a, WSUSLocationTimeout = 604800 ScanAgent 22/09/2021 4:02:00 46152 (0xB448)
    Sources are not current ScanAgent 22/09/2021 4:02:00 46152 (0xB448)
    *WSUSLocationUpdate received for location request guid={5091B341-D581-4273-9E17-D4ACFA3B0519} ScanAgent 22/09/2021 4:02:00 50512 (0xC550)
    ScanJob({3CB8DFF0-D0CC-4342-9323-BAB975A7B948}): - - - - - -Locations requested for ScanJobID={3CB8DFF0-D0CC-4342-9323-BAB975A7B948} (LocationRequestID={5091B341-D581-4273-9E17-D4ACFA3B0519}), will process the scan request once locations are available. ScanAgent 22/09/2021 4:02:00 46152 (0xB448)
    CScanJobMgr::UpdateSUPLocationList- Original WUA location count is 0, new location count is 1, WUA locations updated. ScanAgent 22/09/2021 4:02:00 50512 (0xC550)
    Sources are not current ScanAgent 22/09/2021 4:02:00 46152 (0xB448)
    ScanJob({3CB8DFF0-D0CC-4342-9323-BAB975A7B948}): Scan Succeeded, Resetting Source to Current and TTLs to Valid ScanAgent 22/09/2021 4:02:11 23988 (0x5DB4)
    ScanJob({3CB8DFF0-D0CC-4342-9323-BAB975A7B948}): CScanJob::OnScanComplete - Scan completed successfully, ScanType=1 ScanAgent 22/09/2021 4:02:11 23988 (0x5DB4)
    ScanJob({3CB8DFF0-D0CC-4342-9323-BAB975A7B948}): CScanJobManager::OnScanComplete -ScanJob is completed. ScanAgent 22/09/2021 4:02:11 23988 (0x5DB4)
    ScanJob({3CB8DFF0-D0CC-4342-9323-BAB975A7B948}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients... ScanAgent 22/09/2021 4:02:11 23988 (0x5DB4)

  • Calling back to client on Scan request complete... ScanAgent 22/09/2021 4:02:11 46152 (0xB448)
    CScanAgent::ScanComplete- Scan completion received. ScanAgent 22/09/2021 4:02:11 46152 (0xB448)
    Policy Change notification received for ToolUniqueID={70143F13-E570-482E-9EC7-80F50C525966} ScanAgent 22/09/2021 5:53:10 45880 (0xB338)
    Policy Change notification received for ToolUniqueID={70143F13-E570-482E-9EC7-80F50C525966} ScanAgent 22/09/2021 15:30:10 49052 (0xBF9C)
    *Policy Change notification received for ToolUniqueID={70143F13-E570-482E-9EC7-80F50C525966} ScanAgent 22/09/2021 16:55:09 22480 (0x57D0)

  • · 1
    5 |1600 characters needed characters left characters exceeded

    Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

    Hi,

    We now know how a state message is recorded and the WMI location where these state messages are stored. This schedule can be modified in the State Messaging of the custom or default client settings. We could check StateMessage.log to see if any error in it.

    Here is the article we could refer to:
    https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/track-software-update-compliance-assessment#state-message-processing-flow

    If it is normal in the log, please try to re-install one of the issued client to check if the compliance state unknown could be changed.

    Best regards,
    Amanda

    0 Votes 0 ·