Forum Discussion

dulix's avatar
dulix
Copper Contributor
Mar 07, 2023

Open reportserver webservice URL with https leads to an ERR_HTTP2_PROTOCOL_ERROR

We have installed on a Windows Server 2022 the latest version of PowerBI Reporting Server. We have bound a wild card certificate to the PBRS webservice and PBRS portal site. We have also added the FQDN cname to the PBRS reportingserver config file.

We have used to deploy any reports by URL's like https://reports.contoso.com/ReportServer/Pages/ReportViewer.aspx?/Invoice/InvoiceReport.

Opening with Microsoft Edge we get the error:

Hmmm… can't reach this page

It looks like the webpage at https://reports.contoso.com/ReportServer/Pages/ReportViewer.aspx?/Invoice/InvoiceReport might be having issues or it may have moved permanently to a new web address.

ERR_HTTP2_PROTOCOL_ERROR
 
On the other hand when opening the URL https://reports.contoso.com/Reports/Invoice/InvoiceReport 
we will be asked to login with the user credentials. Afterwards calling the webservice runs fine.
 
Does anybody had already the same error and how we can avoid it?
  • Rodsawhite's avatar
    Rodsawhite
    Copper Contributor

    Hi dulix ,

    After some time spent with Microsoft support we may have a workaround:

    Disable HTTP2 on the server:

    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters

    EnableHttp2Cleartext DWORD = 0

    EnableHttp2Tls DWORD = 0

    Restart the server after adding these in and report back.

    • rhousham's avatar
      rhousham
      Copper Contributor
      Thanks for the response, I've forwarded your request to our systems team. For now we have reverted back and guess we might try the suggestion however don't want to cause more disruption.

      Seems well, poor that we have a workaround that disables HTTP2 - isn't this something Microsoft test???
    • dulix's avatar
      dulix
      Copper Contributor

      Hi Rodsawhite 

      thank you for your post.

      finally with these settings i get it running myself.

      kind regards dulix 

    • GregTz's avatar
      GregTz
      Copper Contributor

      Rodsawhite  Came looking for answers here and voila! Thank you sir! Extra annoying is the fact that SSRS doesn't register anything wrong in the logs which makes trying to find an explanation a pain!

  • JCdmirsAus's avatar
    JCdmirsAus
    Copper Contributor
    We implemented the 'disable HTTP2' option and it solved our problem (although our techos grumbled about 'why not just use HTTP3'). We will be on the lookout for a 'proper' solution from Microsoft going forward

Resources