> 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/nextseq-1000-2000/instrumentation-nextseq-1000-2000-reference_material-list/000008547.md).

# Lost connection with server error on the NextSeq 1000/2000

**Background**

If there is a System Failure: Lost connection with Server error on the NextSeq 1000/2000 instrument while the instrument is sequencing, **DO NOT** select "Yes, I'm finished", as this closes the Control Software and stops the run if it is ongoing.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-5366ba97b27d0babbfcab5bba618c598d06ab039%2Fimage1.jpg?alt=media\&token=719e1184-4b29-4b46-8fa6-5804d6791c6d)

Most often, the run continues sequencing even if it is not displayed on the control software. Please see the following instructions to verify if the run is still proceeding or if it has been completed:

To verify that the run is still sequencing:

1. Minimize the Control Software (if the three-line menu is not accessible, use the "Windows key + H" or "Alt + Spacebar" shortcuts)
2. Open the file navigation system and navigate to `/usr/local/illumina/runs/[run folder]/Data/Intensities/BaseCalls/L001`
3. Check date and timestamps to verify if new files and folders are being created

To verify that a run is completed:

1. Minimize the Control Software
2. Navigate to the output folder configured for the run
3. Check for the presence of the "CopyComplete.txt" file

Once the run completes, close the control software and re-initialize (selecting "Yes, I'm finished" will close the Control Software). [Power cycle](https://knowledge.illumina.com/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-reference_material-list/000003038.md) the instrument before starting the next run.

If the run completes successfully but the run is listed as Errored in Process Management, reach out to [Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) for help generating FASTQ files.

\
\
\ <br>

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