> 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/novaseq-6000/instrumentation-novaseq-6000-troubleshooting-list/000006548.md).

# Troubleshooting "Component Failed" errors immediately after Pre-Run Checks on the NovaSeq 6000

**Background**

The NovaSeq 6000 performs several key steps between the completion of the Pre-Run Checks and the start of a Sequencing run. If there are issues completing any of these steps, the Control Software typically stops the sequencing run within 1-2 minutes of completing the Pre-Run Checks and presents an error indicating, "A component failed during sequencing..."

If this issue occurs at the start of the sequencing run, the consumables can often be reused. However, it is important to review the issue with Illumina Technical Support before attempting a repeat sequencing run.

**Troubleshooting Actions**

If the Control Software presents, "A component failed during sequencing..." error within 1-2 minutes of starting the sequencing run, see the following steps and contact Illumina Tech Support.

1. Collect the following files/folders:
   1. Control Software Logs: `C:\ProgramData\Illumina\NovaSeq\NovaSeq Control Software\Logs folder`
   2. Run Logs (if present): `C:\ProgramData\Illumina\NovaSeq\NovaSeqTemp\<RunID>\Logs`
   3. Universal Copy Service Logs: `C:\ProgramData\Illumina\Universal Copy Service\Logs`
2. Note whether the instrument is configured to connect to **Proactive** or **BaseSpace**
   1. Select the dropdown menu in the top-left corner, then select **Settings**.
   2. For BaseSpace, note whether the **Cloud Settings** or **BaseSpace Sequencing Hub** checkbox is selected.
   3. For Proactive, note whether the **Send Instrument Performance Data to Illumina** checkbox is selected.
3. Once these files and information are collected, please call [Illumina Technical Support](https://www.illumina.com/company/contact-us.html) for next steps.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #6548), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000006548%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 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/instrumentation/novaseq-6000/instrumentation-novaseq-6000-troubleshooting-list/000006548.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.
