Custom Assemblies Returning #Error on Production Server

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

stryder9 - 28 Jun 2005 20:56 GMT

To make a long story short.
I have a custom assembly which works fine on my development pc; however when
I deploy it to the production server, I get #error where my assembly is
supposed to return a value. My assembly on works on the production server
only if I turn off security with caspol.exe.
- Things I've done so far -
1. Copied my DLL to the bin folder of the production Report Server
2. Added a code group to the rssrvpolicy.config file with Full Trust for my
assembly.
3. Evaluted the assembly permission with .Net Configurator, which return
"unrestricted" on all levels.
Any help would be greatly appreciated at this point..Thanks in advance.

Reply to this Message

stryder9 - 30 Jun 2005 16:03 GMT

I've noticed quite a few others having the same problem; so I'm sharing my
solution in hopes that it may help others.

Given what I tried in the previous post, the only thing I didn't do was
"Assert Permissions" within the code in my custom assembly. Even though your
assemly works in the designer; unless you "Assert Permissions", it will NOT
work when you deploy your solution to the production server environment.

Imports for my assembly:

Imports System.Data.SqlClient
Imports System.Security.Permissions

Below is the line of code I added to the assembly:

Dim pSQL As New
SqlClientPermission(System.Security.Permissions.PermissionState.Unrestricted)
pSQL.Assert()

Reference on MSDN:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_
prog_rdl_0so6.asp

Hope this helps someone.

> To make a long story short.
> I have a custom assembly which works fine on my development pc; however when
[quoted text clipped - 8 lines]
> "unrestricted" on all levels.
> Any help would be greatly appreciated at this point..Thanks in advance.

Reply to this Message