> 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/000001296.md).

# How to troubleshoot NovaSeq 6000 Process Management errors

**Background**

There are three types of errors/issues related to Process Management:

1. "Unable to start one or more processes in process management" error in the NovaSeq Control Software (NVCS).
2. Run listed as Running in Process Management tab even though the run is complete.
3. N/A icon is present in Process Management screen.

**1."Unable to start one or more processes in process management" error in NVCS**

###

This can occur after restarting Universal Copy Service (UCS) manually or when there are errors reading UCS files. **Note:** It can take up to five minutes for Process Management to detect that UCS is running and resolve the error message.

* If the issue persists after five minutes of starting the NVCS, restart UCS manually. For more details, see [How to stop and restart Universal Copy Service manually on the NovaSeq 6000](https://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-reference_material-list/000002543.md).
  1. Close the NVCS.
     1. Select the dropdown menu in the top-left corner, then select **Exit Application**.
  2. Open Windows Task Manager.
  3. Navigate to the **Process** tab, and review process list for ucs.exe or universal-copy-service.exe. If UCS is running, right-click the process and select **End Process**.
  4. Restart NVCS.
  5. Wait five minutes after initialization to see if the issue persists.
* If the error reoccurs, contact [Illumina Tech Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for the next steps.

**2. Run listed still in running status in Process Management tab even though the run is complete**

* Acknowledge the end of the current run in the NVCS and exit back to the home screen.
* If the issue persists and there is **NOT** another run in progress:
  * Close and reopen NVCS.
  * Perform a power cycle. For more information, review the Knowledge Base article [How to Power Cycle the NovaSeq 6000](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000002470.md).
* If the issue persists after the power cycle, contact [Illumina Tech Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for the next steps.

**3. If N/A icon is present in Process Management screen**

* If a run is in progress: close the Process Management screen, wait five minutes and reopen Process Management (**Note**: Do **NOT** exit out of the NVCS as that will end the run in progress).
* If a run is **NOT** in progress: power cycle the instrument. For more information, review the Knowledge Base article [How to Power Cycle the NovaSeq 6000](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000002470.md).
* Once instrument and NVCS initialize successfully, reopen Process Management screen.
* If the issue persists, stop and restart UCS manually. For more information, see the Knowledge Base article [How to stop and restart Universal Copy Service manually on the NovaSeq 6000](https://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-reference_material-list/000002543.md).
* If issue persists after power cycling and restarting UCS manually, contact [Illumina Tech Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for the next steps.

\
\
\ <br>

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