SSRS 2012 -Invalid URI: The Uri string is too long - by MS UEIT

Status : 

 


17
0
Sign in
to vote
ID 788964 Comments
Status Active Workarounds
Type Bug Repros 10
Opened 5/30/2013 8:10:57 AM
Access Restriction Public

Description

Hello,

We are migrating SSRS 2008 R2 reports to SSRS 2012. And able to successfully migrate to SSRS 2012.

Everything went smooth expect some reports which were using reporting services. These reports are calling the reporting service webservice and was passing in a huge xml parameter. This XML parameter would work fine for smaller string lengths but failed for larger strings and the error reported is "Invalid URI: The Uri string is too long"

Went through many discussions and could not find any solution.

Observed that, if we pass the XML data upto 65520 characters, then the report works fine and anything greater than 65520 characters it throws an Error

We would like to see...if there is any solution or alternate solution for this issue.
Sign in to post a comment.
Posted by bahushekh on 8/10/2016 at 2:08 AM
This is an active issue and facing in SSRS 2014 also. When contacted to Microsoft they said its because Denial of Services attack security reason.
http://ppalakollu.blogspot.in/2012/06/sql-server-2012-reporting-services.html
Posted by Kalidoss on 6/13/2016 at 9:20 PM
Hi,

Can anyone please post updates on this issue. We are facing this issue even after upgrading to SQL Server 2012 SP2

Regards,
M, Kalidoss
Posted by Kalidoss on 1/21/2016 at 11:05 PM
We are facing the same issue with SQL Server 2012 SP2, I hope SP2 should be included with Cumulative Update 8 for SQL Server 2012 SP1.
Is this a known issue in SQL Server 2012 SP2?

Any fix or workaround is available for this issue.
Posted by Paul Abrams on 8/18/2015 at 10:06 AM
We are upgrading SSRS reports from Sql Server 2008 R2 to Sql Server 2014 and experiencing the same issue described above. We are testing our reports with identical data in the two environments, and in the SQl Server 2014 environment we receive "(rsInvalidParameter).Invalid URI: The Uri string is too long. ". For the same parameters in the SQL Server 2008 R2 environment we do not receive this error. Here is the output from Select @@Server on our target environment:
Microsoft SQL Server 2014 - 12.0.4416.0 (X64)
    Jun 11 2015 19:18:41
    Copyright (c) Microsoft Corporation
    Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
Posted by bahushekh on 6/9/2015 at 8:59 PM
https://support.microsoft.com/en-us/kb/2916827 its the article provided for the fix in SP1 but I dont think its available in SP2.
Is there any workaround if anyone found?
Posted by bahushekh on 6/8/2015 at 8:46 PM
No success even after installing SP2
Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
Posted by Alexander C Rees on 5/28/2015 at 2:35 AM
We're getting this in SQL Server 2014 as well. Really frustrating as it's not the kind of thing that has any easy workarounds...
Posted by Ana Lucero on 4/21/2015 at 2:30 PM
Hello!
I have this issue with SSRS SQL2012 SP2, Do I need to uninstall SP2 and just install SP1 + CU8? or are you planning to include it in any CU for SP2?

thx!
Posted by Ramya B S on 2/23/2015 at 2:20 AM
The same issue happening in sql server 2014 developer edition also .Is there any work around for this.
Posted by Rajeev Shukla on 2/8/2015 at 8:07 PM
After applying SQL Server SP2, still facing the same issue.
Posted by donsjones on 7/31/2014 at 11:30 AM
We upgraded from SQL Server 2008 R2 to SQL Server 2012 SP2 and encountered the same issue. We are running on Windows Server 2008 R2 SP1 within a VMware VM.

Once the SQL Server 2012 SP2 didn't work out, we applied CU1 for SQL Server 2012 SP2, and still same result.

We uninstalled CU1 and SP2 for SQL Server 2012. At the base version of SQL Server 2012, we still had the same issue. Applied SP1 and CU1-8 to see if anything fixes the issue. Nothing worked. We are still having issues.

We are in the process of uninstalling SQL Server, and will try to install a fresh copy of SQL Server 2012 with SP2 to see if everything works.

Right now, we are in the early stages of moving to SQL Server 2012. Goal is to upgrade SQL Server 2005 SP4 and SQL Server 2008 R2 SP2 to SQL Server 2012 SP2 by the end of the year.


Posted by Microsoft on 5/14/2014 at 3:24 PM
Hello,

Thank you for submitting this feedback. As Faruk mentioned, we have fixed this issue. If anyone is still hitting this issue after applying this update, please post on this thread.

Thanks,
Matt Jones
SSRS Tiger Dev Team
Posted by Faruk Celik on 3/11/2014 at 2:09 AM
This issue is fixed with Cumulative Update #8 for SQL Server 2012 Service Pack1. You can obtain CU#8 for SQL Server 2012 SP1 from http://support.microsoft.com/kb/2917531
Posted by wstrasse on 8/9/2013 at 11:34 AM
The same error appears on our SQL 2012 machine:
library!ReportServer_0-4!aec!08/09/2013-11:23:18:: 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 ---;

We tried to modify the web.config with the following parameters without success:

<httpRuntime executionTimeout="9000" maxRequestLength="1024000"/>

<appSettings>
<add key="aspnet:MaxHttpCollectionKeys" value="100000000" />
<add key="aspnet:IgnoreFormActionAttribute" value="true" />
</appSettings>