> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/microarray/general/microarray-general-troubleshooting-list/000009628.md).

# Troubleshooting the "Root element is missing" error on the iScan

If the error "Root element is missing" occurs on an iScan, this often indicates a corrupted RunSummary.xml file and the following message will present:

"**Root element is missing. (System.Xml.XmlException)**

Details:

* There is an error in XML document (0,0)"

  ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-80094dfb510026ff93456741d1080dd42eb06438%2Fimage1.png?alt=media)

**Figure 1.** Example of the "Root elements is missing" error.

A corrupted RunSummary.xml file might be blank. Check for file corruption in the following path:

* C:\RunSummary.xml

A non-corrupted RunSummary.xml file should look like this:

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-13f3158936fdd6227413c488e88d8551d8feb31c%2Fimage2.png?alt=media)

**Figure 2.** Non-corrupted RunSummary.xml file. Note that the value listed in the RunCount line will vary depending on the number of runs that the scanner has undergone.

**Troubleshooting steps:**

1. Make a copy of the RunSummary.xml file to the desktop and rename this as RunSummary - old.xml
   * Contact [Illumina Technical Support](https://emea.illumina.com/company/contact-us.html#/united-states/technical-support) to obtain an uncorrupted new RunSummary.xml file or copy it from another functional iScan under the file path: C:\RunSummary.xml.
2. Replace the old RunSummary.xml file in the C:\ drive with a new or copied RunSummary.xml file.
3. Power cycle iScan and re-initialize the control software.
4. Re-scan the BeadChip(s).
5. If the issue is resolved, remove/delete the old RunSummary.xml file from the iScan computer.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                   |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #9628), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000009628%20-%20Microarray%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.illumina.com/microarray/general/microarray-general-troubleshooting-list/000009628.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
