I have installed SQL Server 2008 Enterprise with Reporting Services. I can configure reporting services and view the report manager web page with no problem. I can do anything I need in the rrpeort manager. I can create reports using the Report Builder 1.0 using data sources and models created in the report manager web site. I cannot get Report Builder 2.0 to connect to the Report Manager. I have set the default URL to the address I use to access the report manager, but this givesthe following error when I try to create a data source. Connection Failed. Unable to connect to the server that is specified in the URL, 'http://<server name>/reports/'. Make sure that the server is running, the URL is correct, and you have permission to use the server. I am able to create an embedded data source using the same server the reporting services are installed on. John PearsonSystems Analyst/ProgrammerUnified Trust Company, N.A.john.pearson@unifiedtrust.com

Hi John -- Report Builder 2.0 needs the URL of the Report Server, not the the Report Manager (confusing I know). Try the URL "http://<servername>/reportserver" Thanks, Denesh.

Hi Denesh,I tried using the report server URL but experience the same problem Connection Failed. Unable to connect to the server that is specified in the URL, 'http://<server name>/reports/'. Make sure that the server is running, the URL is correct, and you have permission to use the server.Regards-Advait

Hi I havethe same problem...solutions?Thanks,Leonard

Hi, I also have a similar problem.Using SQL-2005 as my database, I have another server running SSRS-2008. We also implemented Report Builder 2.0. But we have a problem.Using my Admin credentials I am able to run Report Builder 2.0 to create Shared Data Sources, create Reports using the Shared Data Sources, Publish Reports and, of course, Run and View Reports. That part is great.However, using my Non-admin credentials, I am able to Run and View Reports, but I cannot do anything else (no matter how many Security privileges I am assigned)because I am blocked bythis step:myNon-Adminaccount cannot access the Shared Data Source.Now, the Shared Data Source connection is designedas follows: "Credentials Stored Securely in the Report Server". Those credentials are my Admin credentials, which have no problems with any aspect of Report Builder 2.0.So, I would expect my Non-admin account to be able to connect to the database through the Shared DataSource using those privileged stored credentials.However, the error message I receive is: "Unable to connect to data source <ds_name>".The details are as follows: "Cannot open database <db_name> requested by the login <login_name>." Now, the <login_name> is my Non-admin account!Why?If theShared Data Source is designed to use Stored Credentials with privilegedAdmin credentials, why does Report Builder use my Non-admin account to try to connect? Thanks,--Paul

OK, I think this is the answer. Microsoft has acknowledged this is a bug, however, it has also questioned what to do about it, since it is a potential Security risk. Here's the Microsoft URL:https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=415539&wa=wsignin1.0

Denesh, I'm having the same problem as Advait and Leonardo, and Pablo's issue (and answer) refers to a different problem I think. I cannot find any useful information to resolve this - can you help please? Thanks, Peter.

Right - the reason for this problem (for me) is because Report Builder connects to Reporting Services via the *Web Service URL*, and not the standard URL that I was expecting. To view/modify the web service URL, go to Reporting Services Configuration Manager, select "Web Service URL" from the left-hand menu, and there you go. Why oh why no-one bothers to make that clear for newbies like myself (thrown onto a project where the Web Service URL had already been changed from the default) annoys the pants off me. Danesh Pohar - you need to give better, more complete answers than that I'm afraid!! Saying "Report Builder 2.0 needs the URL of the Report Server " doesn't mean much to someone like me. It's things like this (where one can waste 2 or 3 hours over something that should be blindingly obvious) that make one end up cursing microsoft - and it's your job on this forum to help us through these issues. Peter

AGREE, Denesh Pohar your answear is not bad, but not so clear. Thx PeterMorgan :)

So can ReportBuilder 2.0 use a Shared Data Source Connection in ReportServer with Windows Integrated Authentication to proxy a connection from an end-user?

I thought the answer was very clear.

I am having the same problem that John Pearson started this tread with: I cannot get Report Builder 2.0 to connect to the Report Manager. I have set the default URL to the address I use to access the report manager, but this gives the following error when I try to create a data source. Connection Failed. Unable to connect to the server that is specified in the URL, 'http://<server name>/reports/'. Make sure that the server is running, the URL is correct, and you have permission to use the server. I have tried numerous times to uninstall Report Builder 2.0 and after reinstalling it I recieve the same error when trying to connection to any of our 4 - Report servers. I know the problem is with my work station because I can login to another machine and Report Builder 2.0 will connect to any RS I point it at. Does anyone have a suggestion on what I might try on my WKSTA to get past this problem? It may have something to with HTTPS testing I was doing a couple of weeks ago but, I'm not sure what could have changed to cause this problem.

Try pointing it to ReportServer instead of Reports

That is where I am connecting: http://sqlsrvname/ReportServer_TS2. As I stated above, it is specifc to my development work station. If I login to another work station as myself and connect to this address it works fine.

I applied SQL 2008 SP1 to my workstation and it fixed the RS connection problem.

Hi, can someone help? I too am having the same/similar problem as above. My URL in Configuarion Manager is pointing to 'http://<server name>/reports/" and I do have SQL 2008 SP1 installed. When I click on this URL, a web browser opens up and the Report Manager page does display. However, when I open ReportBuilder and try to connect to the server I get the "Unable to connect" error. What else can I check? thanks!

Check this out: http://betav.com/blog/billva/2009/06/solution-sql-server-report-bui.html

also - RB2.0 only works with Windows Integrated Auth. YOu must deploy it anonymously to make it work (open up). your repor model will be "protected" by ssrs so that works good.

Thanks Denesh. Had the same problem and replaced it with http://<servername>/reportserver and it worked

Right - the reason for this problem (for me) is because Report Builder connects to Reporting Services via the *Web Service URL*, and not the standard URL that I was expecting. To view/modify the web service URL, go to Reporting Services Configuration Manager, select "Web Service URL" from the left-hand menu, and there you go. Why oh why no-one bothers to make that clear for newbies like myself (thrown onto a project where the Web Service URL had already been changed from the default) annoys the pants off me. Peter, you are the winner! It is the Web service URL. The other may work if you don't have a named instance but it absolutely does not work with a named instance. Kudos to you!

Thanks Denesh. Had the same problem and replaced it with http://<servername>/reportserver and it worked This does not work if you are using a named instance in SQL Server (which MS recommends). You have to use the Web service URL. Peter Morgan is absolutely correct.

What worked for me is the Web service URL http://<servername>/ReportServer_<InstanceName> Thanks again to Peter Morgan.

Does it matter if you use a port number and a named instance? I can't figure out why I'm still getting the unable to connect error. My URL is http://gmcrpt:8088/Reportserver_GENMRT I can hit the site with no problem but when I enter it into the Reportbuilder's (stand alone application) server connection I get the error.

No that's fine. Just make sure you're using the ReportServer COnfig utility to set this up. Report manager and ReportServer endpoints should oad on your screen without problem.

I think I found my problem. I was trying to use Reportbuilder 3.0 on 2008. You can only use 3.0 on 2008R2 from my understanding. I can connect using Reportbuilder 2.0

I think I found my problem. I was trying to use Reportbuilder 3.0 on 2008. You can only use 3.0 on 2008R2 from my understanding. I can connect using Reportbuilder 2.0

RB 2.0 will work on 2008 R2 too but RB3.0 only on 2008 R2

RB 2.0 will work on 2008 R2 too but RB3.0 only on 2008 R2