HTTP Error 404 when running reports URL after a fresh instal of a new instance of SSRS

  • Getting this error while trying to set up a second SSRS instance on a seperate physical server using the same RepertServices DB on a third server. Everything runs fine on the original server.

    On the new instance no issues with connectivity to the database. rsreportserver.config matches exactly to the other server's config with the exception of <Dsn> and <InstallationID> tags. Reinstalling SSRS, backing up and restoring encryption key, did not help. What could be the issue? Any other config changes?

  • Wanted to check when you are attempting to access, you are getting 404? (if your response is yes)

    http://Servername/Reports

    How about when you access:

    http://Servername

    What are results then?

    --------------------------------------------------
    ...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully 😀

  • What url? If you can get access to http://server/reports, but not to actual reports... It is a different issue than not being able to get to http://server/reports.

    Jared
    CE - Microsoft

  • SQLKnowItAll (6/13/2012)


    What url? If you can get access to http://server/reports, but not to actual reports... It is a different issue than not being able to get to http://server/reports.%5B/quote%5D

    not able to get to http://server/reports - http error 404

  • when i'm on the server, in report manager i'm able to bring up http://servername/ReportServer but not http://servername/Reports.

  • Did you get this resolved?

    Not sure if you tried to rename the Virtual Directory in Report Manager URL section of reporting services configuration manager.

    Change it to "Test"

    then Change it back to "Reports"

    .. maybe there's a glitch with reports virtual directory?

    I'd be interested in the solution.

    --------------------------------------------------
    ...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully 😀

  • Heard of a similar issue from one of our BI team, in the end it was to do with a corrupted GUID in the ReportServerTempDB database. Have you considered the database might hold incorrect info? Have you replaced the DB with the DB for your new configuration?

    ---

    Note to developers:
    CAST(SUBSTRING(CAST(FLOOR(NULLIF(ISNULL(COALESCE(1,NULL),NULL),NULL)) AS CHAR(1)),1,1) AS INT) == 1
    So why complicate your code AND MAKE MY JOB HARDER??!:crazy:

    Want to get the best help? Click here https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help (Jeff Moden)
    My blog: http://uksqldba.blogspot.com
    Visit http://www.DerekColley.co.uk to find out more about me.

  • derek.colley (6/15/2012)


    Heard of a similar issue from one of our BI team, in the end it was to do with a corrupted GUID in the ReportServerTempDB database. Have you considered the database might hold incorrect info? Have you replaced the DB with the DB for your new configuration?

    Fixed the issue by changing port from 80 to 8080. Looks like something else is using that port.

  • Thanks for your solution, good to know for the future.

    when i'm on the server, in report manager i'm able to bring up http://servername/ReportServer but not http://servername/Reports.

    Does that mean your "ReportServer" was running on 8080 inside Reporting Services Configuration manager, while "Reports" was on 80 ? (by default both are set to port 80) ...this might be all a moot point since you fixed it.. but just curious 🙂

    --------------------------------------------------
    ...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully 😀

  • sqlsurfing (6/15/2012)


    Thanks for your solution, good to know for the future.

    when i'm on the server, in report manager i'm able to bring up http://servername/ReportServer but not http://servername/Reports.

    Does that mean your "ReportServer" was running on 8080 inside Reporting Services Configuration manager, while "Reports" was on 80 ? (by default both are set to port 80) ...this might be all a moot point since you fixed it.. but just curious 🙂

    Yep, under Web Service URL in Report Config Manager, Advanced options, changed TCP port for my url from 80 to 8080.

  • Thanks for clearning that up! 😀

    --------------------------------------------------
    ...0.05 points per day since registration... slowly crawl up to 1 pt per day hopefully 😀

Viewing 11 posts - 1 through 10 (of 10 total)

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