Redirecting HTTP to a new server being blocked by SSRS

  • We have migrated SSRS between servers as part of a SQL version upgrade. The original server has IIS on it (for MDS) and I want to use HTTP Redirection to send the traffic from the old server to the new one.

    If I go to "http://server" it redirects without issue but if I go to "http://server/reporting/browse" it returns HTTP Error 503: The service is unavailable

    As the SSRS service isn't running, why is it grabbing the HTTP request and not just letting IIS redirect it? Can I stop this happening?

    Ta.

  • Because SSRS does not use IIS - so any redirects in IIS have no effect on the SSRS service.  You can use IIS to redirect to SSRS - but you can't redirect SSRS itself to IIS or another system.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • Sorry; phrased my question badly.

    Since SSRS isn't running, *how* is it intercepting the URL? Why isn't this seen by IIS as any other HTTP request and redirected?

    That's what I meant.

  • Because it is installed, so http.sys has been modified

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • Ah. That's annoying. But thanks.

    Is there a way to redirect SSRS given that I don't want to uninstall it just yet.

  • Pete Bishop wrote:

    Ah. That's annoying. But thanks.

    Is there a way to redirect SSRS given that I don't want to uninstall it just yet.

    Not that I am aware of - what you can do is re-IP and rename the old server and add a DNS redirect from the old IP address to the new server's IP address.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • I am guessing that your users are trying to connect using https://servername...

    At my old place we set up a DNS alias for SSRS/PowerBI and got our users to connect simply by using //rsalias.  This gave us a level of abstraction between what users specified and our actual infrastructure.

    We had IIS running on the report server with a default document configured that changed incoming vanilla http requests to https://servername/reporting/browse and then SSRS or PowerBI would grab the http request via their configuration of http.sys

    When we wanted to change the server used to host SSRS (BTW you really should install PowerBI rather than SSRS) we built the new server and at cutover time simply changed the alias used for reporting. This setup took us through over a decade of SSRS upgrades from SQL2012 to SQL2014, then SQL2016, then SQL2017, then to SQL2017 PowerBI and to SQL2019 PowerBI. Many many server names used on this journey, but our users always connected via //rsalias

    • This reply was modified 1 year, 5 months ago by  EdVassie.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • Thanks for the feedback. On our new server (which is actually PowerBI) we have moved to DNS aliases so moving forward, we'll be fine. Just need to deal with the old server.

    Contemplating restoring the http.sys file and letting IIS handle it but not sure if that's sufficient.

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply