April 3, 2007 at 10:35 am
Hi All:
I've been using RS with SQL2000 and vb.net 2003. I recently installed the 2005 tools to get used to the new management studio, and to get up to speed on building/deploying reports using it. I converted one project from vs2003 to 2005, and opened it within management studio to build a new report. All went fine, until I tried to deploy it from my desktop to a remote computer. I get a login dialog box repeatedly. MS has a KB article on it (KB 842517) saying it is fixed in the latest sp for RS 2000. I downloaded and installed it and rebooted the computer that runs RS, but it has not resolved the problem; ie no change in behavior.
The title of the KB is FIX: The Reporting Services Login dialog box appears repeatedly when you deploy a report on a remote computer by using Report Designer.
Does anybody have any experience with this. A search of the forum came up with no hits. Regards. D. Lewis
April 12, 2007 at 11:12 am
I have the exact same problem and I too reinstalled RS SP2, but it didn't fix the problem. Any help would be appreciated. Thanks.
December 7, 2007 at 6:50 am
Could be where you are trying to deploy to. I tried several deployments
localhost/reports
localhost/reporting
finally this one worked
localhost/reportserver
I think it depends on the configuration. I have no trouble is I log in using the console, but if it is just a standard login to a server using remote desktop, I need to have the correct deployment path.
Jamie
December 18, 2007 at 4:31 pm
I had the same problem which turned out to be caused by trying to deploy to SQL 2000 Server Reporting Services using VS 2005.
I got around this by deploying to a SQL 2005 Server, but I would have expected to be able to deploy to SQL 2000 from VS2005?
December 26, 2007 at 11:03 am
VS 2005 can be used to deploy reports to both RS2000 and RS2005.
The login prompts in this case may be coming from your webserver where the ReportServer virtual directory is hosted. We had a similar issue while upgrading from RS2000 to RS2005.
You can try the following.
1. Use basic authentication if you are deploying internally within your company.
2. To publish reports from Visual Studio, try using http://YourComputerName/ReportServer instead of http://localhost/ReportServer. This is particulary important if you are using https.
When Reporting Services is installed, there are hard coded reference to http://yourcomputername/ReportServer so ReportingService.asmx and ReportManager can function properly.
The redirection between the URLs may result in loss of credentials periodically.
I hope this helps.
December 28, 2007 at 8:50 am
I am experiencing the same issue. I'm trying to deploy a report to http://servername/ReportServer, I've given the Administrators group in SRS the Content Manager role, and I'm using my domain admin account, but nothing is getting me past the "Reporting Services Login" box. Basic authentication for the ReportServer virtual directory didn't work for me either.
Thanks-
January 1, 2008 at 4:18 pm
How about the Reports directory. Is that also set to Basic authentication?
Another point to watch for is the domain name in the credentials.
Make sure that you have given the ContentManager permission to "DOMAIN\group" or "DOMAIN\username". SSRS Authorization treats "username" different from "DOMAIN\username".
When you login at the prompt, provide you full username including the domain name.
June 23, 2008 at 7:36 pm
I depolyed to to ReportServer$SQL2005 and then opened
http:\localhost\Reports$sql2005 and it worked
February 23, 2012 at 9:55 am
SSRS 2008
The TargetServerURL in your project needs to be the same as the Web Service URL.
In your SSRS Project Properties
TargetServerURL: http://localhost/Reports$ROSS
Reporting Services Configuration Manager [Web Service URL]
Virtual Directory: Reports$ROSS
URL: http://{servername}/Reports$ROSS
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply