I changed the identity of the WSUS application pool from Network Service to Local System and everything fired right up. We shall see if I can sync or not, I bet I can't; however, if it fails I will post a new question if my research fails me because the nature of the problem has changed, it wasn't an installation issue, it was something to do with IIS. So the good news: WSUS works, or at least the snap-in works, by going into the IIS snap-in, selecting application pools, choosing WSUSPool, right click >advanced settings, and under process model changing identity 'Network Service' to 'local system'. The bad news: I am not confident WSUS will be able to pull updates from the upstream server. At least it's progress!

Things 2 Mac Keygen App on this page. Since a few days we get this error with a few users. Equalizzazione Riaa Software House there. 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.

Windows Server Update Services Event Category: None Event ID: 7053 Date: Time: 4:19:36 PM User: N/A Description: 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. The Windows Server Update Services (WSUS) console crashes when browsing for updates and displays the following error message: 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 Category: None Event ID: 7053 Date: Time. The Windows Server Update Services console crashes. Windows Server Update Services 3.0 Windows Server Update Services 3.0 Service Pack 1. May 12, 2012 - It is a downstream server. Try removing the persisted preferences for the console by deleting the wsus file under%appdata% Microsoft MMC. Stack Trace: at Microsoft.UpdateServices.Internal.ClassFactory.CallStaticMethod(Type type, String methodName, Object[].

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. 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.