IIS services down – "Error parsing XML file. Reason: An invalid character was found in text content" – 4275 Event from IIS Config in the System event log


Problem


IIS Services are not starting

Symptoms

You may see the following events in the System Event log:


Event 7024 from Service Control Manager – The IIS Admin Service service terminated with service-specific error
2149648394 (0x8021080A)



Event 4275 from source IIS Config – Error parsing XML file. Reason: An invalid character was found in text
content.


Resolution


This may be due to some process editted the Metabase.xml. To start the services back, try the following steps:


  1. First, try to verify you have a backup of your Metabase. To know open the Metaback folder under C:\Windows\system32\inetsrv. Try to pick the most recent backup and copy the .SC1 file to Metabase.XML under inetsrv folder

  2. If you didn’t see any recent backups, you can also open the History folder under C:\Windows\system32\inetsrv. Try to pick the recent Metabase_0000xxxx.XML file and the MBSchema_0000xxxx.XML file and copy them as Metabase.XML and MBSchema.XML under inetsrv folder

But, before doing any of the above steps, make sure that you have copied the old Metabase.XML and MBSchema.XML somewhere in your file system.


Happy Troubleshooting!

Comments (10)

  1. Alan says:

    Fixed it.  thanks

  2. Tomas says:

    Had an error:

    "Error parsing XML file. Reason: An invalid character was found in text content"

    Fixed it by following your resolution – you saved my day!

  3. Atul Mathur says:

    Great.. I was able to fix my IIS with this solution.

  4. Len says:

    Thanks man, followed your instruction and it worked!!!

  5. Uma Maheshwaran says:

    great man…thanks for ur info

  6. Bazza says:

    Did the job, the Terminal Server had bad power to the RAID pair and files got damaged and one drive dropped out. I did this after fixing the power etc and hay presto, just like magic!! Thanks heaps dude!

  7. Nat says:

    Thanks very much for your help.

    I also found a post on EE that said this can be caused if you AV software scans the files, and recommends you setup an exclusion.

  8. Blair Lock says:

    Big Respect Thank u this solution works!

  9. NLV says:

    Thanks for your help. It helped me.

  10. NLV says:

    Thanks for your suggestion. It helped me.