Groups | Blog | Home
all groups > sql server reporting services > february 2005 >

sql server reporting services : Loading code module during deployment. Unknown error



Benugo
2/4/2005 9:01:02 AM
I have written a custom assembly which is utilized by a report. I have
referenced the assembly in the designer and copied the dll over to both the
correct designer and server rs folders. The assembly is strongly named and I
have added the public key to the code group for my dll. The assembly info
file uses the assembly level 'PartiallyTrustedUsers' declaration. I have also
provided the SqlClientPermissionSet attribute for my assembly methods.

When in preview mode the report interacts with the assembly without any
problems. However, when I try to deploy the project, the assembly can't
deploy, and the following error message is given;

Error while loading code module: ‘Bills.Reports.Services,
Version=1.0.1861.24738, Culture=neutral, PublicKeyToken=6770a2ddb8b54cb8’.
Details: ?

Has anybody else had this problem? Does anybody know what I am doing wrong
Cem Demircioglu
2/4/2005 5:10:02 PM

Benugo,
It is related to code access security issues. Try running your code under
fulltrust first.
Once it is successful, use permview to determine required CAS level.

Regards,
Cem Demircioglu

[quoted text, click to view]

Benugo
2/7/2005 1:33:01 AM
I have changed the server side rssrvpolicy.cs to full trusted mode and I
still get the same error when attempting to upload the code. I even restarted
IIS to make sure. Is there anything else I can try.

[quoted text, click to view]
Benugo
2/7/2005 2:15:01 AM
Have just attempted to deploy a simple assembly (doesn't access databases,
files etc, just returns a simple "Hello world" string"). Again this code
works well in the preview, but I get the same problem when I try to deploy
it. Can it still be a policy file issue? Surely the policy file shouldn't
prevent the dll from deploying (just from being used by the report).

[quoted text, click to view]
Alexandre Mineev [MSFT]
2/9/2005 11:56:20 AM
Make sure that assembly is in Reportserver/bin. Also check file permissions
on the dll file - RS Server should be able to read the file.
There is a simple way to verify if it's a CAS issue or not: go to
rssrvpolicy.config, temporarily "Nothing" to "FullTrust" at the root code
group, restart IIS and see what happens. If assembly works - then there is a
CAS problem. Please return "Nothing" back afterwards.

--
Alex Mineev
Software Design Engineer. Report expressions; Code Access Security; Xml;
SQE.

This posting is provided "AS IS" with no warranties, and confers no rights

[quoted text, click to view]

Brian Todd [EDS]
4/22/2005 12:00:02 PM
I had the exact same problem. It was the permissions on the dll files
themselves. When I copied them into the folder they did not assume the
permissions of the parent folder. Once I set those it worked.


[quoted text, click to view]
AddThis Social Bookmark Button