Customer Deployment Requirements for Reporting Services Express?

Hello. I have a version of SQL Express with Advanced services. I created a report and all seems well in Report Manager on my computer. Now it's time to deploy my report to some customers.

1. Can I create an application in Visual Studios Express to view my report? I've read things online that seem contradictory to me and I'm hoping you can clarify this.

2. On a customer machine, if they have a .net application that can render my report, will they have to install reporting services on their computer or can the .rdl file run independently of reporting services if plugged into a .net viewer component? If it was called from a .net application, then Report Server and Report Manager aren't really needed are they? I have a situation where we don't want to use IIS on customer computers if we don't need to. Since the reports will not be adhoc, we're hoping to avoid needing to install Reporting Services on customer computers.

Thanks!

Debbie Erickson

Not sure on #1.

On #2, you should be able to render the report through the ReportViewer control, which removes the need for the Report Server and Report Manager (and IIS), as it handles the report rendering.

custom security extension

Hello,
i tried the sample for the custom security extension for sql server 2005.
the c# Version worked, the vb.net version does not!
Is there another example with the use of application roles? We need this for
reporting issues.
thx in advange
michaelHi michael,
Welcome to use MSDN Managed Newsgroup Support.
I am not so sure which sample application you can not deploy. Would you
please post the Application path here?
As for the samples of Application Role, you may try to refer SQL Server
books online.
An application role is a database principal that enables an application to
run with its own, user-like privileges.
The following steps make up the process by which an application role
switches security contexts:
A user executes a client application.
The client application connects to an instance of SQL Server as the
user.
The application then executes the sp_setapprole stored procedure with
a password known only to the application.
If the application role name and password are valid, the application
role is activated.
At this point the connection loses the permissions of the user and
assumes the permissions of the application role.
For more detail information, you may refer the following article:
Application Roles
http://msdn2.microsoft.com/en-us/library/ms190998(SQL.90).aspx
CREATE APPLICATION ROLE
http://msdn2.microsoft.com/en-us/library/ms181491(SQL.90).aspx
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello Wei,
I tried this sample application:
c:\Program Files\Microsoft SQL Server\90\Samples\Reporting
Services\Extension Samples\FormsAuthentication Sample\cs\FormsAuthentication
It worked for me, but i need the ability to work also with Roles (instead of
NT Group names).
Is there a sample application which consider application roles to group
users with identical permissions for a Custom security extension for sql
server 2005?
thx
michael
"Wei Lu" wrote:
> Hi michael,
> Welcome to use MSDN Managed Newsgroup Support.
> I am not so sure which sample application you can not deploy. Would you
> please post the Application path here?
> As for the samples of Application Role, you may try to refer SQL Server
> books online.
> An application role is a database principal that enables an application to
> run with its own, user-like privileges.
> The following steps make up the process by which an application role
> switches security contexts:
> A user executes a client application.
>
> The client application connects to an instance of SQL Server as the
> user.
>
> The application then executes the sp_setapprole stored procedure with
> a password known only to the application.
>
> If the application role name and password are valid, the application
> role is activated.
>
> At this point the connection loses the permissions of the user and
> assumes the permissions of the application role.
> For more detail information, you may refer the following article:
> Application Roles
> http://msdn2.microsoft.com/en-us/library/ms190998(SQL.90).aspx
> CREATE APPLICATION ROLE
> http://msdn2.microsoft.com/en-us/library/ms181491(SQL.90).aspx
>
> Hope this will be helpful.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Michael,
I understand that you want to use application roles for a custom security
extension for SQL reporting services. If I misundestood your concern,
please feel free to point it out.
Application Role is a database principal that enables an application to run
with its own, user-like privileges. So Application Role is a database
security. And I think it is not suitable for the Reporting Service.
If you use application role to control the permission of SQL database then
you can not control the authentication of the Reports in the report server.
Thank your for your understanding.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Custom Rendering Extension in SQL 2000 Reporting Services

