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

# Troubleshooting 'Not Found' error message on NextSeq 500/550

The following error is related to antivirus software (eg, McAfee) considering Illumina's Real-Time Analysis (RTA) as a security threat and archiving the respective executable file (RTA.exe) for quarantine. This error can occur right when the run starts, causing the consumables to be marked as used (and unable to be used for further attempts at starting the run).

***Error message: Not Found (ServiceStack.ServiceClient.Web.WebServiceException)***\
![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-d7ec5d41d55b0826fcfc20f72f0f842068620954%2Fimage1.png?alt=media\&token=44477fee-7dc2-4aa7-90a7-abb7c7afd37c)

**Troubleshooting steps:**

Follow the guidelines for antivirus configuration in the [Illumina Instrument Control Computer Security and Networking Guide](https://support.illumina.com/downloads/networking-security.html).

* Install the antivirus software only when the instrument is not in use and the instrument can be rebooted.
* Do not allow the computer to reboot automatically after install.
* Set antivirus software to manual scans. **Do not enable automatic scans**.
* Perform manual scans only when the instrument is not in use.
* Set updates to download without user authorization, but not to install.
* Exclude the application directory and data drives from any real-time file system protection.

Windows Defender is off by default and it must remain off. This Windows product can affect the computer resources used by Illumina software.

\
\
\ <br>

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