Thanks!

It's a new bug.

It happens when the report contains a logical activity of "failed logon" where the  user is unknown.

You managed to generate the report by "missing" this specific activity using the filter.

I opened a bug to track it down for a  future version.

www.000webhost.com