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

# How to resolve an error occurred while populating NextSeq 1000/2000 data in SAV

**Background**: Sequencing Analysis Viewer (SAV) is a software application that enables viewing of quality metrics generated by the Real-Time Analysis (RTA) software on Illumina sequencing systems. The NextSeq 1000/2000 Control Software release v1.5 requires SAV version 2.5.12 or later to view run metrics. If visualizing data generated from NextSeq 1000/2000 Control Software version 1.5 in SAV version 2.4 user will encounter an error indicating inability to parse various InterOp folder files.

SAV v2.5.12 is compatible with runs generated in the newer NextSeq 1000/2000 Control Software (v1.7.1) for Standard reagents only. If running XLEAP kits, it will show the same errors.

Examples of error language include:

* An error occurred while populating the data: No format found to parse ErrorMetricsOut.bin with version 6 of 3
* An error occurred while populating the data: No format found to parse BasecallingMetricsOut.bin with version 5 of 3

  ![](/files/zYgt32MwM2A8aF5BSWnn)

**Troubleshooting**:

* If on SAV v2.4: Update SAV to v2.5.12 - SAV download can be found on the [NextSeq 1000/2000 Software Downloads](https://support.illumina.com/sequencing/sequencing_instruments/nextseq-1000-2000/downloads.html) page.
* If on SAV v2.5.12 trying to analyze XLEAP runs: Update SAV to v3.0 **or** move the "BasecallingMetricsOut.bin" and the "RegistrationMetricsOut.bin" files from the InterOp folder to another folder (we don't recommend deleting those as they might be necessary in case of troubleshooting).

\
\
\ <br>

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