Credentials Microsoft Certified Trainer (MCT) 2026Microsoft Innovative Educator Expert 2025–2026Microsoft Elevate Educator Expert 2026–2027ISC2 Certified Information Systems Security Professional (CISSP)Microsoft 365 Certified: Enterprise Administrator Expert (MS-102)Microsoft Certified: Azure Solutions Architect Expert (AZ-305)PMI Project Management Professional (PMP) 28 certifications · see all Verify on Credly
Omer EltayebMicrosoft 365
LinkedIn
  1. Home
  2. Articles
  3. Configuration Manager
Configuration ManagerDeep dive

Component status messages in Configuration Manager: WSUS sync, MP and distribution IDs

What status messages 6701, 6702, 6704 to 6706, 5436 and 2302 mean, plus the WCM, wsyncmgr and DistMgr errors behind red components, with usual causes and first checks.

Omer Eltayeb 6 min read Checked against Microsoft Learn

A red component under Component Status tells you that something failed, not what. This quick reference decodes the status messages and log errors behind the components that turn red most often (software update sync, WSUS configuration, the management point and Distribution Manager), with the usual cause, the first check and what a healthy sequence looks like.

Codes in this quick reference

  • 6701 WSUS synchronization startedComponent status (SMS_WSUS_SYNC_MANAGER)
  • 6704 WSUS synchronization is in progress (WSUS server phase)Component status (SMS_WSUS_SYNC_MANAGER)
  • 6705 WSUS synchronization is in progress (site database phase)Component status (SMS_WSUS_SYNC_MANAGER)
  • 6706 WSUS synchronization is in progress (replica software update points)Component status (SMS_WSUS_SYNC_MANAGER)
  • 6702 WSUS synchronization finishedComponent status (SMS_WSUS_SYNC_MANAGER)
  • Sync failed: WSUS server not configured. Please refer to WCM.log for configuration error details.wsyncmgr.log
  • 0x80072EFE - The connection with the server was terminated abnormally (sync with Microsoft Update)Software update synchronization errors
  • System.Net.WebException: The request failed with HTTP status 401 or 403WCM.log

+ 10 more codes in the tables below.

Browse the Configuration Manager error library
How this guide is organized: How to read these messages → Software update sync → WSUS configuration → Management point → Content distribution → How to verify a fixFlow diagram of the article's sections in reading order: 1. How to read these messages. 2. Software update sync. 3. WSUS configuration. 4. Management point. 5. Content distribution. 6. How to verify a fix. Toolbox: 0x80004005, 0x80072EFE, mpcontrol.log, WCM.log, wsusutil.exe.1How to read these messages2Software update sync3WSUS configuration4Management point5Content distribution6How to verify a fixTOOLBOX0x800040050x80072EFEmpcontrol.logWCM.logwsusutil.exeHow this guide is organized: How to read these messages → Software update sync → WSUS configuration → Management point → Content distribution → How to verify a fixFlow diagram of the article's sections in reading order: 1. How to read these messages. 2. Software update sync. 3. WSUS configuration. 4. Management point. 5. Content distribution. 6. How to verify a fix. Toolbox: 0x80004005, 0x80072EFE, mpcontrol.log, WCM.log, wsusutil.exe.1How to read these messages2Software update sync3WSUS configuration4Management point5Content distribution6How to verify a fixTOOLBOX0x800040050x80072EFEmpcontrol.logWCM.logwsusutil.exe
At a glance: how this guide is organized · 6 sections · 5 key settings and tools

How to read these messages#

From a red component to its cause and back to greenStep 1: Open the component's messages. Monitoring › System Status › Component Status; right-click, Show Messages › All. Step 2: Read the full message text first. Many error messages end with possible causes and solutions written by the product team. Step 3: Find the STATMSG line in the component's log. It's logged when the message was raised, so the lines around it give the context. Step 4: Decode the ISTR values and decimals. ISTR0, ISTR1 fill the placeholders; decimals are often HRESULTs: 2147500037 is 0x80004005. Step 5: Fix the cause the message points to. Use the usual cause and first check in the table for that component. Step 6: Reset Counts, then check for new errors. Component Status counts errors over a period, so a fixed component can stay red for a while.1Open the component'smessagesMonitoring › System Status ›Component Status; right-click,Show Messages › All.2Read the full message textfirstMany error messages end withpossible causes and solutionswritten by the product team.3Find the STATMSG line in thecomponent's logIt's logged when the message wasraised, so the lines around it givethe context.4Decode the ISTR values anddecimalsISTR0, ISTR1 fill the placeholders;decimals are often HRESULTs:2147500037 is 0x80004005.5Fix the cause the messagepoints toUse the usual cause and first checkin the table for that component.6Reset Counts, then check fornew errorsComponent Status counts errorsover a period, so a fixed componentcan stay red for a while.From a red component to its cause and back to greenStep 1: Open the component's messages. Monitoring › System Status › Component Status; right-click, Show Messages › All. Step 2: Read the full message text first. Many error messages end with possible causes and solutions written by the product team. Step 3: Find the STATMSG line in the component's log. It's logged when the message was raised, so the lines around it give the context. Step 4: Decode the ISTR values and decimals. ISTR0, ISTR1 fill the placeholders; decimals are often HRESULTs: 2147500037 is 0x80004005. Step 5: Fix the cause the message points to. Use the usual cause and first check in the table for that component. Step 6: Reset Counts, then check for new errors. Component Status counts errors over a period, so a fixed component can stay red for a while.1Open the component's messagesMonitoring › System Status › Component Status;right-click, Show Messages › All.2Read the full message text firstMany error messages end with possible causes andsolutions written by the product team.3Find the STATMSG line in the component's logIt's logged when the message was raised, so the linesaround it give the context.4Decode the ISTR values and decimalsISTR0, ISTR1 fill the placeholders; decimals are oftenHRESULTs: 2147500037 is 0x80004005.5Fix the cause the message points toUse the usual cause and first check in the table for thatcomponent.6Reset Counts, then check for new errorsComponent Status counts errors over a period, so afixed component can stay red for a while.
Figure 1 · Process From a red component to its cause and back to green. Work through these steps for any red component; the tables below give the usual cause and first check for each message.

