In my case with the same error message, the root of the issue is not from the security perspective, but from the database view related to the report. Here's how I found out:
Run the same report from Report Builder: from Report Manager, click the report that produces error. You might have to provide additional parameters depending on your report, then click View Report
You should now see the same error message. The content of the message is the same in the first sentence; but the second sentence on it will show in more detail the cause of the error. In my case I have a view that queries columns not existing (because I deleted) in the table. When I update the view, it works again with the report.