This content has been marked as final. Show 2 replies
I've not seen this issue before, could you contact your local support for further investigation?
I had this error when data range set in trend configuration was not covered by data collected by MI service (when just configured trend gadget before MI service was starded, or after that - when date range was to wide). After first run of MI service, and data range set correctly - trend gadget works fine.