Backup problem

Question

I am trying to run a backup to a network location but I keep getting an error.  I have checked the event viewer and it seems that I have some xml event log file somewhere that is corrupt.  Below is the event information.  Can anyone tell me what file it is that is corrupt and where I may find it so that I can delete it?  Thanks!

Log Name:      Application

Source:        VSS

Date:          3/6/2018 10:11:05 AM

Event ID:      8228

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Latitude

Description:

Fail to parse XML file.

 Reason An invalid character was found in text content.

Line 0x000003c0

 Position 0x000005dc, The event log file is corrupted.

Errorcode 0xc00ce508

 Problem text <WRITER_COMPONENTS xmlns="x-schema:#VssComponentMetadata" instanceId="d1e55f7b-c728-439c-9a1d-bbd370c63f72" writerId="be000cbe-11fe-4426-9c58-531aa6355fc4" backupSchema="0"><COMPONENT logicalPath="ASR" componentName="ASR" componentType="filegroup"><BACKUP_METADATA xmlns="" metadata="<AsrSif><Version AsrVersion="2.0"/><System MachineName="LATITUDE" Platform="AMD64" FirmwareType="2" OSVersion="10.0" BootWinDirectory="C:\WINDOWS" BootSysDirectory="C:\WINDOWS\system32" AutoExtend="1" SKU="0x10100"/><DiskBuses NumBusType="1"><BusType Key="1" Type="8"/></DiskBuses><Disks NumMbrDisks="0" NumGptDisks="1"><GptDisk NumPartitions="4" PartitionTableSize="4" BusKey="1" DeviceNumber="0" IsCritical="1" GptGuid="cc15d905-2885-4482-938d-1f6e50a201eb" MaxPartition="128" BytesPerSector="512" SectorsPerTrack="63" TracksPerCylinder="255" NumCylinders="243201" MediaType="12" DiskSize="2000398934016" IsExcluded="0" IsShared="0"><GptPartition PartitionIndex="0" PartitionFlag="6" PartitionType="c12a7328-f81f-11d2-ba4b-00a0c93ec93b" PartitionID="e410dc5a-4129-4fa6-9561-cacbb24da3fa" GptAttributes="0x0" GptName="

Operation:

   Writer Modifying Modifying Backup Document

Context:

   Execution Context: Requestor

   Writer Instance ID: {D1E55F7B-C728-439C-9A1D-BBD370C63F72}

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="VSS" />

    <EventID Qualifiers="0">8228</EventID>

    <Level>2</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2018-03-06T16:11:05.395487100Z" />

    <EventRecordID>13840</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Latitude</Computer>

    <Security />

  </System>

  <EventData>

    <Data>An invalid character was found in text content.

</Data>

    <Data>0x000003c0</Data>

    <Data>0x000005dc, The event log file is corrupted.

</Data>

    <Data>0xc00ce508</Data>

    <Data><WRITER_COMPONENTS xmlns="x-schema:#VssComponentMetadata" instanceId="d1e55f7b-c728-439c-9a1d-bbd370c63f72" writerId="be000cbe-11fe-4426-9c58-531aa6355fc4" backupSchema="0"><COMPONENT logicalPath="ASR" componentName="ASR" componentType="filegroup"><BACKUP_METADATA xmlns="" metadata="&lt;AsrSif&gt;&lt;Version AsrVersion=&quot;2.0&quot;/&gt;&lt;System MachineName=&quot;LATITUDE&quot; Platform=&quot;AMD64&quot; FirmwareType=&quot;2&quot; OSVersion=&quot;10.0&quot; BootWinDirectory=&quot;C:\WINDOWS&quot; BootSysDirectory=&quot;C:\WINDOWS\system32&quot; AutoExtend=&quot;1&quot; SKU=&quot;0x10100&quot;/&gt;&lt;DiskBuses NumBusType=&quot;1&quot;&gt;&lt;BusType Key=&quot;1&quot; Type=&quot;8&quot;/&gt;&lt;/DiskBuses&gt;&lt;Disks NumMbrDisks=&quot;0&quot; NumGptDisks=&quot;1&quot;&gt;&lt;GptDisk NumPartitions=&quot;4&quot; PartitionTableSize=&quot;4&quot; BusKey=&quot;1&quot; DeviceNumber=&quot;0&quot; IsCritical=&quot;1&quot; GptGuid=&quot;cc15d905-2885-4482-938d-1f6e50a201eb&quot; MaxPartition=&quot;128&quot; BytesPerSector=&quot;512&quot; SectorsPerTrack=&quot;63&quot; TracksPerCylinder=&quot;255&quot; NumCylinders=&quot;243201&quot; MediaType=&quot;12&quot; DiskSize=&quot;2000398934016&quot; IsExcluded=&quot;0&quot; IsShared=&quot;0&quot;&gt;&lt;GptPartition PartitionIndex=&quot;0&quot; PartitionFlag=&quot;6&quot; PartitionType=&quot;c12a7328-f81f-11d2-ba4b-00a0c93ec93b&quot; PartitionID=&quot;e410dc5a-4129-4fa6-9561-cacbb24da3fa&quot; GptAttributes=&quot;0x0&quot; GptName=&quot;</Data>

    <Data>

Operation:

   Writer Modifying Modifying Backup Document

Context:

   Execution Context: Requestor

   Writer Instance ID: {D1E55F7B-C728-439C-9A1D-BBD370C63F72}</Data>

    <Binary>2D20436F64653A2020425545584D4C4330303030303832302D2043616C6C3A2020425545584D4C4330303030303737362D205049443A202030303031303736302D205449443A202030303031323732342D20434D443A202022433A5C57494E444F57535C73797374656D33325C7762656E67696E652E657865222020202020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>

  </EventData>

</Event>

Answer 1

Thank you for the update.

We've found out that the error "Fail to parse XML file. Reason: An invalid character was found in text content." is commonly caused by bad characters in some of the partition names. In some cases, these bad characters are found on unused recovery partitions. To resolve your concern, we'd recommend that you check the link provided by Ralph75 on this thread and see if the steps would resolve the error you're encountering when creating a backup.

Let us know how it goes.

Answer 2

Thanks for the suggestion.  I tried, but it didn't work.  I am still having the same error.  I had actually already tried the DISM command.  Below is a screenshot of the command prompt that shows that no errors were found.  I assume that this means that whatever log file is corrupt, it is not considered in these scans.  Any other ideas?

Answer 3

Hi,

Since you can't create a backup file due to an unknown corrupted application within the system, we'd recommend that you run a system file check using the System File Checker and Deployment Image Servicing and Management tool. System File Checker (SFC) is a utility in Windows that scans for corrupted Windows system files. If it finds a problem, it will try to replace the problematic system files from a cached version that’s on your PC. If SFC can’t replace the files, the Deployment Image Service and Management Tool (DISM) can check the corrupted files then download and replace the files through Windows Update. 

For more information about the tools and how to run them on your device, see System file check (SFC) Scan and Repair System Files & DISM to fix things SFC cannot by ZigZag3143 (MS -MVP).

For anu results, kindly update this thread.