About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
When you open Update Services on a WSUS server and the console shows "Error: Connection Error", the console could not connect to the WSUS server. Microsoft's page gives the whole message as: "An error occurred trying to connect to the WSUS server. This error can happen for a number of reasons. Please contact your network administrator if the problem persists. Click the reset Server Node to connect to the server again."
The message itself tells you to click Reset Server Node "to connect to the server again". If it fails again, read two things in this order: the WsusPool application pool in IIS, and, because Microsoft's page also lists the services WSUS depends on, those services. A different message, "An unexpected error occurred", with event 7053, has a separate cause and is covered below.
What the error means
Microsoft's "WSUS Messages and Troubleshooting Tips" page lists the message together with a second symptom. Browsing to the WSUS Administration website, for example http://WSUS01:8530, fails with "HTTP Error 503. The service is unavailable". Of that situation Microsoft says: "In this situation, the most likely cause is that the WsusPool Application Pool in IIS is in a stopped state." The page adds that the Private Memory Limit (KB) of the pool "is probably set to the default value of 1843200 KB".
The same page covers services that have to be running. Microsoft names the Selfupdate service, WSSUService.exe (shown in the Services list as Windows Server Update Service), the web services hosted in IIS, and the SQL service. It says "Every service except for the selfupdate service requires that the SQL service is running."
A different Microsoft page, "The Windows Server Update Services console crashes when browsing for updates" (KB 2761925), describes a console that shows "An unexpected error occurred. click reset server node to try to connect to the server again", together with this event: Event ID 7053, source "Windows Server Update Services", description "The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console." Microsoft gives the cause as a corrupted application cache.
A third Microsoft post, archived and written in 2008, describes yet another cause for a console that cannot connect to a WSUS server instance on the same machine: a firewall on the local system blocking the console's connection attempts. Its messages are different ("The WSUS administration console was unable to connect to the WSUS Server via the remote API"), so match the text on screen before choosing a fix.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| WsusPool is stopped | "Error: Connection Error"; the WSUS site returns "HTTP Error 503. The service is unavailable" | IIS Manager, Application Pools: WsusPool is stopped |
| WsusPool has a Private Memory Limit at the default | Same Connection Error and 503 page | Microsoft says the limit "is probably set to the default value of 1843200 KB"; read it in WsusPool Advanced Settings |
| A service WSUS needs is not running (Microsoft's page lists these services as ones that must be running, but does not tie them to this message) | Connection Error; synchronisation problems | Services shows the Windows Server Update Service, IIS or SQL service stopped |
| A different console message: corrupted application cache | "An unexpected error occurred. click reset server node..." when browsing for updates, with Event ID 7053 | The event is logged with source "Windows Server Update Services"; Microsoft's page does not name the log |
| Local firewall blocks the console | "unable to connect to the WSUS Server via the remote API" | Different message; Microsoft's post says to test and then allow the connection |
Prove the cause before changing anything
All of these only read. Do them on the WSUS server.
- Browse to the WSUS Administration website, for example
http://WSUS01:8530. If you see "HTTP Error 503. The service is unavailable", go to the WsusPool check. - Open Internet Information Services (IIS) Manager and select Application Pools. Read the state of WsusPool.
- Right-click WsusPool, select Advanced Settings and read Private Memory Limit (KB). Write it down.
- Open Services and find Windows Server Update Service. Microsoft's page says to check its state, and to use Event Viewer to check the Application, Security and System event logs "to see if there are any events that might indicate a problem."
- In the same list find the SQL service Microsoft names: MSSQLSERVER for a default instance, or MSSQL$WSUS "if you're using a SQL Server database and have named your database instance WSUS". Note whether it is running.
- In Event Viewer look for Event ID 7053 from "Windows Server Update Services". Microsoft's page gives the event's type, source and ID but not the log it is written to, so check the logs Microsoft's WSUS page names: Application, Security and System.
Example (illustrative): at contoso.com.au the administrator of wsus01 opens the console after a Sunday patch run and sees "Error: Connection Error". http://wsus01:8530 returns "HTTP Error 503. The service is unavailable". IIS Manager shows WsusPool stopped, and its Private Memory Limit (KB) reads 1843200. The Windows Server Update Service and MSSQL$WSUS are both running. That matches the first two rows, so the pool is the next thing to change, not the services.
Fix
Change one thing, then test the console again. Start with the cause your checks found.
WsusPool stopped or at its memory limit
Disruptive step: the memory-limit change and the pool restart stop WSUS answering the console and clients while the pool restarts.
The change for a stopped pool or one at its default memory limit is the change Microsoft's WSUS messages page gives for this console error. It is written out in full, with its save-first step, warning and back-out, in Windows Update error 0x80244022 against WSUS: HTTP 503 and the WsusPool application pool. Use it when the pool checks above point to the pool, then come back to the console.
A WSUS, IIS or SQL service is stopped
Before you change anything, write down which of the three services was running and which was stopped.
Disruptive step: starting or restarting these services interrupts WSUS. A restart of the SQL service interrupts WSUS, and iisreset restarts IIS, which serves every site on the server.
Microsoft's page says: select Start if the service is stopped, or Restart to refresh it, for the Windows Server Update Service and for the SQL service. For the web services it says "ensure that IIS is running (or started)" and gives the reset command, which you run at an elevated command prompt:
iisreset
To undo it: nothing needs undoing. A restarted service runs again as before. If you started a service that had been stopped on purpose, stop it again from the Services list.
The "unexpected error" message with Event ID 7053
This is a different message from the Connection Error, and the WsusPool and service checks above do not apply to it. Microsoft's page gives the cause as a corrupted application cache and the resolution as: "delete the WSUS application cache from the location below", which it gives as C:\Users\<user profile>\AppData\Roaming\Microsoft\MMC, where the user profile is the one currently signed in.
Microsoft's page does not say which file or files in that folder are the WSUS application cache, and other console settings for that user may live in the same folder, so there is no way to select the right object from the page. Ask the person who administers the console, or Microsoft support, which file to remove.
Confirm the fix
- Open Update Services and select the server node. The console should connect without the connection error.
- Browse to the WSUS site address again; the 503 page should be gone.
- In IIS Manager, WsusPool shows as started, and it is still started an hour later.
- No new Event ID 7053 from "Windows Server Update Services" in Event Viewer.
What to watch afterwards
- WsusPool state after the next clients' scan cycle, if you changed it.
- Clients that report 0x80244022 or "Computer hasn't reported status". Microsoft's page says the second message "is typically caused by the WSUS client computer, not the WSUS server", so a connected console does not mean every client is healthy.
- Synchronisation. The same Microsoft page lists "Message ID 6703 - WSUS Synchronization Failed" with "The request failed with HTTP status 503: Service Unavailable." in the same list of messages, directly above the console error and its 503 explanation.
Read next
Related articles you may want next.
- TroubleshootingWindows Update error 0x80244022 against WSUS: HTTP 503 and the WsusPool application poolWindows Update error 0x80244022 against WSUS means HTTP 503. Check the WsusPool application pool, its memory limit and the detectoid cleanup.Read article
- TroubleshootingWindows Update error 0x8024402C: the proxy or WSUS server name cannot be resolvedWindows Update 0x8024402C: the proxy or target server name cannot be resolved. Check the WinHTTP proxy and the WSUS server name before changing either.Read article
- TroubleshootingIIS 502 and 503 Errors: Find the Failing Request LayerUse IIS status fields, worker-process evidence and proxy logs to separate application-pool failures from upstream errors and backend timeouts.Read article
Risks and limits
These commands have not been run or lab-tested.
Microsoft's WSUS messages page names no Windows Server version beyond "Supported versions of Windows Server". The console-cache page does not say which file in the MMC folder holds the cache, so no deletion step is given. The archived firewall post gives no port list and no rule, and Microsoft's Windows Update troubleshooting page says that "Stopping the service associated with Windows Firewall with Advanced Security isn't supported by Microsoft". The archived post says "Either disable the firewall or configure a rule to allow the connection"; no firewall step is given here.
Sources
- WSUS Messages and Troubleshooting Tips — Microsoft Learn, page dated 2026-02-12, accessed 22 November 2026
- The Windows Server Update Services console crashes when browsing for updates — Microsoft Learn, page dated 2026-03-30, accessed 22 November 2026
- WSUS: Console fails to connect with "The WSUS administration console was unable to connect to the WSUS Server via the remote API" error — Microsoft Learn, page dated 2008-10-15, accessed 22 November 2026
- Windows Update issues troubleshooting — Microsoft Learn, page dated 2026-02-12, accessed 22 November 2026
This article was originally published on .