Solved

Reporting Services on two servers without Domain

Posted on 2008-06-24
3
426 Views
Last Modified: 2008-08-18
SHORT:
I want to be able to install Microsoft SQL Server 2005 Reporting Services on two servers.

MY SETUP:
I have a three server setup without any domain server. A public frontend server, a backend server and a database server behind a firewall (not public). On the database server I have installed Microsoft SQL Server 2005 SP2 + Reporting Services. When using http://localhost/reports on the database server everything works fine. I can view and change the reports with sufficient rights.

WHAT I WANNA DO:
To be able to have the end user access the report services I have installed the reports web site on the frontend aswell. When I then use this http://mysite/reports I get prompted for username/password. If I use the username of the user of the database server I cannot login. This is obvious since that user is not known to the frontend. If I create a user on the frontend with the same name, I can log in but the Report Services complain that the user does not have enough rights to use the reporting services. Problem is that I cant create a frontend user on the database server.

SOLUTION NEEDED:
My idea now is to setup a domain controller and use a domain user instead. Problem about that is that this is a costly affair (hosting used is not cheap). But if its the only solution and if I can be sure it works thats what I gonna do.

I am hoping that some other solution can be presented here though :)

Thanks in advance
0
Comment
Question by:MadsNielsen
  • 2
3 Comments
 
LVL 18

Assisted Solution

by:chrismc
chrismc earned 50 total points
ID: 21859037
You should be able to set this up entirely in SQL and RS. You probably know a lot of this already so I apologise if that's the case
Make sure the security on the SQL Server is set to "Mixed mode".
Setting users in SQL is a two part process, you have to set up the "Logins" which gives permission to the access the Server. Then on the databases you setup the "User" that maps to a "Login". This is where you give the user specific rights to the database itself.

In Reporting services there are two seperate security areas. One is the datasource, the other is the reports themselves.
You can set the RS credentials either from Report Manager (the "FrontEnd") or the SQL Management Studio.
One of the security options is to "Prompt the user", I guess that's what you should use.
Also with the datasource, typically you might use a special account with read-only privileges to the data on that and just rely on authentication to the report this simplifies the security setup substantially. Just make sure you hide the datasources.

Well there are a few pointers!
0
 

Author Comment

by:MadsNielsen
ID: 21863861
Thanks for your reply chrismc. You at least gave me an idea on what to try. When I log in (with remote desktop) to the frontend server I am able to login to the database server (holdning the reporting services) with http://dbserver/reports and with database server windows user credentials. Then I tried to create a new role, hoping that I could create a role based on a frontend user. Funny thing is when I click on the OK button nothing happens. Also nothing happens when I try to edit an existing user.

All the SQL stuff you wrote about - I cant recognize at all. Maybe I misunderstood you. Let me state again that when I am logged in (with remote desktop) to the database server the Reporting Services are fully functional.
0
 

Accepted Solution

by:
MadsNielsen earned 0 total points
ID: 22221420
We finaly gave up and installed SQL Server on the frontend server aswell.
0

Featured Post

Backup Your Microsoft Windows Server®

Backup all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Join & Write a Comment

How to increase the row limit in Jasper Server.
In this article I will describe the Backup & Restore method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

708 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now