In the console, go to Monitoring › System Status › Component Status, right-click a component and choose Show Messages › All. The Status Message Viewer lists each message's ID and description. Open a message to see its full text: many error messages end with possible causes and solutions written by the product team, so read them first.

The same message is logged as a STATMSG line in the component's own log, at the moment it was raised, which gives you the surrounding context:

Text
STATMSG: ID=5436 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_MP_CONTROL_MANAGER" ... ISTR0="500" ISTR1="Internal Server Error"
  • ID is the message ID; SEV=I marks information and SEV=E an error.
  • ISTR0, ISTR1 and so on fill the placeholders in the description, here the HTTP status code and text.
  • Decimal numbers in descriptions are often HRESULTs: 2147500037 is 0x80004005 ('0x{0:X}' -f 2147500037 in PowerShell).

Which component does what, and its log:

  • SMS_WSUS_SYNC_MANAGER (WSyncMgr): synchronizes update metadata into WSUS and the site database; wsyncmgr.log.
  • SMS_WSUS_CONFIGURATION_MANAGER (WCM): applies the software update point settings to WSUS every hour; WCM.log. SMS_WSUS_CONTROL_MANAGER checks WSUS health on the software update point itself; WSUSCtrl.log, on that server when it's remote.
  • SMS_MP_CONTROL_MANAGER: tests whether the management point answers HTTP or HTTPS requests; mpcontrol.log.
  • SMS_DISTRIBUTION_MANAGER (DistMgr) manages content and creates jobs for SMS_PACKAGE_TRANSFER_MANAGER, which copies it to distribution points; distmgr.log and PkgXferMgr.log.
  • SMS_SITE_COMPONENT_MANAGER installs site system roles (sitecomp.log); SMS_HIERARCHY_MANAGER processes and replicates site hierarchy changes (hman.log); SMS_POLICY_PROVIDER creates and updates policies (policypv.log).

Software update sync (SMS_WSUS_SYNC_MANAGER)#

A healthy sync at the top-level site raises 6701, 6704 and 6705, then 6702. A child site raises 6701, then 6706 for any replica software update points, then 6702. WSUS lists a sync started by Configuration Manager as a manual synchronization, even when a schedule triggered it.

CodeMeaningUsual causeFirst check
6701WSUS synchronization startedA scheduled or manual sync began, or a child site received its parent's notificationIf nothing follows, the wsyncmgr.log lines after it
6704WSUS synchronization is in progress (WSUS syncs from Microsoft Update or the upstream server)Normal; slow on a first sync or after adding productssync: WSUS synchronizing updates, processed … lines
6705WSUS synchronization is in progress (site database phase)Normal; WSyncMgr writes updates into the site database as configuration itemssync: SMS synchronizing updates lines; SQL Server load if it stalls
6706WSUS synchronization is in progress (replica software update points)Normal at sites with more than one software update point; the text mentions an internet-facing server even when the replica isn't oneThe replica named after Synchronizing replica WSUS servers
6702WSUS synchronization finishedSuccessNothing to fix
Sync failed: WSUS server not configured. Please refer to WCM.log for configuration error details.WSyncMgr won't sync because WCM couldn't configure WSUS; it retries in 60 minutesProxy, authentication, port or SSL problems between the site server and WSUSWCM.log (next table)
0x80072EFE - The connection with the server was terminated abnormallyWSUS couldn't complete the connection to Microsoft UpdateInternet access, firewall or proxy on the top-level software update point; the sync endpoint accepts only TLS 1.2The WSUS server's internet access, proxy and TLS settings

Two more things WSyncMgr does: if the console isn't available, a zero-byte SELF.SYN file in the WSyncMgr.box inbox on the top-level site server starts a sync (Microsoft advises this only as a fallback). It also removes expired updates from the site database when the component starts and at the end of a sync, at most every three hours; look for Deleted N expired updates to confirm the cleanup runs.

WSUS configuration (SMS_WSUS_CONFIGURATION_MANAGER)#

