> 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/000006513.md).
# Troubleshooting the Error "Could not launch selected viewing application" in BeadArray Controls Repo
The BeadArray Controls Reporter (BACR) software is used to analyze sample control metrics for Illumina Methylation Arrays. After analysis, the software generates an Excel file containing summary values for each control and sample within a project.
This article describes a known issue in which BACR displays a **"Could not launch selected viewing application"** error after analysis is complete and provides a workaround.
####
**Error**
After BACR completes an analysis, the **View Output** dialog box appears and asks:
*Would you like to view the output?*
**Figure 1.** View Output prompt after analysis is complete.
If **Yes** is selected, BACR may display the following error message:
**Could not launch selected viewing application**
**Figure 2.** Error message displayed when BACR is unable to open the output file automatically.
**Cause**
This error occurs when BACR is unable to automatically launch the output file using newer version of Excel (for example, Excel Office 365).
BACR was released in 2015 and was originally designed for systems running Windows XP with Microsoft Excel 2007. As a result, the automatic file-opening function may not be compatible with current versions of Excel.
####
#### **Resolution**
Although the error message is displayed, BACR still generates the output file successfully.
To access the results:
1. Navigate to the BACR output folder.
2. Locate the generated Excel output file.
3. Open the file manually using Microsoft Excel.
This workaround allows the analysis results to be viewed despite the application launch error.
**References:**
* [BeadArray Controls Reporter Software Guide](https://support.illumina.com/downloads/beadarray-controls-reporter-software-guide-1000000004009.html)
* [BeadArray Controls Reporter v1.1 Installer and Release Notes](https://support.illumina.com/downloads/beadarray-controls-reporter-installer.html)
\
\
\
| |
| :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #6513), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000006513%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 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/microarray/general/microarray-general-troubleshooting-list/000006513.md?ask=&goal=
```
`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.