Hi All,I installed SQL Server 2005 SP2 recently. After that when I try todeploy a solution in SSRS 2005, I get a dialog box with title:"Reporting Services Login". It has my server listed as the first row:"http://localhost/reportserver" and then it has two text boxes askingfor Username and Password. I checked my IIS settings and only Integrated Security is checked forthe Reports Server folder (and for the entire website). I tried tochange that to Allow Anonymous Access = Checked, but still the sameproblem. Any ideas?Thanks! GB

GB, Just wondering if you ever resolved this problem... How'd do you do it? I'm having the same symptoms and can't find a single post anywhere in which someone had a solution. Thanks!

Me too. Exactly the same symptoms. Tried the same things to solve it too.

i have face the same problem anybody is there to help us.?

You need to give rights in the report manager sites to the user. Do not change it in IIS, it will do nothing. If you have the rights to the report manager you can give access on specific folders or all folders to users. http://yourservername/reports is the default link to the report manager. If you preferyou can use the "Microsoft SQL Server managment studio " to do the same thing. If you are not an admin on the reporting services server contact your admin. Good Luck

I have solve this problem, myself. The problem is that i have written the target server url only to http://localhost/ but when i change it to "http://localhost/reportserver" it work fines. so in this way all of you check your target server url to remove this problem

I have been hoping for resolution of this problem. Having recently installed SS05, I have not yet got this sorted. I have followed generic instructions, incl. IIS set ups, deployment options (incl using http:\\localhost\ReportServer), but still get the credentials request. I have local admin rights to server\ using windows domain account. Could you be more explicit (sorry!) Paul about how to give necessary access to (which) folders, given I am using default settings?Thanks for everyone's input on this.Ken

i keep getting EXACTLY the same issue. wasted 5 hours of the day trying to figure it out before i finally called in a troubleshoot request with microsoft. will let you guys know what the problem is as well! Xavier (perth, australia)

I found this thread because I was experiencing the same issue described here. I just found a resolution, for my specific case anyway. It turns out that the report server path property was wrong in the reports project properties. I had to create the reports web site http://localhost:81/reports and I neglected to put in the port number in the properties so it was attempting to access a site that didn't exist. My only suggestion would be to check the url of your report server very closely.Good luck.

still no word from MSFT. Thanks scott for your advice, I presume you inserted this URL in the "Manage Integration Settings" http://localhost:81/reports Then where "Grant Database settings, you entered the name of your server (no port included). In my VM, the server name is CLEANSERVER2003 Instance is default (MSSQL) I still get the same "Could not open DBASE with user name and password settings" Any further info you could possibly give? Cheers

SQL 2005 I have the opposite problem. I am trying to deploy the solution and it is using some other login to try to deploy. This other login does not have the correct rights to deploy. How do I get Visual Studio to prompt for the login name and password when I am trying to deploy the solution. I have checked that the target is correct. I have deleted all cookies and internet files from my PC, removed all other (file share) connections to the serverand rebooted. Still no luck - it still wants to use the old login id.

Works great for me! Thx!PS: another solution that I found is here: FIX: The Reporting Services Login dialog box appears repeatedly when you deploy a report on a remote computer by using Report Designer http://support.microsoft.com/kb/842517 (not working for me)

Paul.G. wrote: You need to give rights in the report manager sites to the user. Do not change it in IIS, it will do nothing. If you have the rights to the report manager you can give access on specific folders or all folders to users. http://yourservername/reports is the default link to the report manager. If you preferyou can use the "Microsoft SQL Server managment studio " to do the same thing. If you are not an admin on the reporting services server contact your admin. Good Lucksry for the second post. This solution works for me.

I've been fussing with this a couple days now myself. The fix, quite simply really:In my particular case I install SQL 2005 as a seperate instance, so instead of http://localhost/reportserve mine was http://localhost/reportserve$SQL2005and that, in itself, was enough to break reporting services and query for the reporting serivces login again and again and again.So, where do you fix it:1. Open your project in SQL Server Business Intelligence Development Studio2. Select the project menu followed by the properties of the project.3. Change the TargetServerURL: To the appropriate path to your reportserver.if your still not sure ( hard to believe but I suppose... ) open your IIS manager, expand the default web site and spot your reporting services virtual dir.There you go ... what a pain in the ...Regards from Indianapolis

