> 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/microarray/general/microarray-general-troubleshooting-list/000003031.md).

# How to Troubleshoot the GenomeStudio Genotyping Error "Error - writing data beyond end of sample"

#### **Description of Error**

During the final step of creating a GenomeStudio Genotyping project, a pop-up window may appear displaying the error message: "Error - writing data beyond end of sample" (Figure 1).

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-b443835d3187c165b31e063946d715ef8cdeffcf%2Fimage1.png?alt=media)

**Figure 1.** Pop-up window in GenomeStudio displaying the error message: "Error - writing data beyond end of sample."

The error is followed by a second pop-up window displaying the message: "The Project can not be created. No valid samples were loaded." (Figure 2). As a result, GenomeStudio is unable to create a project.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-3224854cf4492c28d5dab15b46f24745eef597a3%2Fimage2.png?alt=media)

**Figure 2.** GenomeStudio pop-up window displaying the error: "The Project can not be created. No valid samples were loaded."

####

#### **Resolution**

* This error can occur when both IDAT (intensity data files) and GTC (genotyping call files) files are located in the same repository folder.
* To resolve the issue, move the GTC files to a separate folder, ensuring that only the IDATs remain in the scan folder.
* When recreating the project, GenomeStudio should be able to access only a single source file type (IDAT files).

**Reference:**

* [Can Genotype Call (GTC) files be used as input for GenomeStudio?](https://knowledge.illumina.com/microarray/general/microarray-general-reference_material-list/000005917.md)

\
\
\ <br>

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