Hi, I am currently working on SQL server reporting. I have created custom assemblies. I am loading the custom assebly in the rdl file. I am getting following exception An error occurred while executing OnInit: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. (rsErrorInOnInit) Please let me know if anyone knows the reason. Thanks in Advance.

Are you saying you have created assemblies that have been deployed to SQL Server, and when you try toexecute an exposed method you are getting said exception? If so, what permission set did you give the assemblies when deploying? If you didn't give the assembly any explicit permission set, re-deploy using EXTERNAL_ACCESS, if that doesn't help use UNSAFE.Niels

I am having the same problem...I haveused a Custom data extension assembly which is working fine on Visual studio RDL development preview but Now...as I paste it to SSRS bin and try to view in report server it doesnot work...error given An error has occurred during report processing. (rsProcessingAborted) Cannot create a connection to data source 'DataSource1'. (rsErrorOpeningConnection) Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServerand register give necessary permission(1)<Extension Name="DATASET" Type="Prologika.RS.Extensibility.CustomDataExtension.DsConnectionWrapper,Prologika.CustomDataExtension"/>(2)<CodeGroup class="UnionCodeGroup" version="1" Name="CustomDataExtensionCodeGroup" Description= "Code group for the Custom Data Extension" PermissionSetName="fulltrust"> <IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Program Files\ Microsoft SQL Server\MSSQL.3\ Reporting Services\ReportServer\bin\ Prologika.CustomDataExtension.dll"/> </CodeGroup>

Hi abhisharmaDid you finally find a way to solve your problem?Because i have the same now...Thanks a lot if you have the solutionMaxime

I am having the same problem...I have used a Custom data extension assembly which is working fine on Visual studio RDL development preview but Now...as I paste it to SSRS bin and try to view in report server it doesnot work...error given An error has occurred during report processing. (rsProcessingAborted) Cannot create a connection to data source 'DataSource1'. (rsErrorOpeningConnection) Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer and register give necessary permission (1) <Extension Name="DATASET" Type="Prologika.RS.Extensibility.CustomDataExtension.DsConnectionWrapper,Prologika.CustomDataExtension"/> (2) <CodeGroup class="UnionCodeGroup" version="1" Name="CustomDataExtensionCodeGroup" Description= "Code group for the Custom Data Extension" PermissionSetName="fulltrust"> <IMembershipCondition class="UrlMembershipCondition" version="1" Url="C:\Program Files\ Microsoft SQL Server\MSSQL.3\ Reporting Services\ReportServer\bin\ Prologika.CustomDataExtension.dll"/> </CodeGroup> I am having the same EXACT problem with the same code any resolution?

Hi folks,This is a ReportServer problem (in SSRS service) not a SQLCLR problem. Did you also post on the reporting services forum? Do you want me to transfer this posting to that forum?Cheers,Bob BeaucheminSQLskills

I am having the same issue. Does anyone here know how to solve this?Thanks,

sorry but i am haveing the same problem, any resolution??

I finally found the solution. I don't know if it applies to other but to me it is very stupid.I just fixed the path for the dll file from policy config file by doing it without newline./**Before**/C:\Program Files\ Microsoft SQL Server\MSSQL.3\ Reporting Services\ReportServer\bin\ Prologika.CustomDataExtension.dll/**After**/C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Prologika.CustomDataExtension.dllThis fix my problem! More and more I found Microsoft products really bad. I use to love using MS products a lot but not anymore. Most of their products just cannot compete with others. The worst I will say is their IE Browser. I never seen a browser that slow anymore.Anyways, hope my solution help.

I finally found the solution. I don't know if it applies to other but to me it is very stupid. I just fixed the path for the dll file from policy config file by doing it without newline. /**Before**/ C:\Program Files\ Microsoft SQL Server\MSSQL.3\ Reporting Services\ReportServer\bin\ Prologika.CustomDataExtension.dll /**After**/ C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\bin\Prologika.CustomDataExtension.dll This fix my problem! More and more I found Microsoft products really bad. I use to love using MS products a lot but not anymore. Most of their products just cannot compete with others. The worst I will say is their IE Browser. I never seen a browser that slow anymore. Anyways, hope my solution help. no, thats how i already have it but still no luck its because my dll is a custom one i use to connect to the database not using prologika.

well i SOLVED THE PROBLEM but u wont like the solution i went into the web.config file in \reportserver\ and changed <securityPolicy> <trustLevel name="RosettaSrv" policyFile="rssrvpolicy.config" /> </securityPolicy> <trust level="RosettaSrv" originUrl="" /> </system.web> to </securityPolicy> <trust level="Full" originUrl="" /> </system.web> clearly the problem is in this file. now besides making this full trust like that, maybe we can use a scalper instead of a shovel ! any suggestions?

I know this is an old thread, but it has 18K views (wow!!!) so let me see if I can spot the issue: The only difference I see and I *think* it is the problem is that you're using lower case in the PermissionSetName attribute. Try "FullTrust" which is the actual permission set defined at the top of the file... <PermissionSet class="NamedPermissionSet" version="1" Unrestricted="true" Name="FullTrust" Description="Allows full access to all resources"/> Hope this helps, -LukaszGot a bug or feature request? Tell me about it at http://connect.microsoft.com. This posting is provided "AS IS" with no warranties, and confers no rights.

Dude! You rock! Thanks!