I still have the problem after trying all the above. I'm running XP Professional 32-Bit (SP2), SQL 2005 Developer Edition (SP2) and Visual Studio 2005 (Version 8.0.50727.762 SP.050727-7600) all on my local machine. SQL 2005 developer is installed as an instance called LOCALHOST\SQL2005 running undermy domain administrator account. (TheDC isunavailable however since i work offsite, i don't see why this should be an issue though). I can connect to reporting services using ie7 http://localhost/Reports$SQL2005it all seems to be working fine, it doesn't ask for a username it appears to be using my windows login credentials When i try to deploy from Visual Studio i just keep getting the Reporting Services Login box. I've tried all combinations of username and passwords available. This isvery frustrating!

Found the solution, i removed the 2000 version of reporting services and it now deploys ok, the login dialog doesn't even appear at all.

I too have wrestled with this "Reporting Services Login" box issue for a while. I have FINALLY solved the issue ( or at least what was causing my occurance of this annoying box) I have tried everything. It started when i was trying to deploy to a remote server. To try and take the security out of the picture, I tried to deploy locally with the "sa" user. Still no luck. I tried every login i could think of. domain users, domain admins, sql server admin, and local administrators. Nothing worked. I'm using SQL Server 2005. Deploying with Visual Studio 2005. In a last ditch effort I looked at the SQL Server Reporting Services Configuration Setup. I tried adding myself as the "Execution Account" (this step was apparently not setup automatcially when Reporting Services is installed) and had a yellow triangle when i revisited the setup screen. Worked like a charm! I can't tell you how excited i was to see the words "Deploy Succeeded" Hope this helps someone else struggling with the same issue

I had the same problem as AmandaLynn is describing. Thanks to her post where she shared her information about the "Execution Account" I finally was able to deploy my reports. Thanks alot. Regards, Richard

For what it's worth, I found success when I modified theLog Onin SQL Server Reporting Services (via control panel, services) to be the Local System account.

Hello, I have been struggling with this issue for two days now. New to it all. Can you explain, step by step how you resolved this? I am going into the configuration manager, but do not see the "Execution Account". Thank you for your help.

GB, This happened to me and in my case somehow SSRS is running in internet zone in IE rather than local intranet zone as it should. (of course you know you see that at bottom right area of browser window, with IE7 anyway). So, i reluctantly had to change the security for the internet zone. Go to IE, tools, internet options, security tab, under internet zone click custom level and if it's set to "Automatic login only in local intranet zone" you will need to change it to "Automatic login with current username and password". This will work but i'd like to know why this is running in internet zone to begin with. I am running XPSP2, IIS 5.1 and SQL Server 2005 Express. I noticed all of my asp.net websites started to error if I run w/debugging and it was because of this same thing, they are running in internet zone. I know they were not before I installed SSRS for SQL Express advanced. I am now looking for that information.....so if that was not your issue, can you tell me how to tell SSRS http://localhost/reports to run in local intranet zone? Or anyone that may see this. If this was your issue, please let me know and maybe pass on if you figure out why reporting services is using internet zone on local setup. Thanks, Jerry

Grantingaccess through "Execution Account" could resolve the issue but you still need to provide the user name and password everytime you deploy. To avoid the dialog box from popping up, changeyour TargetServerURL from http://localhost/Reports to http://localhost/ReportServer. Hope this help.

