URL length affecting SSRS 2008 R2 in URL Access mode
Hi, I am trying to migrate my SSRS report from 2005 SP3 to 2008 R2. In the process, I am facing an issue where one of my report which has 5 visible report parameters out of which one of the parameter is a multi-valued parameter and we are passing more than one value for that parameter. We use the URL Access mode to render the report in another .NET application. The URL looks like the following, http://localhost/reportserver_sql2008r2?/Client1/National Dashboards/abcd-efghij Brand Dashboard&CurrentMeasure=[Measures].[Value AUD NSA]&CurrentChannel=[Channel].[Channel].[All Channel]&SelectedProducts=[Market].[Market Hierarchy].[Submarket Level 1].%26[PROD1ONAZOLE]%26[abcd-efghij Market]%26[Speciality]&SelectedProducts=[Market].[Market Hierarchy].[Submarket Level 2].%26[PROD1 Tablets]%26[PROD1ONAZOLE]%26[abcd-efghij Market]%26[Speciality]&SelectedProducts=[Market].[Market Hierarchy].[Submarket Level 2].%26[PROD1 Oral Suspension]%26[PROD1ONAZOLE]%26[abcd-efghij Market]%26[Speciality]&SelectedProducts=[Market].[Market Hierarchy].[Submarket Level 2].%26[PROD1 IV]%26[PROD1ONAZOLE]%26[abcd-efghij Market]%26[Speciality]&SelectedProducts=[Market].[Market Hierarchy].[Submarket Level 1].%26[PROD1S]%26[abcd-efghij Market]%26[Speciality]&CurrentPeriod=TAIL([Date].[Relative Month].Members,12)&CurrentProduct=[Market].[Market Hierarchy].[Submarket Level 1].%26[PROD1ONAZOLE]%26[abcd-efghij Market]%26[Speciality]&rc:Toolbar=false&rs:Command=Render&rs:Format=HTML4.0 In the above URL, we have 5 products selected for the SelectedProducts parameter and it fails to load the report in the browser (I have tried IE 8). However, when we try the same URL on the server that has SSRS 2005 SP3, it renders the report correctly in the browser. Also, when I reduce the number of products selected in the URL from 5 to 4, it manages to render the report correctly even on the server that has SSRS 2008 R2. Within the application that makes the actual web request to reporting services (the url is the same as above), the request fails after the 'requesttimeout' period with 'no response' from the server. Initially our suspicion was that the request length was the issue and tried to override the maxrequestlength and similar properties on the configuration files but with no luck. Even turning on failed request tracing in IIS did not help. We also noticed that in the Reporting services HTTP log, the request seems to arrive (so one entry shows up as soon as the request is made), but nothing happens afterwards and the requesting application, be it the browser or the web application, times out and fails. Thanks in advance for your help.
February 15th, 2011 12:50pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics