This is a migrated thread and some comments may be shown as answers.

Print Button not presenting dialog box Silverlight

4 Answers 67 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

4 Answers, 1 is accepted

answered on 26 May 2011, 04:25 PM

Hello Mark,

Please check whether you have registered the Reporting Service endpoints in the web.config correctly as shown in the Hosting WCF Service in IIS help article. Namely the resource endpoint is responsible for the print, so if it missing the print button would not work. Additionally the print functionality depends on the Acrobat PDF plug-in, so if Acrobat Reader is not installed or the plug-in is disabled in the browser you would not be able to take advantage of the true print.

All the best,
Steve
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

answered on 02 Jun 2011, 01:57 PM

I have made sure that the adobe add-in is installed. I also added the service in the web.config as in the "Hosting WCF Service in IIS". When I added the service to the web.config, the report does not work. It gives the following error: "An exception occurred during the operation, making the result invalid. Check InnerException for exception details." The problem is I have no way to look at the InnerException to get the details. I am attaching my web.config.

Thanks for any help you can give me,
Mark

<?xml version="1.0"?>

<!--

For more information on how to configure your ASP.NET application, please visit

http://go.microsoft.com/fwlink/?LinkId=169433

-->

<configuration>

<configSections>

<section name="openaccess" type=

"Telerik.OpenAccess.Config.ConfigSectionHandler, Telerik.OpenAccess.Config, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7ce17eeaf1d59342"

requirePermission="false" />

<section name="Telerik.Reporting"

type=

"Telerik.Reporting.Processing.Config.ReportingConfigurationSection, Telerik.Reporting, Version=4.1.10.921, Culture=neutral, PublicKeyToken=a9d7983dfcc261be"

allowLocation="true"

allowDefinition="Everywhere"/>

</configSections>

<system.web>

<compilation debug="true" targetFramework="4.0">

<assemblies>

<add assembly="Telerik.OpenAccess, Version=2010.1.527.2, Culture=neutral, PublicKeyToken=7ce17eeaf1d59342" />

</assemblies>

</compilation>

</system.web>

<system.serviceModel>

<behaviors>

<serviceBehaviors>

<behavior name="">

<serviceMetadata httpGetEnabled="true" />

<serviceDebug includeExceptionDetailInFaults="false" />

</behavior>

<behavior name="ReportServiceBehavior">

<serviceMetadata httpGetEnabled="true" />

<serviceDebug includeExceptionDetailInFaults="false" />

</behavior>

</serviceBehaviors>

<endpointBehaviors>

<behavior name="WebBehavior">

<webHttp />

</behavior>

</endpointBehaviors>

</behaviors>

<bindings>

<customBinding>

<binding name="MartialArtsStudentsDataServiceCustomBinding">

<binaryMessageEncoding />

<httpTransport />

</binding>

<binding name="ReportDataServiceCustomBinding">

<binaryMessageEncoding />

<httpTransport />

</binding>

</customBinding>

<webHttpBinding>

<binding name="WebHttpBindingConfig">

<security mode="Transport"/>

</binding>

</webHttpBinding>

</bindings>

<serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true" />

<services>

<service name="MartialArtsStudents.Web.MartialArtsStudentsDataService">

<endpoint address=""

binding="customBinding"

bindingConfiguration="MartialArtsStudentsDataServiceCustomBinding"

contract="MartialArtsStudents.Web.MartialArtsStudentsDataService" />

<endpoint address="mex"

binding="mexHttpBinding"

contract="IMetadataExchange" />

</service>

<service name="MartialArtsStudents.Web.ReportDataService">

<endpoint address=""

binding="customBinding"

bindingConfiguration="ReportDataServiceCustomBinding"

contract="MartialArtsStudents.Web.ReportDataService" />

<endpoint address="mex"

binding="mexHttpBinding"

contract="IMetadataExchange" />

</service>

<service name="Telerik.Reporting.Service.ReportService" behaviorConfiguration="ReportServiceBehavior">

<endpoint address=""

binding="basicHttpBinding"

contract="Telerik.Reporting.Service.IReportService">

<identity>

<dns value="localhost" />

</identity>

</endpoint>

<endpoint address="resources"

binding="webHttpBinding"

behaviorConfiguration="WebBehavior"

contract="Telerik.Reporting.Service.IResourceService" />

<endpoint address="mex"

binding="mexHttpBinding"

contract="IMexdataExchange" />

</service>

</services>

</system.serviceModel>

<openaccess xmlns="http://www.telerik.com/OpenAccess">

<references>

<reference assemblyname="Data" configrequired="True" />

</references>

<connections>

<connection id="DatabaseConnection1">

<backendconfigurationname>mssqlConfiguration</backendconfigurationname>

<integratedSecurity>False</integratedSecurity>

<databasename>MartialArtsData</databasename>

<servername>(local)\SQLEXPRESS</servername>

<user>wbmuser</user>

<password>Twelve_12</password>

<!--<servername>facit-svr</servername>

<user>facit</user>

<password>F@citTwelve_12</password>-->

</connection>

</connections>

<backendconfigurations>

<backendconfiguration id="mssqlConfiguration" backend="mssql">

<mappingname>mssqlMapping</mappingname>

</backendconfiguration>

</backendconfigurations>

<mappings current="mssqlMapping">

<mapping id="mssqlMapping" />

</mappings>

</openaccess>

</configuration>

answered on 03 Jun 2011, 12:45 PM

Hello Ashton,

In the latest version Q1 SP1 2011, we've improved the error handling for the Silverlight viewer and it now shows the inner exception. If feasible for your case - go ahead and upgrade.
If this is not an option you can still pinpoint the problem by trying the following:

show the Output window in Visual Studio and check whether there is an exception when you're running your application in debug mode.
access the .svc file directly in your browser to see if it reports any problems.
enable the CLR exceptions from Debug --> Exceptions menu in Visual Studio and run your project in debug.

Greetings,
Steve
the Telerik team