Kelvin, The report manager and report server are 2 different things. While you can run reports from reportserver, you don't have access to folders, properties, security settings, roles etc. This is an update to my earlier post.This happened once before a long while back that Idiscovered I cannot debug ASP.NET web apps after some event, usually an installation. Ican't recall the resolution then but this timeresorted to using something I found in a microsoft blog which tells you to change security settings for the Internet zone to Automatic login for current username and password. That fixed the problem, no more login boxes when accessing http://localhost/reports and I could deploy reports from VS 2005 BI add in just fine. But why was everything running in internet zone? I'm not strong with web related programming and setup as I'm sure anyone can tell by now. Anyway, since it had been set on automatic login in intranet zone only, it was not working because the Report services install somehow changed zone settings in IE security and had removed http://localhost from being seen as a local intranet app. When a localhost app is seen as intranet app, your credentials will be passed on successfully w/o any other messing around. So, what I found to be the REAL problem, for me anyway, was that in IE, tools, internet options, security, if I clicked the local intranet icon, then clicked the sites button which brings up a box showing Auto detection of intranet network. If you then click Advanced button at the bottom, you will get a screen to add sites. Add http://localhost here if it's not added. I found the box empty and i'm sure SSRS installation somehow caused this since my asp.net websites running on localhost had always worked in debug mode just fine before that install and you must have http://localhost added there for that to happen. My original mistake was clicking trusted sites on the security tab, then the add sites button and putting in http://localhost there. That did not help, you must have local intranet highlighted before clicking the add sites button and just verify that localhost is added as a site in that zone. It will then treat it as local and pass your credentials just fine for SSRS and all other local web apps that require authentication beyond anonymous access set in virtual directory properties. In fact, for reports and reportserver virtual directories, make sure you don't have anonymous access checked. It won't work for SSRS.

Changing from /Reports to /ReportServer sure helped me - thanx Cato

Hi, I read your post with interest but am still having the popup login box appear. What account did you use for the execution account? Is it the ISS anonymous account, i.e. IUSR_whatever, or are you using the local PC/domain sign-on. If the latter what are your IIS authentication settings? Cheers, Lee.

Further to the above .... My problem seems to arise before I get to the configuration stages of Report Server. Let's say I have a simple 'hello.html' page and place this in the root directory of a virtual server created through IIS. The result is the page I expect. Now if I do the same with a virtual server, created through the Report Server Virtual Directory Settings, then I get a "Server Application Unavailable" browser message. I've checked the permissions in both cases and they are the same. So if I can't get this far then the problem is nothing to do with Visual Studio and deployment. I'd be grateful if anyone can shed some light on this. I don't really want to do a re-install of all my software. Thanks, Lee.

Hi Mr Guran,maybe you install SSRS 2000 and SSRS 2005 in the same computer? if yes, reporting service login box repeatedly appears if you deploy SSRS 2005 from SQL Server Business Intelligence Development Studio. the sollution from articel that i have read at http://support.microsoft.com/kb/842517. first you should check SSRS 2000 Latest Service Pack. How to obtain the latest service pack at http://support.microsoft.com/kb/842440/ should solve your problem..regards,ARIES BUDI SUSILO

Hello, Finally I have found the reason for this login popup. When you want to deploy your report; in the report properties you will have to enter the "TargetServerURL". If you enter the server URL like this "http://<SERVER>/reportserver/reports" you will throw an error which will make the login popup appear. The key is to put the folder name, in this case "reports" in the "TargetReportFolder" area and only put the following in the server URL "http://<SERVER>/reportserver". Again,the login popup appears if you try to put the target folder name at the end of the server URL. All of this is done in the Report's properties. Mark aka AuSablewolff

JerryeE, your solution doesn't work for me. Is it important to restart the computer after these edits, or to restart the Visual Studio? Anyway, I carefully followed your advise, but it didn't work, I still get the login box.Any more ideas?

