# Error con modulo reporting **URL:** \ **Category:** General Discussion\ **Tags:** ignition80\ **Created:** [June 30, 2022, 6:09pm UTC](https://forum.inductiveautomation.com/t/error-con-modulo-reporting/61407 "2022-06-30T18:09:56Z")\ **Posts on this page:** 1\ **Showing post:** 6
**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:** [July 1, 2022, 1:00pm UTC](https://forum.inductiveautomation.com/t/error-con-modulo-reporting/61407/6 "2022-07-01T13:00:59Z")
Please post the whole error text (as text, not a screenshot). After pasting into the forum, highlight all of that text and click the "Preformatted text" button in the editor. That will make the pasted error easy to read. It does look like a bug, though. Consider upgrading your SQL Server JDBC driver. Ignition major version upgrades (like 8.0 =\> 8.1) are only free if your support contract with IA is up to date for your server's license. Otherwise you must pay a re-instatement fee. See also this discussion of IA's Long-Term-Supported version policies: > [@GIT - best practice](https://forum.inductiveautomation.com/t/git-best-practice/58732/9): > > This graphic from 2019 shows the expected support lifetime of v8.0. (Very short. I don’t recall the source article for that image, but it was widely discussed on this forum.) This blog post from last year explains the extension of v7.9’s active support phase to this June due to the length of time between v7.9’s release and v8.1: A similar effect will happen when v8.2 comes out. It will be glorious–new features galore, enabled by architecture changes that would be too disruptive to intro… --- _[View the full topic](https://forum.inductiveautomation.com/t/error-con-modulo-reporting/61407)._