# Unaccessible "Data Collection Errors" info (Reporting Module)

**URL:** <https://forum.inductiveautomation.com/t/unaccessible-data-collection-errors-info-reporting-module/37877>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [August 18, 2020, 7:15pm UTC](https://forum.inductiveautomation.com/t/unaccessible-data-collection-errors-info-reporting-module/37877 "2020-08-18T19:15:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mlopez48](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@mlopez48](https://forum.inductiveautomation.com/u/mlopez48)\
**Post date:** [August 18, 2020, 7:15pm UTC](https://forum.inductiveautomation.com/t/unaccessible-data-collection-errors-info-reporting-module/37877/1 "2020-08-18T19:15:08Z")

</div>

I’m using the reporting module and I can’t view the full “Data Collection Errors” message from the pop-up. In previous versions I could select the error message and Cmd+C/Cmd+V into a code editor to view the full message, but this seems to be disabled.

Additional details:  
Using Ignition Designer (Mac)  
Ignition 8.0.15

---

<div class="post-metadata">

**Author:** ![kaushik.shah](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@kaushik.shah](https://forum.inductiveautomation.com/u/kaushik.shah)\
**Post date:** [November 19, 2021, 2:39pm UTC](https://forum.inductiveautomation.com/t/unaccessible-data-collection-errors-info-reporting-module/37877/2 "2021-11-19T14:39:16Z")

</div>

Same thing. I am seeing data collection error but can’t see any information where is it coming from.  
Ignition 8.0.17

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 19, 2021, 2:43pm UTC](https://forum.inductiveautomation.com/t/unaccessible-data-collection-errors-info-reporting-module/37877/3 "2021-11-19T14:43:34Z")

</div>

Y’all do know that 8.0.x is an already-expired non-LTS series? Even if this is a bug, it will not be fixed. Upgrade to the current 8.1.x and see if this behavior is still present.
