> 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-troubleshooting-list/000008923.md).

# Troubleshooting no DRAGEN License after installing DRAGEN BCL Convert 4.2

* The upgrade of the NextSeq 1000/2000 Control Software (NCS) from version 1.5 to 1.7 requires the removal of previous DRAGEN workflow versions.
  * Only DRAGEN workflow version 4.2 and later are compatible with NCS v1.7
* It is normal when initializing the control software after updating to receive the notification: The active DRAGEN workflow is not compatible.
  * For instructions on how to un-install previous versions and install the correct DRAGEN workflow in response to this warning, see Knowledge Base Article: Troubleshooting DRAGEN version warnings and errors after the NextSeq 1000/2000 Control Software upgrade to version 1.7

After older DRAGEN version workflows have been deleted and the newer DRAGEN BCL convert 4.2 has been installed, in some cases the DRAGEN license will not populate. This can cause an error to display when trying to start a sequencing run.

![](/files/o4hwWY1lww0fYIKQjfi3)

To allow the DRAGEN license to display:

1. Login to ilmnadmin account on the instrument.
2. Download the DRAGEN BCL Convert workflow installer from Illumina's website: [here](https://support.illumina.com/downloads/dragen-workflow-bclconvert-installer.html)
3. In the Control Software, Navigate to the menu > DRAGEN > Browse for New Version > Select the DRAGEN BCL Convert workflow installer
4. Follow the prompts to install this workflow and enter the ilmnadmin password when directed.

The DRAGEN license will now be displayed.

\
\
\ <br>

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