I started having issues with the WSUS console (2012 R2). It would throw an error but if I click reset server node, then it is ok. I narrowed it down to a computer group. When I clicked on the group, it would error out. I cleared the MMC cache and when I click on the group, it is ok. However, the default view is 'failed or needed'. When I change the view in this group to 'any' then it fails again. It only happens with this one group. I get the same error when trying to view from powershell. Database is SQL 2012 express. I have a couple workarounds I could try but wanted to get some opinions first from some SQL experts as to how to troubleshoot since this is a weak area for me.
Log Name: ApplicationSource: Windows Server Update ServicesDate: 7/21/2016 8:52:23 AMEvent ID: 7053Task Category: NoneLevel: ErrorKeywords: ClassicUser: N/AComputer: <server>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 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.Xml.XmlException -- '', hexadecimal value 0x16, is an invalid character. Line 1, position 36072.SourceSystem.XmlStack Trace: at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.ParseNumericCharRefInline(Int32 startPos, Boolean expand, StringBuilder internalSubsetBuilder, Int32& charCount, EntityType& entityType) at System.Xml.XmlTextReaderImpl.ParseCharRefInline(Int32 startPos, Int32& charCount, EntityType& entityType) at System.Xml.XmlTextReaderImpl.ParseText(Int32& startPos, Int32& endPos, Int32& outOrChars) at System.Xml.XmlTextReaderImpl.ParseText() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XmlReader.ReadStartElement() at System.Xml.Serialization.XmlSerializationReader.ReadStringValue() at System.Xml.Serialization.XmlSerializationReader.ReadTypedPrimitive(XmlQualifiedName type, Boolean elementCanBeType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderApiRemotingCompressionProxy.Read1_Object(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderApiRemotingCompressionProxy.Read2_GenericReadableRow(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderApiRemotingCompressionProxy.Read339_Item() at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)** this exception was nested inside of the following exception **System.InvalidOperationException -- There is an error in XML document (1, 36072).SourceSystem.XmlStack Trace: at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events) at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPSearchComputers(String computerTargetScopeXml) at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchComputers(String computerTargetScopeXml) at Microsoft.UpdateServices.Internal.BaseApi.ComputerTarget.SearchComputerTargets(ComputerTargetScope searchScope, UpdateServer updateServer) at Microsoft.UpdateServices.UI.AdminApiAccess.ComputerTargetManager.GetComputerTargets(ComputerTargetScope searchScope) at Microsoft.UpdateServices.UI.AdminApiAccess.BulkComputerPropertiesCache.GetAndCacheComputers(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope) at Microsoft.UpdateServices.UI.SnapIn.Pages.ComputersListPage.GetListRows()
Try to find which are the computers on the faulty group, then run the WUAUCLT /reportnow command on these computers to force then to overwrite their data on the WSUS database. Then try to open the faulty group again.
If that fails, you will have to rebuild the entire database (discard and create a new one), or restore a previously saved copy of the database.
Editing the internal records of the WSUS database is not supported by Microsoft as you can read here. If you take that risk you may end with a corrupted database and everything can get worst.
Seth Simmons
ASKER
still working on this
some users are traveling or on vacation
Try to find which are the computers on the faulty group, then run the WUAUCLT /reportnow command on these computers to force then to overwrite their data on the WSUS database. Then try to open the faulty group again.
If that fails, you will have to rebuild the entire database (discard and create a new one), or restore a previously saved copy of the database.
Editing the internal records of the WSUS database is not supported by Microsoft as you can read here. If you take that risk you may end with a corrupted database and everything can get worst.