I'm very, very new to this (SQL, Reporting Services...) and was going through MSDN tutorials on Reporting Services. I got to the last part, publishing the report, and encountered this problem (login box). Tried my domain credentials, no success. So I Googled and found this thread. I tried a couple things here (Execution Account, IIS Permissions on default web site). I have domain admin privileges. (not important, but I am doing all this on a test LAN). No success. I then read AuSablewolff's post and thought he might be on to something regarding URL. Thanks to another post in this thread, I stumbled into Reporting Services Configuration. (Start, Programs, SQL, Config Tools, RSC and noticed that the Report Server and Report Manager Virtual Directorties had a $<sqlinstancename> at the end of ReportServer and Reports respectfully. This helped solve one of my earlier mysteries: accessing SSRS report manager through the 'default' URL of http://localhost/reports (in my case I have to go to http://localhost/reports$<sqlinstancename>). So, I went back to the tutorial and specified the RSVD URL as the TargetServerURL and the report published with no login box! So, bottom line, (at least for me)... check Reporting Services Configuration Manager for the name of your RS Virtual Directory, then use that name in the URL when deploying (Debug, Start without deploying... according to the Tutorial). I haven't gone further than this, so I reserve the right to have more problems with future reports or whatever, but this worked in this particular case anyway.

Hi everyone!Having the same problem I'd tried almost everything (checked report catalgogue rights on IIS, giving propert permisions in SS 2005), but I still couldn't deploy my RS project. Finally I tried this (trusting my intuition):1. Reporting Services Configuration Manager -> Database setup2. Check the Server Name property -> The default setup in my case was "USER/2005" , I've checked this (using dropdown) to "(local)/2005" ...and to my surprise it started to work!I hope I can help someone,greetings

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=338852&SiteID=1I had the same problem but was resolved because of the access to the file Reporting Services\ReportServer\rsreportserver.config. See the post above.

I too am having this problem. Can someone who may have expert knowledge of this product give a list of possible causes and a solution?

Thanks mughal bro.

Looks like the solution was posted earlier in the thread and I marked it as such. To summarize the case for this thread: Report Designer (BIDS) will prompt you for a login repeatedly if you enter the wrong URL in the Target Server property in the report project settings. The URL you enter must match the URL of the report server (NOT report manager!). The default value is http://localhost/reportserver. If you have different port numbers or instance names you'll have to adjust to match the setting you have configured for your report server. You can use IIS manager or the report server configuration tool to check the URL you should be using. HTH, -Lukasz

This worked fine with me too. TargetServerURL: http:/<servername>/ReportServer/ Thanks!

I was having problems deploying a Report Model to my pristine and new SSRS 2005 deploy with the Forms Authentication Sample implemented (including Tyler Chessman's fixed file for the VB one from SQLMag). For the life of me I could not figure out how to get the Deploy of my first and only Report Model to work from BIDS 2005. It would repeatedly prompt me for "User Name" and "Password", in a Reporting Services Login box, and would not accept valid credentials (SSMS didn't have a problem with the Forms Authentication at all). I went through permissions with a fine tooth comb. Hours on the Google (a small portion of which was the troubleshooting in this thread). Completely reinstalled everything. Still wouldn't work. In the end, the solution for me was quite simple: use BIDS from SQL Server 2008 (CTP worked for me). It worked from a remote box in the domain. I tested with another SQL BIDS 2005 box that was also remote, same problem handling the Forms Authentication Sample. That would seem to indicate an issue in BIDS 2005 iteslf. Just posting this info as many places as I can recall visiting in the course of this odyssey. Maybe will save some other folks some heartache and gray hairs.

IndianaLMC wrote: I've been fussing with this a couple days now myself. The fix, quite simply really:In my particular case I install SQL 2005 as a seperate instance, so instead of http://localhost/reportserve mine was http://localhost/reportserve$SQL2005and that, in itself, was enough to break reporting services and query for the reporting serivces login again and again and again.So, where do you fix it:1. Open your project in SQL Server Business Intelligence Development Studio2. Select the project menu followed by the properties of the project.3. Change the TargetServerURL: To the appropriate path to your reportserver.if your still not sure ( hard to believe but I suppose... ) open your IIS manager, expand the default web site and spot your reporting services virtual dir.There you go ... what a pain in the ...Regards from Indianapolis Thanks it works for me

Well,I too have just experienced the issue mentioned. I hate to say how many entries I have read trying to sort out my particular issue. It is, in fact, the same as many others where I get the Reporting Services Login box. When I went to IIS and changed from version 1.1.4322 to 2.0.50727 under the ASP.NET tab of the ReportServer Properties dialog window, the reports started to publish with no problems. How long has ReportServer been out? I worked on this issue for an hour before thinking to check this and have not seen this solution in anything I have read. I can only hope that this will help someone else.

Works for me! Thanks Indianapolis!

The problem is that the ReportServer (whilst visible as an entry in IIS) is actually screwed up behind the scenes. The resolution is to un-install the Reporting Services component and then re-install. If you have SSRS on the same box as the SQL Server 2005 Management System you ought to be able to just un-install the SSRS bit.

Changing the TargetServerURL from http://hostServer/Reports to http://hostServer/ReportServer solved the problem. I had also added my Domain Login as an Admin User in Report Manager.

"The Web Service URL should be different from the Report Manager URL, and reports go in the Web Service URL".Just to verify, this is still an issue in VS & SSRS 2008. You'd think there'd be a knowledge base article by this time, at the very least.

Hi All, Here is the solution for it. Please go to reporting services configuration in configuration tools of MSSQL Server and configure Report server in it. and configure the webservices indentity in it. Thanks Pradeep Kumar

I've tried everything on this thread that applied (some didn't as they were already implemented), and nothing worked. Admittedly, I haven't tried all permutations and combinations of suggestions, and I haven't looked at .The problem disappeared after I uninstalled and reinstalled the SQL instance I'm working with. This was several days of frustration and delay ago. If I remember correctly, I did the uninstall/reinstall to restore my test/instruction machine to an uncompromised state after running the SQL scripts in SQL Server 2005 Reporting Services Step by Step. Running them generated a lot of errors, and I couldn't be certain of the competence of the sample database after running the scripts. I resolved that situation (after uninstall/reinstall, that is) by reading through the SQL script carefully, carefully considering the author's intend, and entering one or a few lines of SQL at a time. (Tangential thought: Don't MS Press's editors include fact checking in their workflow? I have twelve years of experience in tech pubs and thought that was part of the job responsibilities. Further, haven't they heard that the scripts don't work and corrected them? The book came out over two years ago. Oh, well.)I would have been okay, but I promoted my test/instruction machine to a domain controller, which seemed to be necessary to set up the database users properly (that is, converting Windows logins to database users, as the text seemed to require). After that, the problem of RS project deployment gratuitously requesting auser nameand password, and not accepting anyvalid user name, recurred.I may spend the time on another uninstall/reinstall cycle. Fortunately, I saved a printout of the corrected SQL code. But who has time to douninstall/reinstall repeatedly? And what sense does that make in a real-life development/production environment?Does anyone have any more suggestions? Someone on this thread mentioned getting help from Microsoft. How is that done, and who can do it? It's by email, I suppose.Daigoro

