An unexpected error occurred. Click reset server node to try to connect to the server again Event Type: Error Event Source: Windows Server Update Services Event. Jun 07, 2016 Windows 2012 R2 VM SQL 2012 Enterprise WSUS 6.3 I. Windows Server Update Services. Oct 10, 2012 This is the Windows Server Update Services support team blog. We cover all things relating to WSUS and Windows Update.

Usually WSUS just works. Server 2012 with WSUS. MMC locks up and event log show: The WSUS administration console has encountered an unexpected error.

This may be a transient error; try restarting the administration console. If this error persists, Try removing the persisted preferences for the console by deleting the wsus file under%appdata% Microsoft MMC. The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists, Try removing the persisted preferences for the console by deleting the wsus file under%appdata% Microsoft MMC. The WSUS administration console has encountered an unexpected error.

This may be a transient error; try restarting the administration console. If this error persists, Try removing the persisted preferences for the console by deleting the wsus file under%appdata% Microsoft MMC. System.Threading.ThreadAbortException -- Thread was being aborted.

Since a few days we get this error with a few users. When starting the WSUS MMC we get a button 'Reset Server Node', when clicking on this button, nothing happens. Here is the actual error: The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

System.Net.WebException -- The request failed with HTTP status 400: Bad Request. So a few weeks ago we've found the cause of the problem. The support call didn't help us that much, but looking at this problem from a different angle did. The affected users where member of too many Active Directory security groups.

Ski Doo Graphics Templates. We have set the MaxTokenSize on the workstations, domain controllers and member servers. But this didn't solve it.

Making the user member of less security goups did! Before we set the MaxTokenSize we had similar problems with some users/applications. This in combination with a migration to one Active Directory we decided to set the value. But this doesn't help in this case. I don't remember the exact treshold. But removing the affected users from a few groups did solve it. Thanks everyone.

First I get Event ID: 7032: Event Type: Warning Event Source: Windows Server Update Services Event Category: None Event ID: 7032 Date: 16-6-2011 Time: 10:39:15 User: N/A Computer: CW021550 Description: The WSUS administration console was unable to connect to the WSUS Server via the remote API. Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.