Report Builder Question

Please help!!!!

We have recently implemented an SQL Server 2005 and when i click on the report builder button (reporting services) for the user i am getting the message "Application Download did not succeed. Check your network connection or contact your system administrator or Network Service Provider"

This is actually performed while the user has administrator privledges.

If someone has this problem or a solution, could you please post.

Thanks

This sounds like at authentication problem. If the logged-in user's default Windows credentials are not appropriate or sufficient for authenticating to the report server, then ClickOnce cannot download the application. In these cases (i.e. when you are not using Windows Auth), you need to go into IIS and allow anonymous access to the ReportBuilder virtual folder.

Hope that helps.

sql

Report Builder not working with Forms Authentication

We have successfully implemented forms authentication. The ReportServer and Report Manager both are working fine. However, when we launch the ReportBuilder using the url http://<server-name>/ReportServer/ReportBuilder/ReportBuilder.application or from the Report Manager, it prompts for user name and password. On entering the valid user-name and password, it gives the following error.

The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version.

It doesnt accept any user-name, password (neither forms one, nor windows). This error is when we are trying to access Report Builder on the server (not tried on the client machine). The user-name has been given System Administrator and System User role. We have also given the Content Manager, Browser, ... etc all roles to the user.

However, we are testing this on June CTP. Is this a problem ?

This is very urgent as the rest all is working fine. Any suggestions ?

Thanks in advance.

Is there any solution? Does Report Builder work with Forms Authentication ?|||

If I remember correctly, this was a bug that we fixed before the RTM release of RS 2005. If you upgrade to RTM - or better yet, to SP1, this should work.

Thanks

Tudor