Hi everyone,
i have a short status update for you regarding the problems with the reporting mentioned here, here and here (and maybe a few other places, where i marked them as DUPE):
The update to version 8.163 failed to create a database index, which was mostly unrecognized, because the departmental reporting wasn't yet activated. A later update then stumbled over this missing index and thus didn't apply a needed schema update. This bug was then shadowed by the reporter-related problems in 8.164, otherwise we would have seen this behavior much earlier.
As a result, data is written into the wrong database columns, which in turn leads to all kinds of strange results and follow-up errors.
Thanks to your valuable feedback, we've been able to find and fix this issue quickly, so it won't happen if you update a V8.1 to V8.2 later this year, but the bad news is that if you are affected by this problem, your only chance to get a working reporting again, is to re-install a fresh 8.165 (or later) version. While we were able to fix the bug, we cannot move the data that has been written into the wrong columns to the right place, simply because there's no reliable way to find the affected columns automatically.
I know that many of you really love their charts, but the only way to get the reporting working again is to drop the bad data.
Sorry for that.
Let me state this again:
This bug is solely related to the 8.163 up2date and thus only happens if you have updated your ASG along the way through this beta.
It doesn't occur on freshly installed 8.165 machines.
If you have question, please feel free to ask.
Cheers,
Kai