I found a solution. It may not ultimately work for Production, but it's a start. Here is what I did:
1) I added a LOCAL account to the IIS/Reporting Services machine (which, in this stage of the project's development, is my personal development workstation)
2) I granted that user membership to my machine's Administrators group
3) I added that user into Reporting Services Manager.
4) It worked!!
Thank you for your lead, crescendo. The ReportServer database stores information entered through the Reporting Services Manager. It's very simple to walk through, compared with how complicated most major Industry-released products tend to get. However, in this case walking through the DB was of little use.
I'm going to ask that this question be deleted. However, this solution may be useful for others, as I have seen the same question posted (and unanswered) in other places around the internet.
Jason
Main Topics
Browse All Topics





by: crescendoPosted on 2004-08-05 at 16:13:17ID: 11731667
It sounds like you need to add <machinename>\ASPNET to a role in the database(s) accessed by reporting services. Does Reporting Services have its own database? If so, start there. But you may need to give it permission to access other DBs and this could be a security risk.