GerryAre you connected to the Database??
|||In IIS, try unchecking the option to allow anonymous access and then click the link logged in as the local administrator (or add yourself to the local admins). If that works add the other credentials to RS security. Let me know if this helps.
Showing posts with label security. Show all posts
Showing posts with label security. Show all posts
Wednesday, March 28, 2012
Reporting Services Access Problem
I have one problem that must deal with security and I have tried everything to no avail. Reporting Services is running fine, I can deploy, I can see the link to the report in the browser. When I click the link I get Access Denied. All my IIS settings are as RS set them during the install. I am the administrator of the computer. I have given full control to all the folders that I think RS needs. If anyone has a suggestion please reply, thank you
Reporting Services 2005 WMI documentation inccorect?
I have SQL Server 2005 + Reporting Services 2005 installed on a machine. I've
implemented Custom Forms Security Extension. When I run the code below I get
a WMI Exception "Not Found"? I think maybe I have the namespace or class name
wrong... The documentation has both "MSReportManager_ConfigurationSetting"
and "MSReportServerReportManager_ConfigurationSetting" but neither seem to
work. The only WMI class that works properly is "MSReportServer_Instance".
What am I doing wrong?
________________________________________________________
Nuno Pereira
ManagementScope scope = new
ManagementScope(@."\\localhost\root\Microsoft\SqlServer\ReportServer\v9");
scope.Connect();
ManagementPath path = new
ManagementPath("MSReportServerReportManager_ConfigurationSetting");
ObjectGetOptions options = new ObjectGetOptions();
ManagementClass serverClass = new ManagementClass(scope, path, options);
serverClass.Get(); // throws a "Not Found" error...
________________________________________________________________I am now encountering a similar problem as you. I am looking into the sample
provided by MS on Using Forms Authentication in Reporting Services (this is
in SQL2K) and trying to replicate it using SQL 2005 and VS2005.
But I have problems accessing the PathName property of
MSReportServer_ConfigurationSetting, which i need to point to the installed
path for the Report Server. Can any one help to explain more on this area?
Thanks for any assistance.
"Nuno" wrote:
> I have SQL Server 2005 + Reporting Services 2005 installed on a machine. I've
> implemented Custom Forms Security Extension. When I run the code below I get
> a WMI Exception "Not Found"? I think maybe I have the namespace or class name
> wrong... The documentation has both "MSReportManager_ConfigurationSetting"
> and "MSReportServerReportManager_ConfigurationSetting" but neither seem to
> work. The only WMI class that works properly is "MSReportServer_Instance".
> What am I doing wrong?
> ________________________________________________________
> Nuno Pereira
> ManagementScope scope = new
> ManagementScope(@."\\localhost\root\Microsoft\SqlServer\ReportServer\v9");
> scope.Connect();
> ManagementPath path = new
> ManagementPath("MSReportServerReportManager_ConfigurationSetting");
> ObjectGetOptions options = new ObjectGetOptions();
> ManagementClass serverClass = new ManagementClass(scope, path, options);
> serverClass.Get(); // throws a "Not Found" error...
> ________________________________________________________________
>
>|||I am also encountering similar problems trying to retrieve the RS Web Service
from the following constants in Utils.cs provided in the RS 2000 Forms
Authentication example:
// WMI constants
const string WmiNamespace =@."\\localhost\root\Microsoft\SqlServer\ReportingServices\v8";
const string WmiRSClass = @."MSReportServerReportManager_ConfigurationSetting";
I've had to hardcode the Web Service URL (server.Url = "https://<server
name>/reportserver/reportservice.asmx";) in my UILogon.aspx.cs file to make
it work but this obviously isn't a solution since we have multiple test and
production enviornments.
"ice" wrote:
> I am now encountering a similar problem as you. I am looking into the sample
> provided by MS on Using Forms Authentication in Reporting Services (this is
> in SQL2K) and trying to replicate it using SQL 2005 and VS2005.
> But I have problems accessing the PathName property of
> MSReportServer_ConfigurationSetting, which i need to point to the installed
> path for the Report Server. Can any one help to explain more on this area?
> Thanks for any assistance.
> "Nuno" wrote:
> > I have SQL Server 2005 + Reporting Services 2005 installed on a machine. I've
> > implemented Custom Forms Security Extension. When I run the code below I get
> > a WMI Exception "Not Found"? I think maybe I have the namespace or class name
> > wrong... The documentation has both "MSReportManager_ConfigurationSetting"
> > and "MSReportServerReportManager_ConfigurationSetting" but neither seem to
> > work. The only WMI class that works properly is "MSReportServer_Instance".
> >
> > What am I doing wrong?
> >
> > ________________________________________________________
> >
> > Nuno Pereira
> > ManagementScope scope = new
> > ManagementScope(@."\\localhost\root\Microsoft\SqlServer\ReportServer\v9");
> >
> > scope.Connect();
> >
> > ManagementPath path = new
> > ManagementPath("MSReportServerReportManager_ConfigurationSetting");
> > ObjectGetOptions options = new ObjectGetOptions();
> > ManagementClass serverClass = new ManagementClass(scope, path, options);
> >
> > serverClass.Get(); // throws a "Not Found" error...
> > ________________________________________________________________
> >
> >
> >|||Is anybody from Microsoft listening? What's the answer to this question? What
are the equivalent constants for RS 2005 that were documented in the RS 2000
security extension example?
// RS 2000 Code
// WMI constants
const string WmiNamespace = @."\\localhost\root\Microsoft\SqlServer\ReportingServices\v8";
const string WmiRSClass = @."MSReportServerReportManager_ConfigurationSetting";
"JSI" wrote:
> I am also encountering similar problems trying to retrieve the RS Web Service
> from the following constants in Utils.cs provided in the RS 2000 Forms
> Authentication example:
> // WMI constants
> const string WmiNamespace => @."\\localhost\root\Microsoft\SqlServer\ReportingServices\v8";
> const string WmiRSClass = @."MSReportServerReportManager_ConfigurationSetting";
> I've had to hardcode the Web Service URL (server.Url = "https://<server
> name>/reportserver/reportservice.asmx";) in my UILogon.aspx.cs file to make
> it work but this obviously isn't a solution since we have multiple test and
> production enviornments.
> "ice" wrote:
> > I am now encountering a similar problem as you. I am looking into the sample
> > provided by MS on Using Forms Authentication in Reporting Services (this is
> > in SQL2K) and trying to replicate it using SQL 2005 and VS2005.
> >
> > But I have problems accessing the PathName property of
> > MSReportServer_ConfigurationSetting, which i need to point to the installed
> > path for the Report Server. Can any one help to explain more on this area?
> >
> > Thanks for any assistance.
> >
> > "Nuno" wrote:
> >
> > > I have SQL Server 2005 + Reporting Services 2005 installed on a machine. I've
> > > implemented Custom Forms Security Extension. When I run the code below I get
> > > a WMI Exception "Not Found"? I think maybe I have the namespace or class name
> > > wrong... The documentation has both "MSReportManager_ConfigurationSetting"
> > > and "MSReportServerReportManager_ConfigurationSetting" but neither seem to
> > > work. The only WMI class that works properly is "MSReportServer_Instance".
> > >
> > > What am I doing wrong?
> > >
> > > ________________________________________________________
> > >
> > > Nuno Pereira
> > > ManagementScope scope = new
> > > ManagementScope(@."\\localhost\root\Microsoft\SqlServer\ReportServer\v9");
> > >
> > > scope.Connect();
> > >
> > > ManagementPath path = new
> > > ManagementPath("MSReportServerReportManager_ConfigurationSetting");
> > > ObjectGetOptions options = new ObjectGetOptions();
> > > ManagementClass serverClass = new ManagementClass(scope, path, options);
> > >
> > > serverClass.Get(); // throws a "Not Found" error...
> > > ________________________________________________________________
> > >
> > >
> > >|||For those of you who are still looking for the answer. The namespace in sql server 2005 is: "\\localhost\root\Microsoft\SqlServer\ReportServer\v9\Admin" while the class for report manager instance is: "MSReportManager_ConfigurationSetting". For more details please refer to: http://msdn2.microsoft.com/en-us/library/ms153571.aspx
From http://www.developmentnow.com/g/115_2006_2_0_0_693931/Reporting-Services-2005-WMI-documentation-inccorect.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com
implemented Custom Forms Security Extension. When I run the code below I get
a WMI Exception "Not Found"? I think maybe I have the namespace or class name
wrong... The documentation has both "MSReportManager_ConfigurationSetting"
and "MSReportServerReportManager_ConfigurationSetting" but neither seem to
work. The only WMI class that works properly is "MSReportServer_Instance".
What am I doing wrong?
________________________________________________________
Nuno Pereira
ManagementScope scope = new
ManagementScope(@."\\localhost\root\Microsoft\SqlServer\ReportServer\v9");
scope.Connect();
ManagementPath path = new
ManagementPath("MSReportServerReportManager_ConfigurationSetting");
ObjectGetOptions options = new ObjectGetOptions();
ManagementClass serverClass = new ManagementClass(scope, path, options);
serverClass.Get(); // throws a "Not Found" error...
________________________________________________________________I am now encountering a similar problem as you. I am looking into the sample
provided by MS on Using Forms Authentication in Reporting Services (this is
in SQL2K) and trying to replicate it using SQL 2005 and VS2005.
But I have problems accessing the PathName property of
MSReportServer_ConfigurationSetting, which i need to point to the installed
path for the Report Server. Can any one help to explain more on this area?
Thanks for any assistance.
"Nuno" wrote:
> I have SQL Server 2005 + Reporting Services 2005 installed on a machine. I've
> implemented Custom Forms Security Extension. When I run the code below I get
> a WMI Exception "Not Found"? I think maybe I have the namespace or class name
> wrong... The documentation has both "MSReportManager_ConfigurationSetting"
> and "MSReportServerReportManager_ConfigurationSetting" but neither seem to
> work. The only WMI class that works properly is "MSReportServer_Instance".
> What am I doing wrong?
> ________________________________________________________
> Nuno Pereira
> ManagementScope scope = new
> ManagementScope(@."\\localhost\root\Microsoft\SqlServer\ReportServer\v9");
> scope.Connect();
> ManagementPath path = new
> ManagementPath("MSReportServerReportManager_ConfigurationSetting");
> ObjectGetOptions options = new ObjectGetOptions();
> ManagementClass serverClass = new ManagementClass(scope, path, options);
> serverClass.Get(); // throws a "Not Found" error...
> ________________________________________________________________
>
>|||I am also encountering similar problems trying to retrieve the RS Web Service
from the following constants in Utils.cs provided in the RS 2000 Forms
Authentication example:
// WMI constants
const string WmiNamespace =@."\\localhost\root\Microsoft\SqlServer\ReportingServices\v8";
const string WmiRSClass = @."MSReportServerReportManager_ConfigurationSetting";
I've had to hardcode the Web Service URL (server.Url = "https://<server
name>/reportserver/reportservice.asmx";) in my UILogon.aspx.cs file to make
it work but this obviously isn't a solution since we have multiple test and
production enviornments.
"ice" wrote:
> I am now encountering a similar problem as you. I am looking into the sample
> provided by MS on Using Forms Authentication in Reporting Services (this is
> in SQL2K) and trying to replicate it using SQL 2005 and VS2005.
> But I have problems accessing the PathName property of
> MSReportServer_ConfigurationSetting, which i need to point to the installed
> path for the Report Server. Can any one help to explain more on this area?
> Thanks for any assistance.
> "Nuno" wrote:
> > I have SQL Server 2005 + Reporting Services 2005 installed on a machine. I've
> > implemented Custom Forms Security Extension. When I run the code below I get
> > a WMI Exception "Not Found"? I think maybe I have the namespace or class name
> > wrong... The documentation has both "MSReportManager_ConfigurationSetting"
> > and "MSReportServerReportManager_ConfigurationSetting" but neither seem to
> > work. The only WMI class that works properly is "MSReportServer_Instance".
> >
> > What am I doing wrong?
> >
> > ________________________________________________________
> >
> > Nuno Pereira
> > ManagementScope scope = new
> > ManagementScope(@."\\localhost\root\Microsoft\SqlServer\ReportServer\v9");
> >
> > scope.Connect();
> >
> > ManagementPath path = new
> > ManagementPath("MSReportServerReportManager_ConfigurationSetting");
> > ObjectGetOptions options = new ObjectGetOptions();
> > ManagementClass serverClass = new ManagementClass(scope, path, options);
> >
> > serverClass.Get(); // throws a "Not Found" error...
> > ________________________________________________________________
> >
> >
> >|||Is anybody from Microsoft listening? What's the answer to this question? What
are the equivalent constants for RS 2005 that were documented in the RS 2000
security extension example?
// RS 2000 Code
// WMI constants
const string WmiNamespace = @."\\localhost\root\Microsoft\SqlServer\ReportingServices\v8";
const string WmiRSClass = @."MSReportServerReportManager_ConfigurationSetting";
"JSI" wrote:
> I am also encountering similar problems trying to retrieve the RS Web Service
> from the following constants in Utils.cs provided in the RS 2000 Forms
> Authentication example:
> // WMI constants
> const string WmiNamespace => @."\\localhost\root\Microsoft\SqlServer\ReportingServices\v8";
> const string WmiRSClass = @."MSReportServerReportManager_ConfigurationSetting";
> I've had to hardcode the Web Service URL (server.Url = "https://<server
> name>/reportserver/reportservice.asmx";) in my UILogon.aspx.cs file to make
> it work but this obviously isn't a solution since we have multiple test and
> production enviornments.
> "ice" wrote:
> > I am now encountering a similar problem as you. I am looking into the sample
> > provided by MS on Using Forms Authentication in Reporting Services (this is
> > in SQL2K) and trying to replicate it using SQL 2005 and VS2005.
> >
> > But I have problems accessing the PathName property of
> > MSReportServer_ConfigurationSetting, which i need to point to the installed
> > path for the Report Server. Can any one help to explain more on this area?
> >
> > Thanks for any assistance.
> >
> > "Nuno" wrote:
> >
> > > I have SQL Server 2005 + Reporting Services 2005 installed on a machine. I've
> > > implemented Custom Forms Security Extension. When I run the code below I get
> > > a WMI Exception "Not Found"? I think maybe I have the namespace or class name
> > > wrong... The documentation has both "MSReportManager_ConfigurationSetting"
> > > and "MSReportServerReportManager_ConfigurationSetting" but neither seem to
> > > work. The only WMI class that works properly is "MSReportServer_Instance".
> > >
> > > What am I doing wrong?
> > >
> > > ________________________________________________________
> > >
> > > Nuno Pereira
> > > ManagementScope scope = new
> > > ManagementScope(@."\\localhost\root\Microsoft\SqlServer\ReportServer\v9");
> > >
> > > scope.Connect();
> > >
> > > ManagementPath path = new
> > > ManagementPath("MSReportServerReportManager_ConfigurationSetting");
> > > ObjectGetOptions options = new ObjectGetOptions();
> > > ManagementClass serverClass = new ManagementClass(scope, path, options);
> > >
> > > serverClass.Get(); // throws a "Not Found" error...
> > > ________________________________________________________________
> > >
> > >
> > >|||For those of you who are still looking for the answer. The namespace in sql server 2005 is: "\\localhost\root\Microsoft\SqlServer\ReportServer\v9\Admin" while the class for report manager instance is: "MSReportManager_ConfigurationSetting". For more details please refer to: http://msdn2.microsoft.com/en-us/library/ms153571.aspx
From http://www.developmentnow.com/g/115_2006_2_0_0_693931/Reporting-Services-2005-WMI-documentation-inccorect.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com
Monday, March 26, 2012
Reporting Services 2005 - Security Extention
Hi,
I have compiled the security extension sample code that comes with the installation and I was able to successfully deploy it on the Reporting Server. Now my server asks me for username, password when browse to the http://servername/reports folder. I have configured one user as say "AdminUser".
When I login as AdminUser, I am to see all my reports and browse thru them.
I created one more user say "RegUser". I have logged in as AdminUser and I have give permissions to RegUser for some folders on report server.
Until this point every thing just worked fine and absolutly no problems.
The real problem shows up when the "RegUser" logs in to the system. He is able to login, but he cannot see any thing on the Home Page. Even though I have give permission to this RegUser, he is not able to see his folders.
If any body has solved this problem before or had any idea whats going on... please throw me an idea.
Thanks in advance.
Giri
What permission did you give him ? make sure that he is on the group of systeusers in Reporting Services, otherwise he won′t be able to see anything on the report server.HTH, Jens Suessmeyer.
http://www.sqlserver2005.de|||
I have given him the role "Browser" to a particular folder, but that is not helping me out.
Are you talking about giving setup in of the config files?
Reporting Services 2000 web-services rendering
We are using Reporting Services 2000 and we have a project in which we need to implement a security layer in a customized ASP.NET application to authenticate and authorize requests to view reports.
The client's needs are secure / restricted access via the public internet, all requests must go through the ASP.NET application (the report server URL must NEVER be visible) and the client must be able to print the report using the special ActiveX print plug-in for the reports (otherwise the Internet Explorer print functionality will seriously mess up the output)
There are two approaches we have considered with pros and cons:
a.) render the report using the ReportViewer control. The problem is, this control is just a wrapper around query-based accessing of the Report Server. This exposes the RS URL and ultimately, the resulting HTML from the RS will have SRC tags that expose the Report Server. The advantage is the client retains full functionality that the default rendering interface of RS would ordinarily have.
b.) render the report programmatically using the SOAP web service and render each individual stream. The problem with this is the development is far more difficult and we lose the customized printing functionality of the ActiveX control
We are proposing to use a variation of option a.) by having our ASP.NET page delegate a request via a HttpRequest object to the Report Server and then performing either a regex or XSLT transformation on the returned stream to replace all SRC tags to a resource into a redirect to an ASP.NET page that will be parameterized by the streamid of a report resource. This page would simply return the result as a byte stream. This would keep all the work server-side and never expose the server URL. This way we preserve the Report Server interface (and the precious print functionality) while masking the URLs.
There must be a simpler approach than the one I have described. Can anyone come up with a solution that will fulfill our requirements? Will Reporting Services 2005 fix this?
At the very least, is there a way to control the printing (without exporting to PDF) when using the web service API to render the report programmatically?|||I did something similar where we used the MeadCo ScriptX print control to modify some basic print settings (like margin, page setup, and header and footers). Just need to add a script block to the end of the rendered html to modify the print settings.|||There is no better approach to solve the problem in RS 2000. Actually, there is still a flaw in your approach if the report contains drillthrough report (hyperlink to other reports) or subreport, it will still reveal the URL of the report server to the customer.
In RS2005, this problem is solved by the new ReportViewer control. You may get more information about the newly introduced in ReportViewer via the following website:
www.gotreportviewer.com
Reporting services 2000 security
Hi folks,
I have been charged with the task of providing some security measures for
reporting services 2000 and unfortuneately I have found myself a bit out of
my depth (usually I am found developing desktop applications), I am
comfortable with any c# coding required but I'm finding the whole thing
rather confusing.
Our setup consists of a webserver and reporting server (on different domains
at the moment) We have a website that works as we wish, displaying a list
of reports based on the users logon details. However we have found tht the
reporting server can be accessed directly and with a bit of playing around
anyone can view (often sensitive) information.
The current site is written in ASP (not .NET), is it possible to 'wrap' the
existing site in an asp.net form so that we can use forms authentication
providing the necessary security to plug the hole?
To maintian useability we require the dropdowns for parameters provided by
URL addressability, so would we need to move the reporting server onto the
webserver so that it would have the same domain?
Any tips or links would be very much appreciated - I feel like a fish out of
water at the moment :)
Regards
Darren SimCrossing domains is an issue.
Assuming on the same domain you should be able to assign domain users or
domain groups to appropriate roles in RS. If they have been assigned
appropriately then they should not be able to see or run reports they
shouldn't. The way it works is that security starts with whatever roles have
been assigned to the home directory/folder in report manager. All
report/folders inherit from this. You can override at either the folder
level or the report level. For instance, if there is folder that only
management should see the reports then in Report Manager remove the group
for browsing for that folder and add one that is just the managers. You can
also do this for individual reports. My guess is that no-one understood how
roles are used to secure the website. Regardless of whether you integrate
this in with your web app, you need to understand this.
Yes you can integrate in your own authentication, many people have. It is
non-trivial but doable. However, if you have it on the same server as your
web app then you can use integrated security, it will know who is connected
to your web app and they will only be able to view the appropriate reports.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Darren Sim" <darrens@.sirius.co.uk> wrote in message
news:%234FzKGhSHHA.4756@.TK2MSFTNGP06.phx.gbl...
> Hi folks,
> I have been charged with the task of providing some security measures for
> reporting services 2000 and unfortuneately I have found myself a bit out
> of my depth (usually I am found developing desktop applications), I am
> comfortable with any c# coding required but I'm finding the whole thing
> rather confusing.
> Our setup consists of a webserver and reporting server (on different
> domains at the moment) We have a website that works as we wish,
> displaying a list of reports based on the users logon details. However we
> have found tht the reporting server can be accessed directly and with a
> bit of playing around anyone can view (often sensitive) information.
> The current site is written in ASP (not .NET), is it possible to 'wrap'
> the existing site in an asp.net form so that we can use forms
> authentication providing the necessary security to plug the hole?
> To maintian useability we require the dropdowns for parameters provided by
> URL addressability, so would we need to move the reporting server onto
> the webserver so that it would have the same domain?
> Any tips or links would be very much appreciated - I feel like a fish out
> of water at the moment :)
> Regards
> Darren Sim
>|||Thanks Bruce your help is much appreciated,
Just to clarify, at the moment our web app accepts a login from a user then
checks the details against a database, the returned values determine which
reports are made available and the links to these are then displayed on a
page.
If we were to move the reporting server onto our web server, would it just
be a case of turning on integrated security on the report server?
Thanks again
Darren
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%235q3hphSHHA.4632@.TK2MSFTNGP04.phx.gbl...
> Crossing domains is an issue.
> Assuming on the same domain you should be able to assign domain users or
> domain groups to appropriate roles in RS. If they have been assigned
> appropriately then they should not be able to see or run reports they
> shouldn't. The way it works is that security starts with whatever roles
> have been assigned to the home directory/folder in report manager. All
> report/folders inherit from this. You can override at either the folder
> level or the report level. For instance, if there is folder that only
> management should see the reports then in Report Manager remove the group
> for browsing for that folder and add one that is just the managers. You
> can also do this for individual reports. My guess is that no-one
> understood how roles are used to secure the website. Regardless of whether
> you integrate this in with your web app, you need to understand this.
> Yes you can integrate in your own authentication, many people have. It is
> non-trivial but doable. However, if you have it on the same server as your
> web app then you can use integrated security, it will know who is
> connected to your web app and they will only be able to view the
> appropriate reports.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Darren Sim" <darrens@.sirius.co.uk> wrote in message
> news:%234FzKGhSHHA.4756@.TK2MSFTNGP06.phx.gbl...
>> Hi folks,
>> I have been charged with the task of providing some security measures for
>> reporting services 2000 and unfortuneately I have found myself a bit out
>> of my depth (usually I am found developing desktop applications), I am
>> comfortable with any c# coding required but I'm finding the whole thing
>> rather confusing.
>> Our setup consists of a webserver and reporting server (on different
>> domains at the moment) We have a website that works as we wish,
>> displaying a list of reports based on the users logon details. However
>> we have found tht the reporting server can be accessed directly and with
>> a bit of playing around anyone can view (often sensitive) information.
>> The current site is written in ASP (not .NET), is it possible to 'wrap'
>> the existing site in an asp.net form so that we can use forms
>> authentication providing the necessary security to plug the hole?
>> To maintian useability we require the dropdowns for parameters provided
>> by URL addressability, so would we need to move the reporting server
>> onto the webserver so that it would have the same domain?
>> Any tips or links would be very much appreciated - I feel like a fish out
>> of water at the moment :)
>> Regards
>> Darren Sim
>|||Well, it sounds like your web app is not using integrated security. There
are two steps to security. One is authenticating who the user is. That can
be done with forms authentication (in which case you integrate in the
authentication from your web app with RS). Then the other is roles. If you
don't do the roles then the user can go directly to Report Manager web site
and get whatever report they want. So regardless of how you decide to
authenticate you need to still understand and use roles in RS.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Darren Sim" <darrens@.sirius.co.uk> wrote in message
news:uPcxjxpSHHA.3948@.TK2MSFTNGP05.phx.gbl...
> Thanks Bruce your help is much appreciated,
> Just to clarify, at the moment our web app accepts a login from a user
> then checks the details against a database, the returned values determine
> which reports are made available and the links to these are then displayed
> on a page.
> If we were to move the reporting server onto our web server, would it just
> be a case of turning on integrated security on the report server?
> Thanks again
> Darren
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%235q3hphSHHA.4632@.TK2MSFTNGP04.phx.gbl...
>> Crossing domains is an issue.
>> Assuming on the same domain you should be able to assign domain users or
>> domain groups to appropriate roles in RS. If they have been assigned
>> appropriately then they should not be able to see or run reports they
>> shouldn't. The way it works is that security starts with whatever roles
>> have been assigned to the home directory/folder in report manager. All
>> report/folders inherit from this. You can override at either the folder
>> level or the report level. For instance, if there is folder that only
>> management should see the reports then in Report Manager remove the group
>> for browsing for that folder and add one that is just the managers. You
>> can also do this for individual reports. My guess is that no-one
>> understood how roles are used to secure the website. Regardless of
>> whether you integrate this in with your web app, you need to understand
>> this.
>> Yes you can integrate in your own authentication, many people have. It is
>> non-trivial but doable. However, if you have it on the same server as
>> your web app then you can use integrated security, it will know who is
>> connected to your web app and they will only be able to view the
>> appropriate reports.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Darren Sim" <darrens@.sirius.co.uk> wrote in message
>> news:%234FzKGhSHHA.4756@.TK2MSFTNGP06.phx.gbl...
>> Hi folks,
>> I have been charged with the task of providing some security measures
>> for reporting services 2000 and unfortuneately I have found myself a bit
>> out of my depth (usually I am found developing desktop applications), I
>> am comfortable with any c# coding required but I'm finding the whole
>> thing rather confusing.
>> Our setup consists of a webserver and reporting server (on different
>> domains at the moment) We have a website that works as we wish,
>> displaying a list of reports based on the users logon details. However
>> we have found tht the reporting server can be accessed directly and with
>> a bit of playing around anyone can view (often sensitive) information.
>> The current site is written in ASP (not .NET), is it possible to 'wrap'
>> the existing site in an asp.net form so that we can use forms
>> authentication providing the necessary security to plug the hole?
>> To maintian useability we require the dropdowns for parameters provided
>> by URL addressability, so would we need to move the reporting server
>> onto the webserver so that it would have the same domain?
>> Any tips or links would be very much appreciated - I feel like a fish
>> out of water at the moment :)
>> Regards
>> Darren Sim
>>
>|||Thanks again Bruce
You are quite correct - the website set up for viewing reports does not use
integrated security. I have been looking at integrating forms
authentication, but hit a few snags - I think most of the problems are
simply down to a poor understanding of the RS configfiles and what needs to
be done.
We are also moving the reporting services on to the web server to address
the domain issue - I have been thinking of redoing the login page in .NET to
handle forms security, if the login has been successful then allow the user
to proceed to the current site.
At the moment I am using VS2005 and .NET 2.0 for desktop applications, for
RS200 do I neet to use .NET1.1 and VS2003? (I have access to both)
I will read up on roles to get a better understanding of what needs to be
done to enchance security.
Kind regards
Darren Sim
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:e9k5iLuSHHA.1228@.TK2MSFTNGP06.phx.gbl...
> Well, it sounds like your web app is not using integrated security. There
> are two steps to security. One is authenticating who the user is. That can
> be done with forms authentication (in which case you integrate in the
> authentication from your web app with RS). Then the other is roles. If you
> don't do the roles then the user can go directly to Report Manager web
> site and get whatever report they want. So regardless of how you decide to
> authenticate you need to still understand and use roles in RS.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>|||Yes, RS 2000 is a 1.1 application. If your web site is 2.0 it can also run
1.1 for the RS websites.
As a 1.1 application you need to install VS 2003 and then install the report
designer.
If at all possible I would look at upgrading to RS 2005. It uses 2.0. It is
faster and has some important features (end user sorting, multi-select
parameters, calendar control to name a few).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Darren Sim" <darrens@.sirius.co.uk> wrote in message
news:%23caBKv3SHHA.1200@.TK2MSFTNGP04.phx.gbl...
> Thanks again Bruce
> You are quite correct - the website set up for viewing reports does not
> use integrated security. I have been looking at integrating forms
> authentication, but hit a few snags - I think most of the problems are
> simply down to a poor understanding of the RS configfiles and what needs
> to be done.
> We are also moving the reporting services on to the web server to address
> the domain issue - I have been thinking of redoing the login page in .NET
> to handle forms security, if the login has been successful then allow the
> user to proceed to the current site.
> At the moment I am using VS2005 and .NET 2.0 for desktop applications, for
> RS200 do I neet to use .NET1.1 and VS2003? (I have access to both)
> I will read up on roles to get a better understanding of what needs to be
> done to enchance security.
> Kind regards
> Darren Sim
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:e9k5iLuSHHA.1228@.TK2MSFTNGP06.phx.gbl...
>> Well, it sounds like your web app is not using integrated security. There
>> are two steps to security. One is authenticating who the user is. That
>> can be done with forms authentication (in which case you integrate in the
>> authentication from your web app with RS). Then the other is roles. If
>> you don't do the roles then the user can go directly to Report Manager
>> web site and get whatever report they want. So regardless of how you
>> decide to authenticate you need to still understand and use roles in RS.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>|||We are upgrading to sql 2005 and RS2005. This is only to act as a stop-gap
until this can be properly planned and carried out as having the reporting
server accessible by anyone obviously poses a security threat.
Unfortuneately this security hole was only discovered at the last minute
before making the service available to our clients. I have only been here
for 6 months and I'm pushing for all developement to be on the .net 2.0
framework, as I use this for the desktop applications and some of the code I
am using could be reused in the web applications. However we are a very
small operation and getting everyone up to speed takes time, not to mention
the task of doing everything over...
Thanks very much for your assistance Bruce, I think I have an idea of at
least where to begin.
Regards
Darren
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:OqLkrJ4SHHA.4632@.TK2MSFTNGP04.phx.gbl...
> Yes, RS 2000 is a 1.1 application. If your web site is 2.0 it can also run
> 1.1 for the RS websites.
> As a 1.1 application you need to install VS 2003 and then install the
> report designer.
> If at all possible I would look at upgrading to RS 2005. It uses 2.0. It
> is faster and has some important features (end user sorting, multi-select
> parameters, calendar control to name a few).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Darren Sim" <darrens@.sirius.co.uk> wrote in message
> news:%23caBKv3SHHA.1200@.TK2MSFTNGP04.phx.gbl...
>> Thanks again Bruce
>> You are quite correct - the website set up for viewing reports does not
>> use integrated security. I have been looking at integrating forms
>> authentication, but hit a few snags - I think most of the problems are
>> simply down to a poor understanding of the RS configfiles and what needs
>> to be done.
>> We are also moving the reporting services on to the web server to address
>> the domain issue - I have been thinking of redoing the login page in .NET
>> to handle forms security, if the login has been successful then allow the
>> user to proceed to the current site.
>> At the moment I am using VS2005 and .NET 2.0 for desktop applications,
>> for RS200 do I neet to use .NET1.1 and VS2003? (I have access to both)
>> I will read up on roles to get a better understanding of what needs to be
>> done to enchance security.
>> Kind regards
>> Darren Sim
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:e9k5iLuSHHA.1228@.TK2MSFTNGP06.phx.gbl...
>> Well, it sounds like your web app is not using integrated security.
>> There are two steps to security. One is authenticating who the user is.
>> That can be done with forms authentication (in which case you integrate
>> in the authentication from your web app with RS). Then the other is
>> roles. If you don't do the roles then the user can go directly to Report
>> Manager web site and get whatever report they want. So regardless of how
>> you decide to authenticate you need to still understand and use roles in
>> RS.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>sql
I have been charged with the task of providing some security measures for
reporting services 2000 and unfortuneately I have found myself a bit out of
my depth (usually I am found developing desktop applications), I am
comfortable with any c# coding required but I'm finding the whole thing
rather confusing.
Our setup consists of a webserver and reporting server (on different domains
at the moment) We have a website that works as we wish, displaying a list
of reports based on the users logon details. However we have found tht the
reporting server can be accessed directly and with a bit of playing around
anyone can view (often sensitive) information.
The current site is written in ASP (not .NET), is it possible to 'wrap' the
existing site in an asp.net form so that we can use forms authentication
providing the necessary security to plug the hole?
To maintian useability we require the dropdowns for parameters provided by
URL addressability, so would we need to move the reporting server onto the
webserver so that it would have the same domain?
Any tips or links would be very much appreciated - I feel like a fish out of
water at the moment :)
Regards
Darren SimCrossing domains is an issue.
Assuming on the same domain you should be able to assign domain users or
domain groups to appropriate roles in RS. If they have been assigned
appropriately then they should not be able to see or run reports they
shouldn't. The way it works is that security starts with whatever roles have
been assigned to the home directory/folder in report manager. All
report/folders inherit from this. You can override at either the folder
level or the report level. For instance, if there is folder that only
management should see the reports then in Report Manager remove the group
for browsing for that folder and add one that is just the managers. You can
also do this for individual reports. My guess is that no-one understood how
roles are used to secure the website. Regardless of whether you integrate
this in with your web app, you need to understand this.
Yes you can integrate in your own authentication, many people have. It is
non-trivial but doable. However, if you have it on the same server as your
web app then you can use integrated security, it will know who is connected
to your web app and they will only be able to view the appropriate reports.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Darren Sim" <darrens@.sirius.co.uk> wrote in message
news:%234FzKGhSHHA.4756@.TK2MSFTNGP06.phx.gbl...
> Hi folks,
> I have been charged with the task of providing some security measures for
> reporting services 2000 and unfortuneately I have found myself a bit out
> of my depth (usually I am found developing desktop applications), I am
> comfortable with any c# coding required but I'm finding the whole thing
> rather confusing.
> Our setup consists of a webserver and reporting server (on different
> domains at the moment) We have a website that works as we wish,
> displaying a list of reports based on the users logon details. However we
> have found tht the reporting server can be accessed directly and with a
> bit of playing around anyone can view (often sensitive) information.
> The current site is written in ASP (not .NET), is it possible to 'wrap'
> the existing site in an asp.net form so that we can use forms
> authentication providing the necessary security to plug the hole?
> To maintian useability we require the dropdowns for parameters provided by
> URL addressability, so would we need to move the reporting server onto
> the webserver so that it would have the same domain?
> Any tips or links would be very much appreciated - I feel like a fish out
> of water at the moment :)
> Regards
> Darren Sim
>|||Thanks Bruce your help is much appreciated,
Just to clarify, at the moment our web app accepts a login from a user then
checks the details against a database, the returned values determine which
reports are made available and the links to these are then displayed on a
page.
If we were to move the reporting server onto our web server, would it just
be a case of turning on integrated security on the report server?
Thanks again
Darren
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%235q3hphSHHA.4632@.TK2MSFTNGP04.phx.gbl...
> Crossing domains is an issue.
> Assuming on the same domain you should be able to assign domain users or
> domain groups to appropriate roles in RS. If they have been assigned
> appropriately then they should not be able to see or run reports they
> shouldn't. The way it works is that security starts with whatever roles
> have been assigned to the home directory/folder in report manager. All
> report/folders inherit from this. You can override at either the folder
> level or the report level. For instance, if there is folder that only
> management should see the reports then in Report Manager remove the group
> for browsing for that folder and add one that is just the managers. You
> can also do this for individual reports. My guess is that no-one
> understood how roles are used to secure the website. Regardless of whether
> you integrate this in with your web app, you need to understand this.
> Yes you can integrate in your own authentication, many people have. It is
> non-trivial but doable. However, if you have it on the same server as your
> web app then you can use integrated security, it will know who is
> connected to your web app and they will only be able to view the
> appropriate reports.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Darren Sim" <darrens@.sirius.co.uk> wrote in message
> news:%234FzKGhSHHA.4756@.TK2MSFTNGP06.phx.gbl...
>> Hi folks,
>> I have been charged with the task of providing some security measures for
>> reporting services 2000 and unfortuneately I have found myself a bit out
>> of my depth (usually I am found developing desktop applications), I am
>> comfortable with any c# coding required but I'm finding the whole thing
>> rather confusing.
>> Our setup consists of a webserver and reporting server (on different
>> domains at the moment) We have a website that works as we wish,
>> displaying a list of reports based on the users logon details. However
>> we have found tht the reporting server can be accessed directly and with
>> a bit of playing around anyone can view (often sensitive) information.
>> The current site is written in ASP (not .NET), is it possible to 'wrap'
>> the existing site in an asp.net form so that we can use forms
>> authentication providing the necessary security to plug the hole?
>> To maintian useability we require the dropdowns for parameters provided
>> by URL addressability, so would we need to move the reporting server
>> onto the webserver so that it would have the same domain?
>> Any tips or links would be very much appreciated - I feel like a fish out
>> of water at the moment :)
>> Regards
>> Darren Sim
>|||Well, it sounds like your web app is not using integrated security. There
are two steps to security. One is authenticating who the user is. That can
be done with forms authentication (in which case you integrate in the
authentication from your web app with RS). Then the other is roles. If you
don't do the roles then the user can go directly to Report Manager web site
and get whatever report they want. So regardless of how you decide to
authenticate you need to still understand and use roles in RS.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Darren Sim" <darrens@.sirius.co.uk> wrote in message
news:uPcxjxpSHHA.3948@.TK2MSFTNGP05.phx.gbl...
> Thanks Bruce your help is much appreciated,
> Just to clarify, at the moment our web app accepts a login from a user
> then checks the details against a database, the returned values determine
> which reports are made available and the links to these are then displayed
> on a page.
> If we were to move the reporting server onto our web server, would it just
> be a case of turning on integrated security on the report server?
> Thanks again
> Darren
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%235q3hphSHHA.4632@.TK2MSFTNGP04.phx.gbl...
>> Crossing domains is an issue.
>> Assuming on the same domain you should be able to assign domain users or
>> domain groups to appropriate roles in RS. If they have been assigned
>> appropriately then they should not be able to see or run reports they
>> shouldn't. The way it works is that security starts with whatever roles
>> have been assigned to the home directory/folder in report manager. All
>> report/folders inherit from this. You can override at either the folder
>> level or the report level. For instance, if there is folder that only
>> management should see the reports then in Report Manager remove the group
>> for browsing for that folder and add one that is just the managers. You
>> can also do this for individual reports. My guess is that no-one
>> understood how roles are used to secure the website. Regardless of
>> whether you integrate this in with your web app, you need to understand
>> this.
>> Yes you can integrate in your own authentication, many people have. It is
>> non-trivial but doable. However, if you have it on the same server as
>> your web app then you can use integrated security, it will know who is
>> connected to your web app and they will only be able to view the
>> appropriate reports.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Darren Sim" <darrens@.sirius.co.uk> wrote in message
>> news:%234FzKGhSHHA.4756@.TK2MSFTNGP06.phx.gbl...
>> Hi folks,
>> I have been charged with the task of providing some security measures
>> for reporting services 2000 and unfortuneately I have found myself a bit
>> out of my depth (usually I am found developing desktop applications), I
>> am comfortable with any c# coding required but I'm finding the whole
>> thing rather confusing.
>> Our setup consists of a webserver and reporting server (on different
>> domains at the moment) We have a website that works as we wish,
>> displaying a list of reports based on the users logon details. However
>> we have found tht the reporting server can be accessed directly and with
>> a bit of playing around anyone can view (often sensitive) information.
>> The current site is written in ASP (not .NET), is it possible to 'wrap'
>> the existing site in an asp.net form so that we can use forms
>> authentication providing the necessary security to plug the hole?
>> To maintian useability we require the dropdowns for parameters provided
>> by URL addressability, so would we need to move the reporting server
>> onto the webserver so that it would have the same domain?
>> Any tips or links would be very much appreciated - I feel like a fish
>> out of water at the moment :)
>> Regards
>> Darren Sim
>>
>|||Thanks again Bruce
You are quite correct - the website set up for viewing reports does not use
integrated security. I have been looking at integrating forms
authentication, but hit a few snags - I think most of the problems are
simply down to a poor understanding of the RS configfiles and what needs to
be done.
We are also moving the reporting services on to the web server to address
the domain issue - I have been thinking of redoing the login page in .NET to
handle forms security, if the login has been successful then allow the user
to proceed to the current site.
At the moment I am using VS2005 and .NET 2.0 for desktop applications, for
RS200 do I neet to use .NET1.1 and VS2003? (I have access to both)
I will read up on roles to get a better understanding of what needs to be
done to enchance security.
Kind regards
Darren Sim
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:e9k5iLuSHHA.1228@.TK2MSFTNGP06.phx.gbl...
> Well, it sounds like your web app is not using integrated security. There
> are two steps to security. One is authenticating who the user is. That can
> be done with forms authentication (in which case you integrate in the
> authentication from your web app with RS). Then the other is roles. If you
> don't do the roles then the user can go directly to Report Manager web
> site and get whatever report they want. So regardless of how you decide to
> authenticate you need to still understand and use roles in RS.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>|||Yes, RS 2000 is a 1.1 application. If your web site is 2.0 it can also run
1.1 for the RS websites.
As a 1.1 application you need to install VS 2003 and then install the report
designer.
If at all possible I would look at upgrading to RS 2005. It uses 2.0. It is
faster and has some important features (end user sorting, multi-select
parameters, calendar control to name a few).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Darren Sim" <darrens@.sirius.co.uk> wrote in message
news:%23caBKv3SHHA.1200@.TK2MSFTNGP04.phx.gbl...
> Thanks again Bruce
> You are quite correct - the website set up for viewing reports does not
> use integrated security. I have been looking at integrating forms
> authentication, but hit a few snags - I think most of the problems are
> simply down to a poor understanding of the RS configfiles and what needs
> to be done.
> We are also moving the reporting services on to the web server to address
> the domain issue - I have been thinking of redoing the login page in .NET
> to handle forms security, if the login has been successful then allow the
> user to proceed to the current site.
> At the moment I am using VS2005 and .NET 2.0 for desktop applications, for
> RS200 do I neet to use .NET1.1 and VS2003? (I have access to both)
> I will read up on roles to get a better understanding of what needs to be
> done to enchance security.
> Kind regards
> Darren Sim
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:e9k5iLuSHHA.1228@.TK2MSFTNGP06.phx.gbl...
>> Well, it sounds like your web app is not using integrated security. There
>> are two steps to security. One is authenticating who the user is. That
>> can be done with forms authentication (in which case you integrate in the
>> authentication from your web app with RS). Then the other is roles. If
>> you don't do the roles then the user can go directly to Report Manager
>> web site and get whatever report they want. So regardless of how you
>> decide to authenticate you need to still understand and use roles in RS.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>|||We are upgrading to sql 2005 and RS2005. This is only to act as a stop-gap
until this can be properly planned and carried out as having the reporting
server accessible by anyone obviously poses a security threat.
Unfortuneately this security hole was only discovered at the last minute
before making the service available to our clients. I have only been here
for 6 months and I'm pushing for all developement to be on the .net 2.0
framework, as I use this for the desktop applications and some of the code I
am using could be reused in the web applications. However we are a very
small operation and getting everyone up to speed takes time, not to mention
the task of doing everything over...
Thanks very much for your assistance Bruce, I think I have an idea of at
least where to begin.
Regards
Darren
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:OqLkrJ4SHHA.4632@.TK2MSFTNGP04.phx.gbl...
> Yes, RS 2000 is a 1.1 application. If your web site is 2.0 it can also run
> 1.1 for the RS websites.
> As a 1.1 application you need to install VS 2003 and then install the
> report designer.
> If at all possible I would look at upgrading to RS 2005. It uses 2.0. It
> is faster and has some important features (end user sorting, multi-select
> parameters, calendar control to name a few).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Darren Sim" <darrens@.sirius.co.uk> wrote in message
> news:%23caBKv3SHHA.1200@.TK2MSFTNGP04.phx.gbl...
>> Thanks again Bruce
>> You are quite correct - the website set up for viewing reports does not
>> use integrated security. I have been looking at integrating forms
>> authentication, but hit a few snags - I think most of the problems are
>> simply down to a poor understanding of the RS configfiles and what needs
>> to be done.
>> We are also moving the reporting services on to the web server to address
>> the domain issue - I have been thinking of redoing the login page in .NET
>> to handle forms security, if the login has been successful then allow the
>> user to proceed to the current site.
>> At the moment I am using VS2005 and .NET 2.0 for desktop applications,
>> for RS200 do I neet to use .NET1.1 and VS2003? (I have access to both)
>> I will read up on roles to get a better understanding of what needs to be
>> done to enchance security.
>> Kind regards
>> Darren Sim
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:e9k5iLuSHHA.1228@.TK2MSFTNGP06.phx.gbl...
>> Well, it sounds like your web app is not using integrated security.
>> There are two steps to security. One is authenticating who the user is.
>> That can be done with forms authentication (in which case you integrate
>> in the authentication from your web app with RS). Then the other is
>> roles. If you don't do the roles then the user can go directly to Report
>> Manager web site and get whatever report they want. So regardless of how
>> you decide to authenticate you need to still understand and use roles in
>> RS.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>sql
Wednesday, March 7, 2012
Reporting Service 2005, Custom Security Extension failed.
Hi,
I am trying the get the custom security extension samples to work on my machine. I have installed everything according the sameple help file. However, i am getting a "Authentication Ticket is not issued by LogonUser." error after I attempted to log on to the report manager thru UILogon.aspx page. I already created an admin user. Upon a closer inspection, I realized that the authentication went thru okay, however, the authentication Ticket Name contained in the "RSAuthenticationHeader" has a duplicate value of "sqlauthticket, sqlauthticket". So apparently, the report server added this value twice to the response header. Has anyone seen this error before? How would you fix it? Also to bypass this error, I parsed out the header and take the correct auth ticket name, now report manager just redisplays the logon page and not letting me thru. Has anyone have seen that before? I am running in Win 2003 server, IIS 6, .NET 2.0 and SQL server 2005 enterprise version.
Thanks for the help,
Eric
Hi EriC!
Did you ever get an answer to your question? I have exactly the same isse.
Best,
Dmitri
Reporting Service 2005, Custom Security Extension failed.
Hi,
I am trying the get the custom security extension samples to work on my machine. I have installed everything according the sameple help file. However, i am getting a "Authentication Ticket is not issued by LogonUser." error after I attempted to log on to the report manager thru UILogon.aspx page. I already created an admin user. Upon a closer inspection, I realized that the authentication went thru okay, however, the authentication Ticket Name contained in the "RSAuthenticationHeader" has a duplicate value of "sqlauthticket, sqlauthticket". So apparently, the report server added this value twice to the response header. Has anyone seen this error before? How would you fix it? Also to bypass this error, I parsed out the header and take the correct auth ticket name, now report manager just redisplays the logon page and not letting me thru. Has anyone have seen that before? I am running in Win 2003 server, IIS 6, .NET 2.0 and SQL server 2005 enterprise version.
Thanks for the help,
Eric
Hi EriC!
Did you ever get an answer to your question? I have exactly the same isse.
Best,
Dmitri
Tuesday, February 21, 2012
Reporting instsallion-problem, initialize RS and security exception
Hi all RS professinal,
I am deploying RS on SQL 2000/sp4 on win2003 sp1.
after we install RS on it. it is running well until the last moment. It said
" setup could not initialize the report server. You must manually initialize
the report server before using it for the first time. For more information,
see the Reporting Services setup documentation"
Then we uninstall it, and then install again, which have the same result.
Then we manually activate it by issuing " rsactivate -c"D:\Program
Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config" -t "
it shows the following error
Failure starting the web service:
System.Exception: The Report Server Web service has not generated a public
key.
The service may not have started successfully. Check the log files for
more in
formation.
at
Microsoft.ReportingServices.RSActivate.RSActivate.RpcActivateService(Int32
clientType)
at Microsoft.ReportingServices.RSActivate.RSActivate.InstanceMain()
at Microsoft.ReportingServices.BaseCmdLine.CommandLineMain(String[] args,
Bas
eCmdLine instance)
when we open http://localhost/reports . it shows the error as attached
Security Exception:
Description: The application attempted to perform an operation not allowed
by the security policy. To gran this applicatino the rqiured permission ,
please contact your system administrator or change the applications trust
level in the configuration file.
we have granted admin right the IUSR_localhost account.
Any Expert can give us opinions on it?
Thanks for millions
PatrickHi Patrick,
I am having an exact same problem as you.
I have Windows Server 2003 SP1, SQL 2000 Standard SP4, no SSL, got the same
error message.
Do you have any luck?
BTW, I have another Windows server 2003 (No SP1), SQL Server SP3, with
Visual Studio .NET install. It worked.
Thanks
Skip
"Patrick Lam" wrote:
> Hi all RS professinal,
> I am deploying RS on SQL 2000/sp4 on win2003 sp1.
> after we install RS on it. it is running well until the last moment. It said
> " setup could not initialize the report server. You must manually initialize
> the report server before using it for the first time. For more information,
> see the Reporting Services setup documentation"
> Then we uninstall it, and then install again, which have the same result.
> Then we manually activate it by issuing " rsactivate -c"D:\Program
> Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\RSReportServer.config" -t "
> it shows the following error
> Failure starting the web service:
> System.Exception: The Report Server Web service has not generated a public
> key.
> The service may not have started successfully. Check the log files for
> more in
> formation.
> at
> Microsoft.ReportingServices.RSActivate.RSActivate.RpcActivateService(Int32
> clientType)
> at Microsoft.ReportingServices.RSActivate.RSActivate.InstanceMain()
> at Microsoft.ReportingServices.BaseCmdLine.CommandLineMain(String[] args,
> Bas
> eCmdLine instance)
> when we open http://localhost/reports . it shows the error as attached
> Security Exception:
> Description: The application attempted to perform an operation not allowed
> by the security policy. To gran this applicatino the rqiured permission ,
> please contact your system administrator or change the applications trust
> level in the configuration file.
>
> we have granted admin right the IUSR_localhost account.
> Any Expert can give us opinions on it?
> Thanks for millions
> Patrick
>
>
I am deploying RS on SQL 2000/sp4 on win2003 sp1.
after we install RS on it. it is running well until the last moment. It said
" setup could not initialize the report server. You must manually initialize
the report server before using it for the first time. For more information,
see the Reporting Services setup documentation"
Then we uninstall it, and then install again, which have the same result.
Then we manually activate it by issuing " rsactivate -c"D:\Program
Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\RSReportServer.config" -t "
it shows the following error
Failure starting the web service:
System.Exception: The Report Server Web service has not generated a public
key.
The service may not have started successfully. Check the log files for
more in
formation.
at
Microsoft.ReportingServices.RSActivate.RSActivate.RpcActivateService(Int32
clientType)
at Microsoft.ReportingServices.RSActivate.RSActivate.InstanceMain()
at Microsoft.ReportingServices.BaseCmdLine.CommandLineMain(String[] args,
Bas
eCmdLine instance)
when we open http://localhost/reports . it shows the error as attached
Security Exception:
Description: The application attempted to perform an operation not allowed
by the security policy. To gran this applicatino the rqiured permission ,
please contact your system administrator or change the applications trust
level in the configuration file.
we have granted admin right the IUSR_localhost account.
Any Expert can give us opinions on it?
Thanks for millions
PatrickHi Patrick,
I am having an exact same problem as you.
I have Windows Server 2003 SP1, SQL 2000 Standard SP4, no SSL, got the same
error message.
Do you have any luck?
BTW, I have another Windows server 2003 (No SP1), SQL Server SP3, with
Visual Studio .NET install. It worked.
Thanks
Skip
"Patrick Lam" wrote:
> Hi all RS professinal,
> I am deploying RS on SQL 2000/sp4 on win2003 sp1.
> after we install RS on it. it is running well until the last moment. It said
> " setup could not initialize the report server. You must manually initialize
> the report server before using it for the first time. For more information,
> see the Reporting Services setup documentation"
> Then we uninstall it, and then install again, which have the same result.
> Then we manually activate it by issuing " rsactivate -c"D:\Program
> Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\RSReportServer.config" -t "
> it shows the following error
> Failure starting the web service:
> System.Exception: The Report Server Web service has not generated a public
> key.
> The service may not have started successfully. Check the log files for
> more in
> formation.
> at
> Microsoft.ReportingServices.RSActivate.RSActivate.RpcActivateService(Int32
> clientType)
> at Microsoft.ReportingServices.RSActivate.RSActivate.InstanceMain()
> at Microsoft.ReportingServices.BaseCmdLine.CommandLineMain(String[] args,
> Bas
> eCmdLine instance)
> when we open http://localhost/reports . it shows the error as attached
> Security Exception:
> Description: The application attempted to perform an operation not allowed
> by the security policy. To gran this applicatino the rqiured permission ,
> please contact your system administrator or change the applications trust
> level in the configuration file.
>
> we have granted admin right the IUSR_localhost account.
> Any Expert can give us opinions on it?
> Thanks for millions
> Patrick
>
>
Subscribe to:
Posts (Atom)