We experience the same issue off and on. Usually renaming the store procedure that the report is running fixes the issue. However, it's really annoying and would like to know what the cause is.