There are not good error messages. What I think is happening is that when the ORM profiler is enabled, the report viewer does not pass any parameters to stored procedures. When it is disabled, the parameters are passed correctly. I reviewed the output of the ORM profiler and I see the call that is made to the stored procedure without any parameters.