This behavior is due to an error that occurred when the report was first created and saved, and the report configuration was somehow corrupted as a result.  You can resolve this issue by recreating your report with the same configuration.  Please note that copying the report will not work; you will need to create a new report from scratch.