> 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/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000009180.md).
# Troubleshooting "file is not properly formatted" warning on the MiSeq
**Background**
The following warning messages may occur if the MiSeq Control Software (MCS) is reading the files in the output location and is not recognizing the formatting of these files.
**Warning:** The RunParameters.xml file located at \['file path'] is not properly formatted.
* This warning may result from a communication error on the MiSeq. Potential communication-related causes include corrupted formatting or old files generated by outdated control software versions at the output location. In some cases, this is a temporary situation that requires no action.
* This warning does not impact run performance or prevent users to start a new run. The instrument can continue to be used, even if this warning is displayed.
**Troubleshooting steps**:
1. Check if the mentioned file (following the file path) is corrupt.
1. If it is corrupt, remove the file from the folder to avoid future communication errors with the MCS.
2. If the is not corrupt, back up these files to an external hard drive or another location, as there may be some momentary incompatibility between these files and the checks made by the MCS.
2. Power cycle the MiSeq (**Note:** If a run is in progress, let the run finish before power cycling, as this will cause the run to be terminated). For detailed instructions, please review [How to Power Cycle the MiSeq](/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000001894.md) or [How To Power Cycle the MiSeq Video](/instrumentation/miseq-ruo/instrumentation-miseq-ruo-reference_material-list/000005871.md).
3. If there are no warnings with re-initialization, the instrument is clear to use.
\
\
\
| |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #9180), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000009180%20-%20Instrumentation%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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://knowledge.illumina.com/instrumentation/miseq/instrumentation-miseq-troubleshooting-list/000009180.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.