I've never seen this error when using a stored procedure. I've never had an issue with the no rows message not being used when a stored procedure doesn't return data.

Does the report work when the stored procedure does return data?

Can you run a trace when you run the report with a parameter combination does not return data and see what is happening on the SQL Server?

What happens when you run the stored procedure directly with the parameter combination that doesn't return data?