The one stop shop for FIXING your Reporting Service's Issueshttps://blogs.msdn.microsoft.com/selvar
Here you can find most of the details regarding the reporting service troubleshooting on different scenarios.Sat, 22 Jul 2017 06:37:31 +0000en-UShourly1Rendering a large report in SharePoint mode fails with maximum message size quota exceeded error messagehttps://blogs.msdn.microsoft.com/selvar/2017/07/22/rendering-a-large-report-in-sharepoint-mode-fails-with-maximum-message-size-quota-exceeded-error-message/
https://blogs.msdn.microsoft.com/selvar/2017/07/22/rendering-a-large-report-in-sharepoint-mode-fails-with-maximum-message-size-quota-exceeded-error-message/#respondSat, 22 Jul 2017 06:37:09 +0000https://blogs.msdn.microsoft.com/selvar/?p=1205Recently, i was working on a scenario where reporting services 2012 was configured in SharePoint 2013 integrated mode. We were exporting a report that was ~240MB in size. When we do that, the reports fails with the following exception:

8. Remember, the steps #2 thro' #7 has to be done on all the machines identified in step #1.

9. Secondly, you need to go to each of the SharePoint WFE server including the app servers (that hosts Reporting services which was identified on step #1) and locate client.config file from the following location:

15. Remember, the steps #9 thro' #14 has to be done on all the WFE machines as well as the app servers (that hosts Reporting services which was identified on step #1).

Now the large report that you are trying to export should come up fine as expected be it from within SharePoint or from any custom application.

This article applies to all the reporting services version from SSRS 2012 thro' SSRS 2016 and for SharePoint 2010 thro' SharePoint 2016. The path referenced in steps #2 and #9 varies between 14 / 15 / 16 according to the SharePoint versions 2010 / 2013 / 2016 respectively.

Hope this helps!

Selva.

[All posts are AS-IS with no warranty and support]

]]>https://blogs.msdn.microsoft.com/selvar/2017/07/22/rendering-a-large-report-in-sharepoint-mode-fails-with-maximum-message-size-quota-exceeded-error-message/feed/0URL access with rc:Toolbar command fails with rsRenderingExtensionNotFoundhttps://blogs.msdn.microsoft.com/selvar/2017/07/01/url-access-with-rctoolbar-command-fails-with-rsrenderingextensionnotfound/
https://blogs.msdn.microsoft.com/selvar/2017/07/01/url-access-with-rctoolbar-command-fails-with-rsrenderingextensionnotfound/#respondSat, 01 Jul 2017 11:11:00 +0000https://blogs.msdn.microsoft.com/selvar/?p=1175Recently i was working on a scenario where Reporting Services 2016 is configured for SharePoint (Applicable to both 2013 and 2016) integrated mode. Now, when you use URL access with the rc:Toolbar command, the reports would fail with the following error:

You have attempted to use a rendering extension that is either not registered for this report server or it is not supported in this edition of Reporting Services. (rsRenderingExtensionNotFound)

Upon further investigation, we found that when we use rc:Toolbar command, Reporting Services would attempt to render the report explicitly in HTML5 format as opposed to RPL format. The HTML5 rendering extension should have been configured by default. Since it was not, we've to manually do that as shown below. The possible reason could be the integration was done with SharePoint 2013 instance that has been upgraded to SharePoint 2016.

Open the SharePoint management shell as an Administrator.

Run the command: $app=get-sprsserviceapplication –Name "xxxxxxxxxxxx"

Note that the name to use in the above step could be taken from SharePoint central admin -> Manage service application under Application management and look for "SQL Server Reporting Services Service Application" as shown below:

Followed by the command in #2, run the following command:
New-SPRSExtension -identity $app -ExtensionType "Render" -name "HTML5" -TypeName "Microsoft.ReportingServices.Rendering.HtmlRenderer.Html5RenderingExtension,Microsoft.ReportingServices.HtmlRendering" -ExtensionConfiguration "<DeviceInfo><DataVisualizationFitSizing>Approximate</DataVisualizationFitSizing></DeviceInfo>"

