This is the Windows Server Update Services support team blog. We cover all things relating to WSUS and Windows Update.
Here’s a new Knowledge Base article we published. This one talks about an issue where the Windows Server Update Services (WSUS) console crashes when browsing for updates and generates an Event ID 7053.
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: User: N/A Computer: Description: The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console.
This can occur if the application cache is corrupted.
To resolve this issue, delete the WSUS application cache from the location below:
C:\Documents and Settings\<user profile>\application data\microsoft\mmc
where user profile is the currently logged in user profile.
For the most current version of this article please see the following:
2761925 - The Windows Server Update Services console crashes when browsing for updates
J.C. Hornbeck | Knowledge Engineer | Management and Security Division
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
How did the application cache get corrupted? The problem with clearing this cache is that you lose your customizations to the console. Since this crash occurs fairly frequently, you're frequently resetting the console settings.
wsus is shite, microsoft should be ashamed of releasing a product meant to help but is so unstable its no use