Recently, we upgraded our 2008 R2 reporting services instance to 2012. The upgrade itself went smooth. There were no errors reported. But after the upgrade, one of our reports started failing intermittently. Below is the error: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: Internal error, Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. ---> System.UriFormatException: Invalid URI: The Uri string is too long. at System.Uri.EscapeString(String input, Int32 start, Int32 end, Char[] dest, Int32& destPos, Boolean isUriString, Char force1, Char force2, Char rsvd) at System.Uri.EscapeDataString(String stringToEscape) at Microsoft.ReportingServices.Common.UrlUtil.UrlEncode(String input) at Microsoft.ReportingServices.ReportProcessing.ParameterInfoCollection.UrlEncodeSingleParam(StringBuilder url, String name, Object val, Func`2 cs) at Microsoft.ReportingServices.ReportProcessing.ParameterInfoCollection.ToUrl(Boolean skipInternalParameters, Func`2 cs) at Microsoft.ReportingServices.Library.ReportExecutionBase.WriteParametersToJobContext(RunningJobContext jobContext) at Microsoft.ReportingServices.Library.ReportExecutionBase.Execute() at Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper() --- End of inner exception stack trace ---; Looks like the error is: Invalid URI: The Uri string is too long. If the parameters are not really long, then it works. Otherwise it crashes the whole reporting services component. Anyone else had the same issue ? All of our other reports seem to work fine.

Is this specific to one of the reports or all the reports are failing with the same error. If this is specific to a report, then do the following: Reproduce the issue, and look for errors on Reporting Services Log files. For more information see, http://technet.microsoft.com/en-us/library/ms157403.aspxCan you export the report rdl from your report manager, and check if you are able to run the report from within the Report Designer? Also, suggest you to refer the detailed documentation for upgrading to reporting services 2012: http://technet.microsoft.com/en-us/library/ms143747.aspx. ThanksChaitanya( Twitter | Blogs ) Any documentation bug? Tell us about it at Connect. Please feel free to add any community comments in any of the MSDN/technet articles. This posting is provided "AS IS" with no warranties, and confers no rights.

How did you upgrade? Open a new project in SSDT and add upgraded report to the project, now ,deploy it and it should be working .Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/

Thanks for replying. The above error message is from the reporting services logs. The error is restricted to usage of a particular parameter's length. When this parameter is long, the reporting services crashes. It can be reproduced using the designer also. We did an in-place upgrade on the database to 2012. We tried creating a new project and redeploying it but the same error message.

Can you create a sample proj and use connect.microsoft.com to file a defect? That can really help us research around the isuse and narrow down what the problem is. ThanksChaitanya( Twitter | Blogs ) Any documentation bug? Tell us about it at Connect. Please feel free to add any community comments in any of the MSDN/technet articles. This posting is provided "AS IS" with no warranties, and confers no rights.