Solution lies in the Project Properties, Target Server URL.This URL by default will need to be the following:http://localhost/reportserverThis may have been altered during creation of the project.

Hi,Has anyone had any luck in resolving the login box which appears in SSRS?Sharon

Hi All, I just got the same problem with ssrs to deploy the reports to the report server, the problem for me is: I installed sql server 2005 with a name instance, and the report server url and report view site in the iis are all adding my instance name with a dollar sign something like reportserver$instance_name, so when I noticed this from iis and go back to my project property page and changed the target server url just like the one in iis, then everything worked fine, so make sure the report server url in your project property should be the same as the iis one, it is it.

I ended up having to use the IP address for the server, and the deploy now works for me.

Thanks a lot. I faced the same issue in SSRS 2008 and your suggestion fixed it.

As many people say in this thread You must change the "TargetServerURL" by clicking Right mouse button and"properties" on your solution in "Solution Explorer" in theSQL Server Business Intelligence Development Studio.in my case it was:http://myhostname/ReportServer_SQLEXPRESS(not working)and its working on:http://myhostname:80/ReportServer_SQLEXPRESSeventually You can just upload your reports from the web appfrom the same adressBTW This problem occurs in SQL Server 2008 also.

Hi all, I faced a similar problem SSRS 2008 when i was using Mozilla but when i tried it in IE there was no request for credentials and the report worked just fine but still this is not the solution i need a way to use it in Mozilla please help thanks

