404 from ReportService.svc using https and silverlight

[Sergey]

Hello,
I went through many 'Enable SSL for Telerik Reporting WCF service' posts and articles. Still, when accessed through ReportViewer - ReportService.svc returns 404. If I use the same url in IE – it works.
I’m using 'reportViewer.ReportServiceClientFactory = this' and as soon as I create binding using: new BasicHttpBinding(BasicHttpSecurityMode.Transport) – I get this error.
Not sure where to look anymore… All other wcf services (same web app) do work with https.

Thanks,Sergey

[Sergey]

OK, 404 is gone (resources most likely). I'm back to "The provided URI scheme 'https' is invalid; expected 'http'." error. Here are relevant parts of the web.config: 

 

<service behaviorConfiguration="ReportServiceBehavior" name="Telerik.Reporting.Service.ReportService">
    <endpoint address=""
                   bindingConfiguration="ReportService_basicHttpBinding"
                   name="basicHttpEndpoint"
                   binding="basicHttpBinding"
                   contract="Telerik.Reporting.Service.IReportService">
    </endpoint>
    <endpoint address="resources" binding="webHttpBinding" bindingConfiguration="WebHttpBindingConfig" behaviorConfiguration="WebBehavior" contract="Telerik.Reporting.Service.IResourceService"/>
    <endpoint address="mex" binding="mexHttpsBinding" contract="IMetadataExchange" />
</service>

<behavior name="ReportServiceBehavior">
    <serviceMetadata httpsGetEnabled="true" httpGetEnabled="true" />
    <serviceDebug includeExceptionDetailInFaults="true" />
    <serviceTimeouts transactionTimeout="00:00:30" />
    <serviceSecurityAudit auditLogLocation="Application" serviceAuthorizationAuditLevel="SuccessOrFailure"
                messageAuthenticationAuditLevel="SuccessOrFailure" />
</behavior>

<binding name="ReportService_basicHttpBinding"                     maxReceivedMessageSize="2147483647" maxBufferPoolSize="2147483647" maxBufferSize="2147483647"         transferMode="Buffered" closeTimeout="05:20:00" openTimeout="05:20:00" receiveTimeout="05:20:00" sendTimeout="05:20:00">
<readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647"  maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/>
<security mode="Transport">
<transport clientCredentialType="None"/>
</security></binding>

<webHttpBinding>

    <binding name="WebHttpBindingConfig">

        <security mode="Transport">

            <transport clientCredentialType="None"/>

        </security>

    </binding>

</webHttpBinding>

Do you see what's wrong here?
Thank you,
Sergey

[Sergey]

I copied your configuration from http://www.telerik.com/help/reporting/silverlight-enable-ssl-for-telerik-reporting-wcf-service.html to the letter, still the same error. Only from report viewer, IE still shows 'You have created a service.' page, other services continue to work.
What am I missing?

Thanks,
Sergey

[Massimiliano Bassili]

The web.config markup in the documentation is correct, however it depends on IIS settings, authentication etc. See this forum for different variations depending on different settings: http://www.telerik.com/community/forums/reporting/telerik-reporting/enable-ssl-for-telerik-reporting-wcf-service.aspx

Cheers!

[Sergey]

Thank you, Massimiliano. I tried all that, didn't help. I understand it depends on IIS settings, environment etc. - I'm just not sure what else to try...

[Massimiliano Bassili]

One of those changes should work for you... If I were you, I would host this on my dev machine IIS, enable CLR exceptions in Visual Studio and start debugging. As Telerik have advised, you can get Fiddler to track your requests and responses to see where the chain gets broken. I often see people rant that their other WCF services work, but Telerik's doesn't, forgetting that the regular WCF services have been added from Visual Studio item template, so VS has done all the setup. Well Telerik's does not have item template, so you have to register it manually and sometimes people miss stuff that is often obvious.

Cheers!

[Sergey]

I didn’t mean to rant, just wanted to solicit suggestions :) 
We don’t use templates, all services created manually and that was one of the problems – apparently telerik reporting requires configuration in Silverlight’s solution web.config.

Anyway, it solved now. Problem was inside of ReportService processing where we would try to call another service with security mode=’None’ and report service reported back that “The provided URI scheme 'https' is invalid; expected 'http'.”

Thanks again,
Sergey