Wsus blew a gasket on Sunday and I rebooted the SCCM server yesterday. As of today I cannot load the wsus console. I know you are not supposed to use the console but it use to work. I have SCCM-2012 R2 SP1 CU1 installed.

Any thoughts on what

Does the WSUS integration in SCCM still work?

Have you look at the monitoring node to see if any issue with WSUS ?

Did you look at the log ?

Are the sync still working or you seeing the new update. In SCCM can you change the catalog to request new update or product ?

hard to help you if all you are saying is that the WSUS console doesn't open?

• Edited by Frederick Dicaire 15 hours 31 minutes ago

It appears to be syncing with SCCM at this point. When I rebooted yesterday the ccmexec.exe was using over 8 gigs of ram.

The wsusctrl.log is showing the following error on a regular basis:

Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701.

But it says it is connecting to WSUS server.

"This snap-in is not responding" is the error once the console times out when trying to open it.

On a side note, the process ccmexec.exe was using over 8 gigs of ram before the reboot yesterday.

Opps sorry about the repeat of the runaway process.

This is a bug don't worry about it

https://social.technet.microsoft.com/Forums/en-US/4181ea8a-c4ae-4713-aa4a-e5a56d4b56b1/failed-to-create-assembly-name-object-for-microsoftupdateservicesadministration-error-?forum=configmanagersecurity

• Edited by Frederick Dicaire 15 hours 8 minutes ago
• Marked as answer by Ed - LSUHSC 14 hours 34 minutes ago

That explains the error message but not the console. Interestingly enough the system has now calmed and the console is working. So never mind until it blows up again.