I faced a similar problem but when I deployed that report, it worked without throwing

any exceptions or errors.

http://support.microsoft.com/kb/909678