WCM records its result as a configuration state: 0 none, 1 pending, 2 success, 3 failed, 4 subscription pending. These errors in WCM.log usually explain a failed state:

CodeMeaningUsual causeFirst check
The request failed with HTTP status 401 or 403Unauthorized or ForbiddenThe WSUS Server Connection Account, or missing rights on the ApiRemoting30 virtual directoryEdit Permissions on ApiRemoting30 in IIS Manager
The request failed with HTTP status 407 or 502Proxy Authentication Required or Proxy ErrorA proxy in the path rejects or can't forward WCM's requestProxy and account settings of the software update point
The request failed with HTTP status 500 or 503The WSUS web service failedUpdate Services service or WSUS website stopped or unhealthyThe service, the website, then wsusutil.exe checkhealth and the Application log
No connection could be made because the target machine actively refused itNothing answered on the port WCM usedPorts in the software update point properties don't match the WSUS websitePort settings on both sides
Authentication failed because the remote party closed the transport streamThe TLS connection failedSSL is enabled for the software update point but WSUS isn't correctly set up for itThe WSUS certificate's FQDN and expiry; WSUS SSL configuration
WSUS_CONFIG_FAILED (state 3)WCM couldn't apply the settings to WSUSOne of the errors aboveThe lines before Setting new configuration state

Management point (SMS_MP_CONTROL_MANAGER)#

CodeMeaningUsual causeFirst check
5436MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 500, Internal Server Error (or 403, Forbidden).Causes the message lists: SQL Server access (the MP's account not in smsdbrole_MP), SQL SPNs, IIS not on the site's ports, the website disabled, or the MP ISAPI identity denied batch logonmpcontrol.log, then IIS logs and the database role (see management point unhealthy)
The http error is 2147500037MP Control Manager detected MP is not responding to HTTP requests; the error is 0x80004005The message suggests the SMS Agent Host service or IIS isn't responding; on HTTPS sites, no usable client certificateFailed to retrieve client certificate in mpcontrol.log; restart SMS Agent Host and W3SVC

Content distribution (SMS_DISTRIBUTION_MANAGER)#

CodeMeaningUsual causeFirst check
2302Distribution Manager failed to process package "<name>" (package ID = <ID>).Causes the message lists: no access to the source folder or distribution point, paths too long, low disk space on the site server or distribution point, source files in usedistmgr.log filtered on the thread for that package ID
Distribution Manager failed to connect to the distribution point.DistMgr can't reach or manage the distribution pointAccess permissions: the site server's computer account or the Site System Installation account isn't an administrator on the distribution pointLocal Administrators on the distribution point
~Currently using 3 out of 3 allowed package processing threads.Every package processing thread is busyA large queue, or stuck threadsPackages Being Processed under HKLM\SOFTWARE\Microsoft\SMS\Components\SMS_DISTRIBUTION_MANAGER

The step-by-step fixes are in content not reaching distribution points.

How to verify a fix#

  • Sync: run Synchronize Software Updates and watch for 6701, the progress messages and then 6702 (Sync succeeded at child sites). Monitoring › Software Update Point Synchronization Status should show a recent successful sync for every software update point.
  • WCM: the next hourly cycle logs Setting new configuration state to 2 (WSUS_CONFIG_SUCCESS) or No changes - WSUS Server settings are correctly configured.
  • Management point: mpcontrol.log shows Successfully performed Management Point availability check against local computer. and no new 5436 messages.
  • Distribution: the package reaches Success under Monitoring › Distribution Status › Content Status.

Component Status counts errors over a period, so a fixed component can stay red for a while. Right-click it and choose Reset Counts after the fix, then check for new errors. To see the latest sync messages in the log:

PowerShell
$log = 'C:\Program Files\Microsoft Configuration Manager\Logs\wsyncmgr.log'   # your install path
Select-String -Path $log -Pattern 'STATMSG: ID=67' | Select-Object -Last 10

References#

TagsSite serverQuick referenceComponent statusStatus messages

Written and checked against current Microsoft Learn documentation. Test changes with a pilot group before rolling them out to everyone, and if an admin center path has moved since, search for the setting name instead.

Spotted a mistake, or did this fix work differently for you? Email me or message me on LinkedIn — corrections are credited in the article.

Written by

Omer Eltayeb

M365 Subject Matter Expert, former Microsoft Cloud Solutions Architect, Microsoft Certified Trainer and Microsoft Innovative Educator Expert (2024–26) and Microsoft Elevate Educator Expert (2026–27). I share practical, step-by-step guides, study plans, scripts and toolkits for Microsoft Intune, Configuration Manager, Microsoft Entra ID, Microsoft Defender, Exchange and Microsoft 365 with the community.

Microsoft Certified Trainer (MCT) 2026Microsoft Innovative Educator Expert 2025–2026Microsoft Elevate Educator Expert 2026–2027ISC2 Certified Information Systems Security Professional (CISSP)Microsoft 365 Certified: Enterprise Administrator Expert (MS-102)
Connect on LinkedIn My community contributions More about me
Keep reading

More Configuration Manager articles

All Configuration Manager articles