Our team went through this a couple of months ago. After trying multiple options that failed it seemed that it had something to do with the select option of the query using Powershell scripting combined with calling the CR report.
By chance, we decided to take the query and stuff it into a stored procedure and make a call to that in the report and it worked!!!!