This should give you an output as shown below:

Do an IISRESET from a command prompt in admin mode.

Now render the Report with the command rc:Toolbar. The URL should resemble the following:
http://xxxxx/_vti_bin/reportserver?http://xxxxx/Shared Documents/HelloWorld.rdl&rs:Command=Render&rc:ToolBar=False

That should ensure that the reporting services 2016 in SharePoint mode is now capable of using the rs:Toolbar command. Do that this issue would not surface when you're using the URL against the Reporting Services 2016 in Native mode.

If you would like to remove this extension or any other extension in the future, use the following command preceded by #2:

]]>https://blogs.msdn.microsoft.com/selvar/2017/07/01/url-access-with-rctoolbar-command-fails-with-rsrenderingextensionnotfound/feed/0Configuring Reporting Services 2016 with ARRhttps://blogs.msdn.microsoft.com/selvar/2017/07/01/configuring-reporting-services-2016-with-arr/
https://blogs.msdn.microsoft.com/selvar/2017/07/01/configuring-reporting-services-2016-with-arr/#respondSat, 01 Jul 2017 07:27:26 +0000https://blogs.msdn.microsoft.com/selvar/?p=1135Recently, i was working on a deployment where we need to configure SQL Server Reporting Services 2016 with ARR so that reporting services is exposed over the internet without exposing the machine itself. If you are looking for such implementations, then this guide is for you. Please do note that I've tested this against Reporting Services 2016. But this should be fairly the same for prior versions or Reporting Services 2017 as well.

Make sure that you've installed the ARR module on the machine which is hosting IIS.

Open the INETMGR and click on the Server name.

In the right hand side, you should see Application Request Routing. Double click to open it.

Under Actions tab in the right hand side, click on "Server Proxy Settings..."

Click on Enable proxy and close the INETMGR.

Open the "applicationHost.config" located under "C:\Windows\System32\inetsrv\config\"

Make sure you keep a back up of the file.

Search for the <rewrite> element within the file. That should be located underneath "<proxy enabled="true" />" element.

. Under the Outbound rules, replace the pattern with the Report server URL name and the rewrite action with the ARR server URL name as shown below:

pattern="(.*)// SSRS Server name from URL/(.*)"

<action type="Rewrite" value="{R:1}//ARR Server URL name/{R:2}" />

Restart IIS using the command IISRESET.

Do note that this rule is written for both HTTP as well as HTTPS. So, if you use either one of them, it should continue to work. The authentication that we enabled for ARR server was Anonymous and for Reporting Services we used Basic authentication (RSWindowsBasic).

Hope this helps!

Selva.

[All posts are AS-IS with no warranty and support]

]]>https://blogs.msdn.microsoft.com/selvar/2017/07/01/configuring-reporting-services-2016-with-arr/feed/0Demystifying Last Run column in Report Manager Details Viewhttps://blogs.msdn.microsoft.com/selvar/2017/02/04/demystifying-last-run-column-in-report-manager-details-view/
https://blogs.msdn.microsoft.com/selvar/2017/02/04/demystifying-last-run-column-in-report-manager-details-view/#respondSat, 04 Feb 2017 10:53:41 +0000https://blogs.msdn.microsoft.com/selvar/?p=1115We often see our reporting services users asking us the question why the "Last Run" column in Report Manager details view is blank. This post would help you to get the necessary clarification on the behavior.

The Last Run column was supposed to only show the value when the report is based on execution snapshots.

The column will be blank if the report is set for execution anything other than the option mentioned in #1.

]]>https://blogs.msdn.microsoft.com/selvar/2017/02/04/demystifying-last-run-column-in-report-manager-details-view/feed/0Reporting services support for Microsoft EDGE browserhttps://blogs.msdn.microsoft.com/selvar/2017/01/12/reporting-services-support-for-microsoft-edge-browser/
https://blogs.msdn.microsoft.com/selvar/2017/01/12/reporting-services-support-for-microsoft-edge-browser/#respondThu, 12 Jan 2017 09:31:18 +0000https://blogs.msdn.microsoft.com/selvar/?p=1095EDGE is the latest browser released by Microsoft along with Windows 10. There are so much of questions around the supportability of SSRS with Microsoft EDGE browser.

