> 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-500-550/instrumentation-nextseq-500-550-troubleshooting-list/000007806.md).

# Troubleshooting Local Run Manager originally caused by an internal server error on NextSeq 500/550

The "Local Run Manager: Originally caused by an internal server error" notification in the NextSeq 500/550 Control Software (NCS) can indicate either a transient communication issue or that the PostgreSQL service is not running.

**Troubleshooting steps:**

1. Power cycle the NextSeq 500/550 following the instructions in [How to Power Cycle the NextSeq 500/550](/instrumentation/general/instrumentation-general-reference_material-list/000001972.md).
2. If the NCS reinitializes without errors, continue with next sequencing run.
3. If the notification persists in the NCS after a power cycle, restart the PostgreSQL service using the following steps:
   1. Close the NCS.
   2. Search for the Services App in Windows task bar, then right-click and select **Run as Administrator**. Enter the sbsAdmin or other local windows admin-level account password
   3. Search for **PostgreSQL** and check to see if it is 'Running'. If not, right-click and select **Start**.
   4. Relaunch the NCS.

If the issue persists, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#) for additional assistance.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #7806), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000007806%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/nextseq-500-550/instrumentation-nextseq-500-550-troubleshooting-list/000007806.md?ask=<question>&goal=<endgoal>
```

`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.