I was having same issue too. I found an article this explains why this happens, I think it is also depends on the configuration too but this solution worked for me and i am using SSRS 2005 http://blogs.msdn.com/lukaszp/archive/2008/03/26/solving-the-reporting-services-login-issue-in-the-february-ctp-of-sql-server-2008.aspx Hope this helps.Orhan Taskin

Hi,I was experiencing this issue - possibly for different reasons, possibly just being a numpty... butI thought id post this just in case it helps :)I was simply entering an incorrect 'TargetServerURL' when deploying/publishingMy instance was called : CUFFBERT-PC\SQLSERVER2008 however the url whichI had been entering as http://CUFFBERT-PC/SQLSERVER2008should have actually been http://CUFFBERT-PC/ReportServer_SQLSERVER2008Ifound this difference when I saw the URL property under the general tab of properties of my instance and can also be found in the Reporting Services Configuration ManagerGood Luck!

Solution for SQL Express 2008. Following the instructions from http://msdn.microsoft.com/en-us/library/ms160721.aspx I had the same problem as you all. The only solution that is working for is to change the TargetServerURL from http://localhost/reportserver$SQLExpress to http://localhost/reportserver_SQLExpress The dollar sign is now underscore.. Again, check your URL for very closely and you'll have your solution.

Thank you, Thank you Kelvinninh, you saved the day. That was the answer that worked for me. Ohhh what fun we have.

1. try to use "http://<servername>/ReportServer" instead of "http://localhost/ReportServer" in BIDS-Project-Properties-TargetServerURL. 2. Use admin right to start BIDS and RS ConfigurationManager.

Here is how I solved the issue. I had originally configuring Reporting Services on SQL Server 2005 SP2 and upgraded to SP3 at a later time. I noticed in the Reporting Services Configuration that the Database Setup had a red X and was no longer configured. I pointed it to the old ReportingServer database and clicked "Upgrade". Afterwards, I was able to deploy my script just fine. Hopefully this will help some others!

I have tried everything but still got nowhere. 1. I specified the BIDS(Visual Studio)-Project-Properties-TargetServerURL as http://servername/reportserver, I also tried http://localhost/reportserver. No luck. 2. I knew the specified URL exists. When I viewed through the browser, I got the message "Reporting Services Error----- The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing...." 3. This is an XP SP3 machine and I am using SQL2005 Dev edition. My account is the admin. 4. In the report service configuration tool, the Executive Account is green with my account (machinename\login). 5. I gave the "users" account full control over the two folders "C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager" and "C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer." This is not safe but it is for testing anyway. 6. I have rebooted my workstation. It is time for me to try it on another machine. Since I am new to SSRS, I wonder what this "deployment" does? If it simply builds some files and then copy over to the virtual directory, can I do it manually? Seaport

Hi, Thanks to suggestion. But really it was surprising for me.

Thanks for your suggestions

this helped me too !Ls

Hi All, you´re great Shujamughal :-) I had the same problem and solved with youre tip. Thanks! Bernd

Hi All, you´re great Shujamughal :-) I had the same problem and solved with youre tip. Thanks! Bernd

Hi all, I faced a similar problem SSRS 2008 when i was using Mozilla but when i tried it in IE there was no request for credentials and the report worked just fine but still this is not the solution i need a way to use it in Mozilla please help thanks I had same problem and thanks it works. Just to clerify that the problem is not the pop up window during deployment one. It's in fact after the depolyment and i tried to view reports from the target url and got pop window asking for login. I got this problem in Firefox and luckliy found this reply and tried in ie 7 and no problem at all.