Please do go through the above blog post for usage and supportability of the same.

HTH!

Selva.

[All the posts are AS-IS with no warranty]

]]>https://blogs.msdn.microsoft.com/selvar/2017/01/12/reporting-services-support-for-microsoft-edge-browser/feed/0Intermittent E_ACCESSDENIED when opening SSRS related contentshttps://blogs.msdn.microsoft.com/selvar/2017/01/12/intermittent-e_accessdenied-when-opening-ssrs-related-contents/
https://blogs.msdn.microsoft.com/selvar/2017/01/12/intermittent-e_accessdenied-when-opening-ssrs-related-contents/#respondThu, 12 Jan 2017 09:20:19 +0000https://blogs.msdn.microsoft.com/selvar/?p=1076Have you ever wondered why does your Reporting Services behave in a weird way when you either try to access report manager page or open a report or open a shared data source etc. by throwing errors like: (You'll find these errors either in the page itself on in the Reporting Services log files located under your installation directory)

library!ReportServer_0-2!e8c8!01/06/2017-13:06:22:: Call to GetSystemPropertiesAction().
ui!ReportManager_0-1!f8c0!01/06/2017-13:06:22:: e ERROR: System.IO.FileLoadException: Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of its dependencies. Access is denied.
File name: 'System.EnterpriseServices.Wrapper.dll' ---> System.IO.FileLoadException: Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of its dependencies. Access is denied.
File name: 'System.EnterpriseServices.Wrapper.dll' ---> System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

We believe that one of our patches https://support.microsoft.com/en-us/kb/3045999 has caused this issue. This has to do with CLR functionality where underlying file access is fails randomly with UnAuthorized exception causing issues.

To fix this issue, please follow the workaround:

1) Add a Key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options and name it “ReportingServicesService.exe”

2) Add a DWord named “UseImpersonatedDeviceMap” with a value of 1

3) Reboot the box

The registry key UseImpersonatedDeviceMapis set if an application is allowed to call Kernel services with Impersonation. If the key doesn't exist (by default), then it is forbidden.

HTH!

Selva.

[All the posts are AS-IS without any warranty]

]]>https://blogs.msdn.microsoft.com/selvar/2017/01/12/intermittent-e_accessdenied-when-opening-ssrs-related-contents/feed/0IE 11 browser support for Reporting services versions prior to 2012https://blogs.msdn.microsoft.com/selvar/2015/01/21/ie-11-browser-support-for-reporting-services-versions-prior-to-2012/
https://blogs.msdn.microsoft.com/selvar/2015/01/21/ie-11-browser-support-for-reporting-services-versions-prior-to-2012/#commentsWed, 21 Jan 2015 01:29:00 +0000https://blogs.msdn.microsoft.com/selvar/2015/01/21/ie-11-browser-support-for-reporting-services-versions-prior-to-2012/I frequently come across customers who use IE 11 to view reports (From Report manager as well from applications using Report viewer controls) that are deployed on Reporting service version prior to 2012 and end up in facing unexpected viewing experiance right from:

Multi line tool bar

Print button not visible.

Page getting stuck with just Loading message.

Report formatting getting messed up.

And the list doesn't just stop here.

One thing you've to be aware of is that neither report viewer control nor the reporting services version prior to SQL server 2012 SP 1 CU 8 have the browser detection logic for IE 11.

What this means is, you do not have much of the options to help yourself here other than the following:

