locked
Report Library providing row to RS Report Viewer - Wrong URL provided RRS feed

  • Question

  • Good afternoon,

     

    I am using an environment with the following:

    • SharePoint Server 2007 on two front-end Windows 2003 32-bit web servers w/ Reporting Services Integration
    • Backend SQL 2005 SP2 Windows 2003 server with Reporting Services in SharePoint integration mode.
      • This backend server also hosts the ReportServer virtual directory in an IIS site.

    I have successfully integrated our two front-end web servers with the reporting services module and after publishing a report to the Report Library in SharePoint, I can click on that report and have it open and display properly... All is well there (though it took many hours to get to that point ).

     

    So - when I try to add the MS SQL Svr Reporting Services Report Viewer web-part to a new web-part page in addition to the Report Library web-part and use the Connections->Provide Row to->Report Viewer function, I expect it should work. However, what happens is the Report Viewer displays an error.

     

    If the full URL of a particular report is  http://fqdn/sites/mySPSite/Report Library/My Chart.rdl, when the Report Library tries to pass the link into the Report Viewer, i instead get: http://fqdn/sites/mySPSite/sites/mySPSite/Report Library/My Chart.rdl. Note the duplication in sites/mySPSite/sites/mySPSite.

     

    Any thoughts on how to cure this? I did this same function in a test environment, but in that scenario, all my web parts were on the main page (http://fqdn) since it was just a test site.... and in that situation, it worked beautifully.

     

    Open to any and all suggestions. Thanks!

     

    Craig C. Regester

    Business Systems Analyst/Programmer

    Unity Physician Group

    Thursday, October 25, 2007 9:19 PM

All replies

  • Did you ever get an answer to this?

     

    The closest I got was a post from a MS Employee on one of the forums to say that this was a known bug that had crept in just befroe release - we now have SP1 and I am still experiencing this same problem!

     

    Anyone got a solution?

     

    Cheers,


    Sam

     

    Wednesday, March 26, 2008 12:22 PM
  • Hi,

    I am experienting then issue with sharepoint 3.0 SP1. Have you been able to solve this problem, or it is still pending?

    Regards

    Itexis
    Wednesday, December 10, 2008 5:18 PM