Asked by:
Best Practice Analyzer- Errors out on Servers - 2016 OS Desktop Experience In-Place Upgrade

Question
-
Over that last 2 weeks I have been tasked to do In-Place Upgrades of Domain Controllers in our Environment. A few of our DCs after I run the BPA will kick off and run as if all is good to then ERROR OUT. Here is 2 examples of the error we see:
DC04: Errors occurred while running BPA scan on DNS Server, Active Directory Domain Services, File and Storage Services
An Error occurred while parsing EntityName. Line 1 Position 356
DC06: Errors occurred while running BPA scan on DNS Server, Active Directory Domain Services, File and Storage Services
An Error occurred while parsing Entity Name. Line1, position 358
Could this be generated because of a Kerberos issue or another Authentication issue? How can I rectify this? Any help would be greatly appreciated.
Kevin C. (Pennsylvania)
ADDED 2/21/2018-- after digging deeper I am seeing an Event ID 4. User name and Server Name removed for Security --
Log Name: Microsoft-Windows-BestPractices/Operational
Source: Microsoft-Windows-BestPractices
Date: 2/21/2018 9:19:24 AM
Event ID: 4
Task Category: Model Invocation
Level: Error
Keywords:
User: XXXXRemoved for SecurityXXXX
Computer: XXXXRemoved for SecurityXXXX
Description:
System.Xml.XmlException: An error occurred while parsing EntityName. Line 1, position 358.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseEntityName()
at System.Xml.XmlTextReaderImpl.ParseEntityReference()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.LoadXml(String xml)
at Microsoft.BestPractices.CoreInterface.ScanMessageArtifact.ProcessMessage(String message)
at Microsoft.BestPractices.CoreInterface.ScanMessageArtifact.Load(DocumentCollection documents, DocumentMessage message)
at Microsoft.BestPractices.CoreInterface.ScanArtifact.ProcessResultMessages()
at Microsoft.BestPractices.CoreInterface.ScanArtifact.LoadXmlResult(String path)
at Microsoft.BestPractices.CoreInterface.EngineManager.TransformResults(FileInfo tempEngineDetailFile, String engineReport, String modelId, String subModelId, String computerName, String context, String& descriptionMessage)
at Microsoft.BestPractices.CoreInterface.EngineManager.RunScanCurrentFormatModel(Hashtable parameters, Runspace runspace, ScanMode mode)
at Microsoft.BestPractices.CoreInterface.EngineManager.RunScan(Hashtable parameters, Runspace runspace, ScanMode mode, String[] computerNames, String certificateThumbprint, String configurationName, PSCredential credential, AuthenticationMechanism authentication, Int32 port, Int32 throttleLimit, Boolean useSsl)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-BestPractices" Guid="{5218E51A-3996-4A9A-A75A-70BA4EB66312}" />
<EventID>4</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>1</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2018-02-21T14:19:24.517377900Z" />
<EventRecordID>622</EventRecordID>
<Correlation ActivityID="{75ECEB3C-A757-0000-5C65-057657A7D301}" />
<Execution ProcessID="588" ThreadID="9532" />
<Channel>Microsoft-Windows-BestPractices/Operational</Channel>
<Computer>XXXXRemoved for SecurityXXXX </Computer>
<Security UserID="S-1-5-21-1108622230-682851613-316617838-59714" />
</System>
<EventData>
<Data Name="String">System.Xml.XmlException: An error occurred while parsing EntityName. Line 1, position 358.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.ParseEntityName()
at System.Xml.XmlTextReaderImpl.ParseEntityReference()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.LoadXml(String xml)
at Microsoft.BestPractices.CoreInterface.ScanMessageArtifact.ProcessMessage(String message)
at Microsoft.BestPractices.CoreInterface.ScanMessageArtifact.Load(DocumentCollection documents, DocumentMessage message)
at Microsoft.BestPractices.CoreInterface.ScanArtifact.ProcessResultMessages()
at Microsoft.BestPractices.CoreInterface.ScanArtifact.LoadXmlResult(String path)
at Microsoft.BestPractices.CoreInterface.EngineManager.TransformResults(FileInfo tempEngineDetailFile, String engineReport, String modelId, String subModelId, String computerName, String context, String& descriptionMessage)
at Microsoft.BestPractices.CoreInterface.EngineManager.RunScanCurrentFormatModel(Hashtable parameters, Runspace runspace, ScanMode mode)
at Microsoft.BestPractices.CoreInterface.EngineManager.RunScan(Hashtable parameters, Runspace runspace, ScanMode mode, String[] computerNames, String certificateThumbprint, String configurationName, PSCredential credential, AuthenticationMechanism authentication, Int32 port, Int32 throttleLimit, Boolean useSsl)</Data>
</EventData>
</Event>
SCOM Alerting
- Edited by KevinPA17111 Wednesday, February 21, 2018 2:37 PM
Tuesday, February 20, 2018 9:33 PM
All replies
-
Hi Kevin,
For now, for your error message, I couldn't find the reference here, maybe you could take a look.
And for Upgrade Domain Controllers to Windows Server 2016, please also refer to the article below.
https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/upgrade-domain-controllers
Best Regards,
Mary
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Thursday, February 22, 2018 2:21 AM