Hello Report Builder is unable to access RS objects in SP (e.g. to open reports for editing, using shared data sources, etc) when: Multi-server SP 2010 farm RS 2k8 R2 in integrated mode RS configured to use SSL SP web app on SP WFE configured to use HTTP I am seeing Report Builder firing requests at the SP WFE server on port 443, all of which fail, since the WFE is not listening on port 443, only on 80. The RS instance on the RS server is listening on port 443. I am able to execute already written reports via the web app in SP successfully, and directly via the RS ReportServer URL on 443. Report Builder is however broken and seems thoroughly confused in that it is aiming requests at the WFE on port 443. This is I admit a strange configuration (users want the integrated SSRS instance on 443 to support multiple SP web apps, some on HTTP and some over SSL). Has anyone solved this issue? Is this a supported configuration? NB1: If I enable the RS instance to support both HTTP and HTTPS (by re-adding the port 80 web service URL) and setting the SecureConnectionLevel back to 0, Report Builder sends all requests over HTTP and springs back into life. NB2: I have confirmed all of the above by using Fiddler. Thanks, Chris

Hi Chris, Is there any error message when report builder can't access report objects in these scenarios? thanks, Jerry

Thanks for the reply. Typically the error is: ---------- No connection could be made because the target machine actively refused it 192.168.63.13:443 Unable to connect to the remote server ---------- 192.168.63.13 is the WFE. Note the attempt to connect on port 443, when the WFE is listening only on port 80. Only the RS instance (on the RS server) is listening on 443. A screen shot of this can be seen at: http://www.cbailiss.com/ScreenShot.png Note the repeated attempts to connect on 443 in the Fiddler Trace. This trace shows the requests in opening Report Builder and attempting to open a report stored in SP. Unfortunately from the Fiddler trace the URL cannot be seen (since the connection is never made and thus the http request is never sent) but they occur whenever Report Builder is trying to retrieve data/RS objects. Thanks, Chris