I am trying to write a custom rendering extension for the SQL Server 2000
version of Reporting Services. The documentation I found on MSDN indicates
that it is possible to write one using Visual Studio .Net 2003 (which is what
I'm using). The samples they have are for VS.Net 2005. I'm trying to
implement it for VS.Net 2003, and I can't seem to find the references for:
Microsoft.ReportingServices.ReportRendering.IRenderingExtension
in SQL 2000 Reporting Services. What is the equivalent in SQL Server 2000
RS and Visual Studio .Net 2003?
Thanks,
Mike SandwickMicrosoft.ReportingServices.ReportRendering.IRenderingExtension is identical
in RS 2000 and RS 2005. In RS 2000 you need to add a reference to
Microsoft.ReportingServices.Processing.dll, in the final RS 2005 release it
would be Microsoft.ReportingServices.ProcessingCore.dll.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mike Sandwick" <MikeSandwick@.discussions.microsoft.com> wrote in message
news:F9A76586-30EE-450D-993E-7FEE3ADA1BF3@.microsoft.com...
>I am trying to write a custom rendering extension for the SQL Server 2000
> version of Reporting Services. The documentation I found on MSDN
> indicates
> that it is possible to write one using Visual Studio .Net 2003 (which is
> what
> I'm using). The samples they have are for VS.Net 2005. I'm trying to
> implement it for VS.Net 2003, and I can't seem to find the references for:
> Microsoft.ReportingServices.ReportRendering.IRenderingExtension
> in SQL 2000 Reporting Services. What is the equivalent in SQL Server 2000
> RS and Visual Studio .Net 2003?
> Thanks,
> Mike Sandwick|||Thanks, Robert. This is exactly the information I was looking for! I added
the reference to Microsoft.ReportingServices.Processing.dll, and I can now
compile the sample.
Thanks,
Mike Sandwick
"Robert Bruckner [MSFT]" wrote:
> Microsoft.ReportingServices.ReportRendering.IRenderingExtension is identical
> in RS 2000 and RS 2005. In RS 2000 you need to add a reference to
> Microsoft.ReportingServices.Processing.dll, in the final RS 2005 release it
> would be Microsoft.ReportingServices.ProcessingCore.dll.
>
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mike Sandwick" <MikeSandwick@.discussions.microsoft.com> wrote in message
> news:F9A76586-30EE-450D-993E-7FEE3ADA1BF3@.microsoft.com...
> >I am trying to write a custom rendering extension for the SQL Server 2000
> > version of Reporting Services. The documentation I found on MSDN
> > indicates
> > that it is possible to write one using Visual Studio .Net 2003 (which is
> > what
> > I'm using). The samples they have are for VS.Net 2005. I'm trying to
> > implement it for VS.Net 2003, and I can't seem to find the references for:
> >
> > Microsoft.ReportingServices.ReportRendering.IRenderingExtension
> >
> > in SQL 2000 Reporting Services. What is the equivalent in SQL Server 2000
> > RS and Visual Studio .Net 2003?
> >
> > Thanks,
> > Mike Sandwick
>
>

Custom Authentication in RS 2005

We are currently using RS Standard Edition (SE). With the first version of
RS, Custom Authentication was only available for the Enterprise Edition
(EE).
I was reading the new features of RS 2005, and I noticed that Custom
Authentication is now available for both SE and EE licenses. Is this
correct? I just want to confirm (before installing RS 2005) since this is
our major hurdle in creating a secure reporting system.
TIA.
MarlonYES, regarding this article
http://msdn2.microsoft.com/ms143761.aspx
Med bouchenafa
"TechnoSpyke" <technospyke@.yahoo.com> a écrit dans le message de news:
uQtAPloIGHA.1876@.TK2MSFTNGP11.phx.gbl...
> We are currently using RS Standard Edition (SE). With the first version
> of RS, Custom Authentication was only available for the Enterprise Edition
> (EE).
> I was reading the new features of RS 2005, and I noticed that Custom
> Authentication is now available for both SE and EE licenses. Is this
> correct? I just want to confirm (before installing RS 2005) since this is
> our major hurdle in creating a secure reporting system.
> TIA.
>
> Marlon
>

Custom assemblies in July CTP 2005

Hi,
I was just trying to test my new custom assemblies on 2005 CTP July
version (I think). The usual directories are not there. I looked up
the documentation and the directories the documentation told me to put
the custom assemblies in are also not there...
Does anyone know where I should put the dll for custom assemblies for
2005 July CTP?
Thanks
Peter
www.peternolan.comI highly recommend downloading the September CTP. Especially if you are
using Reporting Services.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Peter Nolan" <peter@.peternolan.com> wrote in message
news:1127598946.821023.209470@.f14g2000cwb.googlegroups.com...
> Hi,
> I was just trying to test my new custom assemblies on 2005 CTP July
> version (I think). The usual directories are not there. I looked up
> the documentation and the directories the documentation told me to put
> the custom assemblies in are also not there...
> Does anyone know where I should put the dll for custom assemblies for
> 2005 July CTP?
> Thanks
> Peter
> www.peternolan.com
>|||Regarding custom assemblies on RS 2005 - please check the updated online
documentation for RS 2005: http://msdn2.microsoft.com/en-us/library/ms225486
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:O4KuhwWwFHA.900@.TK2MSFTNGP11.phx.gbl...
>I highly recommend downloading the September CTP. Especially if you are
>using Reporting Services.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Peter Nolan" <peter@.peternolan.com> wrote in message
> news:1127598946.821023.209470@.f14g2000cwb.googlegroups.com...
>> Hi,
>> I was just trying to test my new custom assemblies on 2005 CTP July
>> version (I think). The usual directories are not there. I looked up
>> the documentation and the directories the documentation told me to put
>> the custom assemblies in are also not there...
>> Does anyone know where I should put the dll for custom assemblies for
>> 2005 July CTP?
>> Thanks
>> Peter
>> www.peternolan.com
>|||Hi Bruce,
thanks...I got a note from dundas on their new beta and it being
recommended on the september CTP.....but I am travelling again so I
will fetch all the 'new stuff' next time I on my own dime...
Thanks
Peter|||Hi Robert,
I followed the documentation you pointed to and copied my custom
assembly as put new code groups into the config files as specified..I
still get the message 'The application for BI4ALL.rptproj is not
installed' when I try to open up my visual studio project.....I have
an old version and the only difference is the custom assembly (I
believe).
Do you (or anyone else) have any ideas what else I might have to do?
Thanks
Peter
To deploy a custom assembly in Reporting Services
Copy your custom assembly from your build location to the report server
bin folder or the Report Designer folder. The default location of the
bin folder for the report server is C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportServer\bin. The default
location of the Report Designer is C:\Program Files\Microsoft Visual
Studio 8\Common7\IDE\PrivateAssemblies.
If you need to grant your custom assembly code permissions beyond the
default execute permissions:
Open the appropriate configuration file. The default location of
rssrvpolicy.config is C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer. The default location of
rspreviewpolicy.config is C:\Program Files\Microsoft Visual Studio
8\Common7\IDE\PrivateAssemblies.
Add a code group for your custom assembly. For more information, see
Understanding Code Access Security in Reporting Services.
<CodeGroup class="UnionCodeGroup"
version="1"
PermissionSetName="FullTrust"
Name="MyCodeGroup"
Description="Code group for my data processing extension">
<IMembershipCondition class="UrlMembershipCondition"
version="1"
Url="C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer\bin\Microsoft.Samples.ReportingServices.FsiDataExtension.dll"
/>
</CodeGroup>|||What do you mean with you "have an old version"? RS 2005 report projects
require the installation of BI Development Studio to open successfully. Can
you create report projects without custom assemblies in BI Development
Studio successfully?
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Peter Nolan" <peter@.peternolan.com> wrote in message
news:1127651973.385470.44280@.g49g2000cwa.googlegroups.com...
> Hi Robert,
> I followed the documentation you pointed to and copied my custom
> assembly as put new code groups into the config files as specified..I
> still get the message 'The application for BI4ALL.rptproj is not
> installed' when I try to open up my visual studio project.....I have
> an old version and the only difference is the custom assembly (I
> believe).
> Do you (or anyone else) have any ideas what else I might have to do?
> Thanks
> Peter
> To deploy a custom assembly in Reporting Services
> Copy your custom assembly from your build location to the report server
> bin folder or the Report Designer folder. The default location of the
> bin folder for the report server is C:\Program Files\Microsoft SQL
> Server\MSSQL.3\Reporting Services\ReportServer\bin. The default
> location of the Report Designer is C:\Program Files\Microsoft Visual
> Studio 8\Common7\IDE\PrivateAssemblies.
> If you need to grant your custom assembly code permissions beyond the
> default execute permissions:
> Open the appropriate configuration file. The default location of
> rssrvpolicy.config is C:\Program Files\Microsoft SQL
> Server\MSSQL\Reporting Services\ReportServer. The default location of
> rspreviewpolicy.config is C:\Program Files\Microsoft Visual Studio
> 8\Common7\IDE\PrivateAssemblies.
> Add a code group for your custom assembly. For more information, see
> Understanding Code Access Security in Reporting Services.
>
> <CodeGroup class="UnionCodeGroup"
> version="1"
> PermissionSetName="FullTrust"
> Name="MyCodeGroup"
> Description="Code group for my data processing extension">
> <IMembershipCondition class="UrlMembershipCondition"
> version="1"
> Url="C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportServer\bin\Microsoft.Samples.ReportingServices.FsiDataExtension.dll"
> />
> </CodeGroup>
>|||Hi Robert,
yes, projects without custom assemblies are fine..
What I meant was I have a version of our reports with no custom
assemblies and they upgrade and can be previewed in BI Dev studio just
fine...they can also be deployed to reporting services web server just
fine....
When I try to copy the version of our reports with the Custom Assembly
across to 2005 I get the message 'The application for BI4ALL.rptproj is
not installed' when I try to open up my visual studio project.....So,
I am guessing it is still the CA...
I have gone through all the steps in the documentation referenced but
still cannot get the project to open...
So, I am looking for hints as to whether it is the CA and if so how I
might get it it work..
Thanks
Peter|||Hi All,
I am still working on this...Has anyone else got custom assemblies
working on July CTP for SQL Server?
Thanks
Peter|||Hi All,
thought I would add my latest efforts to trying to get my reports to
migrate across. I have got my custom assembly working on 2005...I was
able to add the custom assembly to the old version of my project and
have it run and work...so I no longer think my error message is related
to the customer assembly.
I searched this group for the message 'The application for project
'xxx.rptproj' is not installed. Make sure the application for the
project type (.rptproj) is installed.
I found this entry on the group about clearing public and private cache
but how do I clear these caches?
http://groups.google.com/group/microsoft.public.sqlserver.reportingsvcs/browse_thread/thread/7e68c4de6af07a72/7bed68d9e4214e23?q=make+sure+application+for+project+type+is+installed&rnum=1&hl=en#7bed68d9e4214e23
All ideas most welcome!!!
How did I get custom assemblies to work you may ask...
Well on CTP July.
I cannot find:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportServer
I can only find...
D:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer
where the following config files reside...
rsreportserver.config
rssrvpolicy.config
web.config
http://msdn2.microsoft.com/en-us/library/ms225486
says the following...
To deploy a custom assembly in Reporting Services
Copy your custom assembly from your build location to the report server
bin folder or the Report Designer folder. The default location of the
bin folder for the report server is C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportServer\bin. The default
location of the Report Designer is C:\Program Files\Microsoft Visual
Studio 8\Common7\IDE\PrivateAssemblies.
If you need to grant your custom assembly code permissions beyond the
default execute permissions:
Open the appropriate configuration file. The default location of
rssrvpolicy.config is C:\Program Files\Microsoft SQL
Server\MSSQL\Reporting Services\ReportServer. The default location of
rspreviewpolicy.config is C:\Program Files\Microsoft Visual Studio
8\Common7\IDE\PrivateAssemblies.
Add a code group for your custom assembly. For more information, see
Understanding Code Access Security in Reporting Services.
So I added these entries to my config files...
Snipped from my rssrvpolivy.config file..
<CodeGroup class="FirstMatchCodeGroup" version="1"
PermissionSetName="Nothing">
<IMembershipCondition class="AllMembershipCondition"
version="1" />
<CodeGroup class="UnionCodeGroup" version="1"
PermissionSetName="FullTrust" Name="IBIRSCustomClass"
Description="IBIRSCustomClass">
<IMembershipCondition class="UrlMembershipCondition"
version="1" Url="D:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting
Services\ReportServer\bin\IBIRSCustomClass.dll"/>
</CodeGroup>
<CodeGroup class="UnionCodeGroup" version="1"
PermissionSetName="Execution"
Name="Report_Expressions_Default_Permissions" Description="This code
group grants default permissions for code in report expressions and
Code element. ">
<IMembershipCondition
class="StrongNameMembershipCondition" version="1"
PublicKeyBlob="0024000004800000940000000602000000240000525341310004000001000100512C8E872E28569E733BCB123794DAB55111A0570B3B3D4DE3794153DEA5EFB7C3FEA9F2D8236CFF320C4FD0EAD5F677880BF6C181F296C751C5F6E65B04D3834C02F792FEE0FE452915D44AFE74A0C27E0D8E4B8D04EC52A8E281E01FF47E7D694E6C7275A09AFCBFD8CC82705A06B20FD6EF61EBBA6873E29C8C0F2CAEDDA2"
/>
</CodeGroup>
Snipped from my rspreviewpolicy.config file...
<CodeGroup class="FirstMatchCodeGroup" version="1"
PermissionSetName="Nothing">
<IMembershipCondition class="AllMembershipCondition"
version="1" />
<CodeGroup class="UnionCodeGroup" version="1"
PermissionSetName="FullTrust" Name="IBIRSCustomClass"
Description="IBIRSCustomClass">
<IMembershipCondition class="UrlMembershipCondition"
version="1" Url="D:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting
Services\ReportServer\bin\IBIRSCustomClass.dll"/>
</CodeGroup>
<CodeGroup class="UnionCodeGroup" version="1"
PermissionSetName="Execution"
Name="Report_Expressions_Default_Permissions" Description="This code
group grants default permissions for code in report expressions and
Code element. ">
<IMembershipCondition
class="StrongNameMembershipCondition" version="1"
PublicKeyBlob="0024000004800000940000000602000000240000525341310004000001000100512C8E872E28569E733BCB123794DAB55111A0570B3B3D4DE3794153DEA5EFB7C3FEA9F2D8236CFF320C4FD0EAD5F677880BF6C181F296C751C5F6E65B04D3834C02F792FEE0FE452915D44AFE74A0C27E0D8E4B8D04EC52A8E281E01FF47E7D694E6C7275A09AFCBFD8CC82705A06B20FD6EF61EBBA6873E29C8C0F2CAEDDA2"
/>
</CodeGroup>
And then it all seems to work ok.... :-)
Hope this helps someone else :-)
Peter
www.peternolan.com