How to set up Silverlight Viewer for Reporting Services on the production server

 The deployment process usually consists of three following steps:

1) WCF service and client application deployment
2) XAML rendering extensions installation on Reporting Services server
3) License installation

Usually, WCF service resides inside deployed client application. Alternatively, you can create a separate application to host a WCF service so it can be deployed exclusively. For more information regarding hosting a WCF service please refer to http://msdn.microsoft.com/en-us/library/bb332338.aspx

WCF service and client application deployment

There's nothing specific when deploying the client app on prod server, except for specifying the correct WCF service url that would be used. This is the scenario when WCF service is deployed inside client app. In case the WCF service is self-hosted, you should pay attention to cross-domain environment that can affect the service requests. Usually, it is solved by placing the clienacesspolicy.xml and crossdomain.xml files configured to allow the cross-domain requests inside the root folder of WCF service host. But, in some cases, other issues may also need to be resolved. Please refer to the following article for your reference ( http://social.msdn.microsoft.com/Forums/silverlight/en-US/0c13492d-92a4-4a69-b3f7-a5b93a8b26b7/silverlight-wcf-crossdomain-issue?forum=silverlightnet).
Also, you should pay attention to the SSRS server URL specified in web.config file of your app, as it has to be valid and the credentials specified should also be correct.

XAML rendering extensions installation on Reporting Services server

After the product is installed on a client PC, the rendering extensions installer can be found in product installation folder. This installer is then copied to a SSRS server box where the installation takes place. The extensions are usually installed automatically to SSRS folder and the required adjustment of two SSRS configuration files (rsreportserver.config and rssrvpolicy.config) is also automatically performed during the installation process.


In order to avoid any issues with XAML rendering extensions, the following steps should be performed after the extensions have been installed on a server. Namely, you should check whether the extensions have been installed correctly. Otherwise, in case something went wrong during the installation process, the manual installation and configuration would be required.


1) Make sure the following files are present in SSRS \bin folder ( the usual path is C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\bin)

PerpetuumSoft.ReportingServices.Viewer.ExtensionLink.dll
PerpetuumSoft.ReportingServices.XamlRendering.dll
PerpetuumSoft.ReportingServices.XamlRendering.R2.dll

2) Check the files' version. It should be the same as the client libraries version.

For example,

if PerpetuumSoft.ReportingServices.Viewer.Server.dll and PerpetuumSoft.ReportingServices.Viewer.Client.dll in your app project has 3.1.0.21 version, then the XAML rendering extension libraries should be the same 3.1.0.21 version.

3) Check whether the following lines are present in two SSRS configuration files.

To be exact,

in rsreportserver.config the <Render> section should contain the XAML definition as shown below:

<Render>
..........

<Extension Name="XAML" Type="PerpetuumSoft.ReportingServices.XamlRendering.XamlRenderer,PerpetuumSoft.ReportingServices.XamlRendering" Visible="false"/>

</Render>


and rssrvpolicy.config should containg the two following CodeGroup definitions:

<CodeGroup class="UnionCodeGroup" version="1" Name="PerpetuumSoftExtensionGodeGroup" Description="" PermissionSetName="FullTrust">
<IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\bin\PerpetuumSoft.ReportingServices.XamlRendering.dll" />
</CodeGroup>

<CodeGroup class="UnionCodeGroup" version="1" Name="PerpetuumSoftExtensionGodeGroup" Description="" PermissionSetName="FullTrust">
<IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\bin\PerpetuumSoft.ReportingServices.XamlRendering.R2.dll" />
</CodeGroup>

In case the version of the XAML libraries used on SSRS side differ from that of the client app, specific errors may occur. The versions used on both client/server sides should match.

Please check the attached sample videos displaying the correct XAML extensions installation procedure and our test sample project IIS deployment procedure.

http://perpetuumsoft.com/Support/special/videos.zip

Also, the screenshots regarding the SSRS URL availability check are under the link below:

http://perpetuumsoft.com/Support/special/SSRS_screenshots.zip


License installation

To be able to use the Silverlight Viewer for Reporting Services successfully, installation of the valid license is required. After the initial installation, the product works in a 30-day trial mode, and after the 30-day period is over the license installation should be done to continue using the product.

To download the license after the product was purchased, a user should log in to http://perpetuumsoft.com web site and proceed to the downloads section of the user account. The link to download the license can be found there.

After the license is downloaded to a development machine it can be installed with the help of the License Manager application that is located in the License Manager folder of the installed product. Please check to make sure the License Manager is run under the user with administrative rights, otherwise 'Cannot create registry key' error may happen. After the license is installed the registered product name should appear in the License Manager window, as well as the registrant's information and license expiration date.

In order to license the applications created during the test period in trial mode (showing 'Unregistered' watermark), the applications should be rebuild and republished.

In case the license was registered successfully, but the 'Unregistered' watermark is still displayed, please refer to the following articles:

http://helpcenter.perpetuumsoft.com/KB/a484/unregistered-label.aspx
http://helpcenter.perpetuumsoft.com/KB/a498/licensing-silverlight-viewer-reporting-services-30-versions.aspx


Add Feedback