1. Add the reporting services / application URL under the IE compatibility setting so that the page will be rendered in compatibility mode and shows up just as expected. This is a setting which could be forced through group policy or could be done on the individual client machines.

]]>https://blogs.msdn.microsoft.com/selvar/2015/01/21/ie-11-browser-support-for-reporting-services-versions-prior-to-2012/feed/3Report exported to PDF causes all the spaces in between the words to be compressedhttps://blogs.msdn.microsoft.com/selvar/2014/09/10/report-exported-to-pdf-causes-all-the-spaces-in-between-the-words-to-be-compressed/
https://blogs.msdn.microsoft.com/selvar/2014/09/10/report-exported-to-pdf-causes-all-the-spaces-in-between-the-words-to-be-compressed/#respondWed, 10 Sep 2014 04:11:22 +0000https://blogs.msdn.microsoft.com/selvar/2014/09/10/report-exported-to-pdf-causes-all-the-spaces-in-between-the-words-to-be-compressed/Have you come across a similar situation when you’ve a report with textbox within or outside a tablix, containing an expression. When you view the report in browser everything looks great. The moment you export the report to PDF and open the same, to your disappointment you see the space in between the words are no more and the words are compressed. All the other formats show the report to be perfectly fine. This looks exactly like below:

In Browser:

In PDF:

If you carefully observe, the line one between the above two images differ. This is what I’m precisely talking about.

Now, do you know what causes this issue?

You check your source data and everything seems to be perfectly intact. Let me tell you what it is actually. There is a character called “Zero width space” which has the unicode representation of “U+200B”. The presence of this character is virtually un noticeable. Hence it appears everything seems to be fine at the source data view.

There are some issue WRT how we handle this character when it comes to PDF and hence this issue is a result of this.

How to get around this?

It is extremely simple. Just wrap your textbox expression with in the below expression and this will be take care off.

=Replace(Fields!Column.Value,ChrW(&h200B),"")

HTH!

Selva.

[All the posts are AS-IS with no warranty]

]]>https://blogs.msdn.microsoft.com/selvar/2014/09/10/report-exported-to-pdf-causes-all-the-spaces-in-between-the-words-to-be-compressed/feed/0Using Report Viewer control in ASPX pageshttps://blogs.msdn.microsoft.com/selvar/2014/09/05/using-report-viewer-control-in-aspx-pages/
https://blogs.msdn.microsoft.com/selvar/2014/09/05/using-report-viewer-control-in-aspx-pages/#commentsFri, 05 Sep 2014 00:36:00 +0000https://blogs.msdn.microsoft.com/selvar/2014/09/05/using-report-viewer-control-in-aspx-pages/If you’re developing a ASP.NET page and planning to use the Microsoft Report Viewer web control for showing reports that are deployed to SSRS prior to 2016, here is a word of recommendation for you.

Make sure the page that hosts the Report viewer control has the compatibility setting enabled as shown below:

Make sure to keep an eye on the DOCTYPE as well as I've posted it on the above sample.

The above blog post is not applicable for the newer version of the Report Viewer control i.e. Report Viewer 2016.

For Report viewer control against SSRS 2016, the newer version of the control (2016) is available here. This would help you to leverage all the newer updates within SSRS 2016 including the print functionality.

HTH!

Selva.

[All the posts are AS-IS without any warranty]

]]>https://blogs.msdn.microsoft.com/selvar/2014/09/05/using-report-viewer-control-in-aspx-pages/feed/2Performance improvement feature request for the Reporting Services in SharePoint modehttps://blogs.msdn.microsoft.com/selvar/2014/06/30/performance-improvement-feature-request-for-the-reporting-services-in-sharepoint-mode/
https://blogs.msdn.microsoft.com/selvar/2014/06/30/performance-improvement-feature-request-for-the-reporting-services-in-sharepoint-mode/#respondMon, 30 Jun 2014 02:17:49 +0000https://blogs.msdn.microsoft.com/selvar/2014/06/30/performance-improvement-feature-request-for-the-reporting-services-in-sharepoint-mode/If you are looking for features outlined in the connect site and would like to see this improved, please feel free to visit these links and vote for the feature as this will help Microsoft to prioritize these items.