My environment is as follows: - Microsoft SQL Server Reporting Services Version 9.00.4035.00 MOSS SP2 with full hotfixes Windows Server 2003 Internet Explorer 7 I'm having an issue that I hope someone can help me with. I'm running a server farm where in which MOSS 2007 (SP2) and SSRS 2005 are running alongside each other. SSRS has been configured to run in SharePoint integrated mode, with what appears to be no problem. We've further configured the report generator to tie into a specific site collection, upon which we hope to store, create and retrieve reports as required. The problem that I'm encountering is that whenever I try and access the Report Builder via this integrated Site collection, I'm generating the following error message: - “An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode. --> The request failed with HTTP status 503: Service Unavailable” This suggested to me that it was a permissions issue, so these have all been checked correctly and nothing stands out as being incorrect. The items I have inspected thus far are: - Permissions across SSRS, SQL, MOSS: These all appear correctly SharePoint Integrated Mode: This is running with no problems in the SSRS Configuration Manager Accessing the instance in SSMS: I'm unable to access the instance in SQL Server Management Studio (I generate a 404 error), but it can be accessed via the browser I have checked the SharePoint hive 12 logs and no SSRS logs appear here. I've checked the ReportServerService logs, and only get one error (see below) I'm able to access the SSRS configuration screen and default settings via MOSS Central administration The ReportServerServices log generated this error message: - "Polling caught an exception, restarting polling. Error Message System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)" Now, in terms of resolution, what could I have missed? The 503 error doesn't seem to be a very common one, I've only found this thread thus far: - http://social.msdn.microsoft.com/forums/en-US/sqlreportingservices/thread/501b36ce-726e-40f8-8284-c635a13843a3/ I'd like to have a concise list of possibilities to look at before I start changing things on the server? I'm thinking of these areas: - Checking there is no application pool conflict; and that each server has its own application pool Add the Reporting Services virtual directories to the Windows SharePoint Services list of exclusions Checking internet explorer authentication is set to integrated windows authentication Look at IIS authentication mode. Some deployments appear to need NTLM anthentication Checking that the SPNs are set up to work with the correct domain accounts I'm up for suggestions on what else I may have missed.

Actually, Report Builder uses ClickOnce technology to download and install its application files on a client computer when you Edit a report. ClickOnce sends requests that specify Windows integrated security in the authentication header. If a server is configured for a different authentication type, the server will fail requests from ClickOnce. To work around this issue, you must either configure a server for Windows integrated security or you must enable Anonymous access to eliminate the authentication check. Steps for enabling Anonymous access are below: 1. Open Internet Information Services (IIS) Manager. 2. Click the sharepoint site, you will see Authentication on the Features View surface. 3. Click the Authentication icon, then Enable the Anonymous Authentication in the status column. For more information about How to: Configure Report Builder Access, please see: http://msdn.microsoft.com/en-us/library/ms365173.aspx Hope this helps. Thanks, Challen FuChallen Fu [MSFT] MSDN Community Support | Feedback to us Get or Request Code Sample from Microsoft Please remember to mark the replies as answers if they help and unmark them if they provide no help.