Hi All, I wanted also to share with you info about the same error that I managed to sort out thanks to the number of different steps from this post. First I had to put http://servername/ReportServer$InstanceName it the Report properties. Then under the Configuration for the Report -->Windows service Identity I had my user name and pass, so I changed it to Local Service. Then in the Database Setup in the Database Connection I changed the server name to (LOCAL)\Instance - drop down menu. And then I can say it worked.... which step from above, I really do not know... honestly.... I hope it helps you as well...

This solution worked after all else failed. I'm on SQL Server 2008 R2 (Windows 7). The report would refuse to deploy (build had no errors) and would prompt for an unending userid/pw - this was on my own laptop of which I am admin. Thanks a LOT AmandaLynn!!!!!!!!!!!!! As a sidenote, http://localhost/reportserver was also giving me an authentication error which worked after I ran IE as administrator.

None of these solutions worked. I changed target URL from reports to reportserver. Now instead of popping up a username and login it told me that for my account (which is the administrator on the machine and is also added a administrator to the report server via report manager and is the execution account) "The permissions granted to user '<my account>' are insufficient for performing this operation." I checked everything in reporting server configuration. The report server virtual directory is in fact "ReportServer". I tried adding port 80 to the URL. No difference. I changed the execution to my admin account. Still no rights. Just for fun and giggles I changed the target URL to http://<servername>/ReportServer$SS2005RepServ (which is the instance name). Now the log in box came back. I promised my customer that they would lose nothing by switching to "SS 2005 Reporting Services" from "Web Focus". However I can not even get past first base. The moderators on the SharePoint forum have advised that no one views threads marked as answered, and if the indicated answer did not address your needs then you should start a new thread Edward R. Joell MCSD MCDBA

None of these solutions worked. I changed target URL from reports to reportserver. Now instead of popping up a username and login it told me that for my account (which is the administrator on the machine and is also added a administrator to the report server via report manager and is the execution account) "The permissions granted to user '<my account>' are insufficient for performing this operation." I checked everything in reporting server configuration. The report server virtual directory is in fact "ReportServer". I tried adding port 80 to the URL. No difference. I changed the execution to my admin account. Still no rights. Just for fun and giggles I changed the target URL to http://<servername>/ReportServer$SS2005RepServ (which is the instance name). Now the log in box came back. I promised my customer that they would lose nothing by switching to "SS 2005 Reporting Services" from "Web Focus". However I can not even get past first base. The moderators on the SharePoint forum have advised that no one views threads marked as answered, and if the indicated answer did not address your needs then you should start a new thread Edward R. Joell MCSD MCDBA

None of these solutions worked. I changed target URL from reports to reportserver. Now instead of popping up a username and login it told me that for my account (which is the administrator on the machine and is also added a administrator to the report server via report manager and is the execution account) "The permissions granted to user '<my account>' are insufficient for performing this operation." I checked everything in reporting server configuration. The report server virtual directory is in fact "ReportServer". I tried adding port 80 to the URL. No difference. I changed the execution to my admin account. Still no rights. Just for fun and giggles I changed the target URL to http://<servername>/ReportServer$SS2005RepServ (which is the instance name). Now the log in box came back. I promised my customer that they would lose nothing by switching to "SS 2005 Reporting Services" from "Web Focus". However I can not even get past first base. The moderators on the SharePoint forum have advised that no one views threads marked as answered, and if the indicated answer did not address your needs then you should start a new thread Therefore I have started a new thread at http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/51cacf35-aab3-487b-bbd2-9ada14e18199 Edward R. Joell MCSD MCDBA

None of these solutions worked. I changed target URL from reports to reportserver. Now instead of popping up a username and login it told me that for my account (which is the administrator on the machine and is also added a administrator to the report server via report manager and is the execution account) "The permissions granted to user '<my account>' are insufficient for performing this operation." I checked everything in reporting server configuration. The report server virtual directory is in fact "ReportServer". I tried adding port 80 to the URL. No difference. I changed the execution to my admin account. Still no rights. Just for fun and giggles I changed the target URL to http://<servername>/ReportServer$SS2005RepServ (which is the instance name). Now the log in box came back. I promised my customer that they would lose nothing by switching to "SS 2005 Reporting Services" from "Web Focus". However I can not even get past first base. The moderators on the SharePoint forum have advised that no one views threads marked as answered, and if the indicated answer did not address your needs then you should start a new thread Therefore I have started a new thread at http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/51cacf35-aab3-487b-bbd2-9ada14e18199 Edward R. Joell MCSD MCDBA

