Я использовал долгое время "новый EventArgs ()" вместо "EventArgs. Пустой"... Я думаю, что важное должно передать что-то, что не вызовет Пустую исключительную ситуацию.
Haven't used Crystal Reports for a bit, but generally an error along the lines of "LogOn Exception" may actually have nothing to do with security at all, Crystal Report errors can be a bit random.
Its possible it may be an error related to memory issues.
Or...
It might be report specific, a sub-report maybe trying to logon using credentials stored within the report, rather than the credentials you've passed into it via the code; You need to loop through all sub-reports rather than just the main report setting the login information.
I remember having this particular error when I used a workaround to install a dynamic logo for a report (that got pulled from a binary field within another database table) except there was a slight error in which it pulled the logo data for each row of data; After a certain amounts of rows returned it died resulting in a similar error.