Resolving The Problem

The error usually indicates a formal error in XML or a tag being used that is unknown to the version that is used. Ie. in 10.2.2 a reportname tag was introduced which is unknown to previous versions.
If you know the latest changes, revert them back and verify if the error goes away.

Steps:

1. Get the report specification in Report Studio by clicking Tools->Copy report to clipboard, then pasting into a text editor. Make sure line wrapping is not enabled so the line numbers will be correct
2. Move to the specified line and column numbers to find out what the offending element is.
3. Fix the problem element, if possible
4. Copy the entire report specification and then in Report Studio: Tools->Open report from clipboard, to use the updated report specs.

Troubleshooting

Usually the detailed message after the RSV-SRV-0003 message can help solve the problem.

E.g. RSV-SRV-0003 The report specification contains an error at line '<line>', column '<col>'.
Detailed message: "Datatype error: Type:InvalidDatatypeFacetException, Message: Value '0' must be greater than or equal to MinInclusive '1'."

Looking at the report specs at line <line> and column <col>, the problem tag was:
<pageset ... resetPageCount="0">

The gist of the message indicates that "Value '0' must be...greater than or equal to ... '1'".

Changing the resetPageCount="0" to resetPageCount="1" resolved the issue. An alternative would have been to change the Pagination property of the Page Set from 0 to 1 in Report Studio.

If you cannot find any obvious errors, save the reportspecification as *.xml and open in a browser, to verify the correctness of the xml format (ie. number of closing tags matches number of open tags).

Note:
The above solution only works when the error message refers to the full report specification. This error message has also been seen on "sub-reports" - for instance, viewing Tabular Data. The report server generates its own report specs for these. This means that you will not have access to these specs, so the above troubleshooting method will not work.