This worked for me as well. In Reporting Services config manager I changed my localhost to an actual IP address. Then in VS2008 under the Report Project Properties TargetURL, I used the IP address instead of localhost. Worked after this. Using SQL Server 2008 R2

Shawn_P's reply was definitively not a solution for me as the machine on which I am working does not have a static IP address. The resolution for was determined to be as follows from my other thread. In Report Manager it it not sufficient for the group to which you belong to be granted rights to Home even if the group is BuildIn\Administrators. You have to explicitly grant the individual user "Content Manager" rights on Home as well. Now the deployment was completed allegedly successfully according to Visual Studio. I was able to view the report in Report Manager. Since this question already has an answer, I fail to understand why New replies are being proposed as answers. Edward R. Joell MCSD MCDBA

I had same problem but after so many trials I figured it out that the targetserverurl will need to be the http://computername/reportserverdatabasename I changed it and fixed the problem

Another thing to try is to right-click on whatever program it is you're trying to test the report with and select "Run As Administrator." This works for me when I run either Firefox, IE, or Business Intelligence Design Studio. Ken

Opening the reportmanager in ie prompts me for username/pwd. Tho I'm able to deploy the report from BIDS. My ReportServicesConfiguration shows all green checks. My target server url is http://localhost/reportserver. I have anonymous access turned off in my website. My Database setup and Windows Identity is set to LocalSystem. I even tried all options mentioned in this thread. Any suggestions? Env : SQL2005/SSRS2005 SE on WinXP

I have three instances of SSRS on my machine, 2000, 2005, and 2008. For my SS 2005 instance the URL was reportserver. But for the 2008 I had to show the url as http://,servername./reportserver_SS2008. (This is despite the fact that the SSRS2008 was installed first.) The SS2008 is the name of the SS 2008 instance. The name of the reports database on that instance is ReportServer$SS2008. I would suggest appending an underscore and the name of your instance to the reportserver part of your URL and trying that. Logically you should not have to do that. But this is Microsoft. Edward R. Joell MCSD MCDBA

I have three instances of SSRS on my machine, 2000, 2005, and 2008. For my SS 2005 instance the URL was reportserver. But for the 2008 I had to show the url as http://,servername./reportserver_SS2008. (This is despite the fact that the SSRS2008 was installed first.) The SS2008 is the name of the SS 2008 instance. The name of the reports database on that instance is ReportServer$SS2008. I would suggest appending an underscore and the name of your instance to the reportserver part of your URL and trying that. Logically you should not have to do that. But this is Microsoft. Edward R. Joell MCSD MCDBA Update I read a MSDN article today (May 6) stating that the when setting up the virtual directory, the name should be set by default be set to be "ReportServer_<instance name where reportserver dB is located>" suggest finding reportserver database on you DBEngine instance and seeing what it's name is.

I think the idea is to ensure that SSRS Service is up & running.(Can do this from Server Status of SSRS Config manager ) Report Server Virtual Directory & Report Manager should be set up in SSRS Config manager with default settings. Windows Service identity should point to current user windows account. Webservice identity can be machinename\ASPNET Under Database set up of SSRS Config manager the server name should be LOCALHOST\Instance name (In my case LOCALHOST\SNPCSQL2005) and it should have a default database created with credentials pointing to current user windows account. Specify an execution account in SSRS Config manager pointing to current user Windows account. In BIDS,the TargetServerURL of the solution should be set to http:\\localhost\ReportServer. Then run the solution and it should not prompt for any id & password but shloud continue to run under the current Windows Identity and deploy the report This worked for me (Windows XP+SQL Server 2005).Hope it helps you get over this pain in the ass problem!