1. Open the SharePoint management shell as an Administrator.
2. Run the command: $app=get-sprsserviceapplication –Name "xxxxxxxxxxxx"
3. 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:
4. 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>"
5. This should give you an output as shown below:
6. Do an IISRESET from a command prompt in admin mode.
7. Now render the Report with the command rc:Toolbar. The URL should resemble the following: https://xxxxx/_vti_bin/reportserver?https://xxxxx/Shared Documents/HelloWorld.rdl&rs:Command=Render&rc:ToolBar=False

1. Make sure that you've installed the ARR module on the machine which is hosting IIS.
2. Open the INETMGR and click on the Server name.
3. In the right hand side, you should see Application Request Routing. Double click to open it.
4. Under Actions tab in the right hand side, click on "Server Proxy Settings..."
5. Click on Enable proxy and close the INETMGR.
6. Open the "applicationHost.config" located under "C:\Windows\System32\inetsrv\config\"
7. Make sure you keep a back up of the file.
8. Search for the <rewrite> element within the file. That should be located underneath "<proxy enabled="true" />" element.
9. Replace the <rewrite> </rewrite> element with the following:

   <rewrite> <globalRules> <rule name="ARR_server_proxy_SSL" enabled="true" patternSyntax="Wildcard" stopProcessing="true"> <match url="*" /> <conditions> <add input="{HTTPS}" pattern="on" /> </conditions> <action type="Rewrite" url="https://xxxxxxxxxxxx/{R:0}" /> <serverVariables> <set name="HTTP_X_ORIGINAL_ACCEPT_ENCODING" value="{HTTP_ACCEPT_ENCODING}" /> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> <rule name="ARR_server_proxy" enabled="true" patternSyntax="Wildcard" stopProcessing="true"> <match url="*" /> <action type="Rewrite" url="https://xxxxxxxxxxxxx/{R:0}" /> <serverVariables> <set name="HTTP_X_ORIGINAL_ACCEPT_ENCODING" value="{HTTP_ACCEPT_ENCODING}" /> <set name="HTTP_ACCEPT_ENCODING" value="" /> </serverVariables> </rule> </globalRules> <outboundRules> <clear /> <rule name="handleCompression" preCondition="Encoding"> <match serverVariable="HTTP_ACCEPT_ENCODING" pattern="^(.*)" /> <conditions logicalGrouping="MatchAll" trackAllCaptures="true" /> <action type="Rewrite" value="{HTTP_X_ORIGINAL_ACCEPT_ENCODING}" /> </rule> <rule name="Outbound" preCondition="json" stopProcessing="true"> <match filterByTags="None" pattern="(.*)//xxxxxxxxxxxxx /(.*)" /> <conditions logicalGrouping="MatchAll" trackAllCaptures="true"> </conditions> <action type="Rewrite" value="{R:1}//xxxxxxxxxxxxx /{R:2}" /> </rule> <preConditions> <preCondition name="json"> <add input="{RESPONSE_CONTENT_TYPE}" pattern="application/json.*" /> </preCondition> <preCondition name="Encoding"> <add input="{HTTP_X_ORIGINAL_ACCEPT_ENCODING}" pattern=".*" /> <add input="{RESPONSE_CONTENT_TYPE}" pattern="application/json.*" /> </preCondition> </preConditions> </outboundRules> <allowedServerVariables> <add name="HTTP_ACCEPT_ENCODING" /> <add name="HTTP_X_ORIGINAL_ACCEPT_ENCODING" /> </allowedServerVariables> </rewrite>

10. Do ensure that the hostname values are changed to the appropriate server URL that hosts Reporting services under the Global rules as shown below: <rule name="ARR_server_proxy_SSL" enabled="true" patternSyntax="Wildcard" stopProcessing="true"> <match url="*" /> <conditions> <add input="{HTTPS}" pattern="on" /> </conditions> <action type="Rewrite" url="https://SSRS Server name from URL /{R:0}" /> <rule name="ARR_server_proxy" enabled="true" patternSyntax="Wildcard" stopProcessing="true"> <match url="*" /> <action type="Rewrite" url="https://SSRS Server name from URL /{R:0}" />
11. . 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}" />
12. Restart IIS using the command IISRESET.

1. The Last Run column was supposed to only show the value when the report is based on execution snapshots.
2. The column will be blank if the report is set for execution anything other than the option mentioned in #1.
3. We acknowledged that it was not showing the data even though the report was set for Execution snapshots and issue was fixed in both SSRS 2012 and SSRS 2014. FIX: The date value in the Last Run column is blank in Report Manager Details View in SSRS 2012 or SSRS 2014
4. Last but not the least, this Last Run column is available in Report Manager details view only till Reporting Services 2014 and not above that.

1. Multi line tool bar
2. Print button not visible.
3. Page getting stuck with just Loading message.
4. 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.

2. Upgrade to SSRS 2012 SP 1 CU 8.

More details on this can be found on my other blog.

More details about browser compatibility can be found here.

HTH!

Selva.

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

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]