Locked out of Reporting Services - 2008r2

Question

Post reply

Locked out of Reporting Services - 2008r2

joelax-685671

SSC Veteran

Points: 285
More actions
June 21, 2012 at 1:52 pm

#392581

I have SQL Server installed on my local machine for development purposes. I'm the local admin of my machine etc, but I can't get into Reporting Services. When I bring up either the reporting server management url or the service url, I get a login screen, which after I enter my password, tells me I have insufficient rights. Any help would be appreciated.
Thanks,
Joe

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Rock from VbCity Hall of Fame Points: 3991 More actions · Answer 1

Hi Joelax, welcome to SQL ServerCentral 🙂

These posts may help you:

Could not deploy the reports on the report...

and

Can't deploy reports from BIDS to reporting...

Cheers,

Hope this helps,
Rock from VbCity

joelax-685671 SSC Veteran Points: 285 More actions · Answer 2

Thanks. But that wasn't the issue. I did find a post somewhere that had the solution. It has to do with an undocumented trick of typing //localhost/reports instead of //machinename/reports and then adding oneself as a content manager. I have no clue why that's necessary.

Brandie Tarvin SSC Guru Points: 173061 More actions · Answer 3

Content manager is necessary because SSRS, like the rest of the SQL Server tools, isn't going to allow a box admin to get into its data without someone saying the box admin can get into the data. It makes sense from a security standpoint if you think about it.

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

joelax-685671 SSC Veteran Points: 285 More actions · Answer 4

Thanks. But since it was me putting myself in as the content manager, it doesn't make sense. When I typed //machinename/reports, I was locked out, when I typed //localhost/reports, I was able to get in and add myself as content manager, after which it worked.

Also, this was straight after the install, and it turns out that it happened both on the SQL2008 install and the SQL2012 install. It might have something to do with the fact that this is on a dev environment and is on Windows 7 perhaps, but in any case, it's not expected behaviour.

I shouldn't have had to search for several hours to try to get into my own reporting services installation, if this is something that's necessary it should be part of the installation process.