I'm fairly new to SSRS and have just gotten to the point of attempting to deploy my first project. However, on deployment, I repeatedly get a Reporting Services Login prompt thatrefuses to accept anything I enter. I've tried every combination of account/password I can think of and nothing seems to be taking. I have done a bit of research into this problem, and it seems fairly common. I've taken the suggested steps of insuring that the TargetServerURL is http://localhost/ReportServer. I've verified that my login has admin priviledges on the machine in question. I've tried tweaking permissions in IIS. I've tried an asssortment of execution accounts in the RS Configuration Manager. Nothing makes a bit of difference. The only other thing that seems a bit off is that, in the RS Config Manager, under database setup, I'm getting a yellow warning under Verifying Database Version, with a not that the current connection string is not valid. I know this issue has come up repeatedly, but so far none of the solutions I've seen have had much impact. Any ideas?

OK. After spending yesterday beating my head against this, I gave up and reinstalled Reporting Services. Happily, I no longer get the repeated login popup. Unhappily, now when I try to deploy,I'm getting a fairly cryptic error: keys lock row not found. I can't seem to find much of any reference to this anywhere. Has anyone experienced this before?

Seems that I've managed to figure this one out on my own. At some point in all of my messing about, I managed to wipe out and/or corrupt some of the data in the ReportServer database. Hence the cryptic keys lock row not found. Created new RS database and I'm back to getting errors that I can understand.

Hi, Did you find the fix to the problem.

We were using the wrong URL in our configuration properties for the TargetServerURL. It's confusing for the following reason: If you go to IIS on your report server, you will see two folders. In our case, they were: Reports05 and ReportServer05 We use: http://<servername>/Reports05 to bring up the report viewer in a browser, but when we deploy the reports, we must use the url: http://<servername>/ReportServer05 Hope this helps.Sophia Bunce

I am having the exactly the same problem. I have been trying to figure out the problem continuously for past 5 hours but nothing seems to work. Could anyone please help.