sql server reporting services: I created a report include some DotNet Assembly in the reports property
reference page like system.drawing, system.windows.forms, write some customer
code using system.drawing & system.windows.forms, the reports display fine in
the preview page, but after i deployee to the sql 2000 server, then view the
report from sql 2000 server, i got error, i think this is the DotNet Assembly
deployee problem, please help me, thanks.

--

Hi steven,

Thanks for your replying.

I think i did not use customer assemblies, i wrote some embedded code and
using system.drawing & system.windows.forms, i add those assembly to the
report's property reference page that i can preview in IDE, but i can not
view this report from server after i deploy this report to server.



--
Pony Tsui

Hi Pony,

Thank you for posting.

From your description, you're using some external or custom .net assemblies
in your SQL Server reporting service report. This runs well at development
in VS IDE through preview, but got some deployment error when publishing to
the actual server, correct?

Based on my experience, as for custom assemblies in Reporting Service
report, we will need to take care of two things:

1. The location of the assembly where you deploy it. This is important for
the report server application to locate the assembly at runtime.

2. The code access security permission for the code in custom assemblies to
execute. By default, the execution permission for custom .net aasemblies
are quite restricted for the report server application(an ASP.NET web
application).

Here is a good tech article discussing on such settings involved in using
custom assemblies in reporting service report:

http://www.yukonxml.com/chapters/apress/reportingservices/dotnet/

Regards,

Steven Cheng
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.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Thanks for your followup Pony,

So I've got that you're just using some built-in classes in the .net
framework's fundamental class library rather than use own custom
assemblies. I've just performed some test on my local side according to
your scenario (reference some built-in assembly and call class's method in
Embeded Code section) and it worked well in both development environment(in
IDE ) and published report server. So I think this should be a project
specific issue, I think you can first try change to use some other
built-in classes to see whether they suffer the same problem. As for
System.Windows.forms assembly, I don't think all the classes in it can be
used in a web application context (report server is an ASP.NET web
application). Anyway, my local test just call the HttpUtility class's
HtmlEncode static method (reference the System.Web.dll assembly) and it
works. You can do such test to verify whether the problem is due to the
particular assemblies or classes you used in your project.

Regards,

Steven Cheng
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.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Hi Steven Cheng[MSFT],
this is exactly my problem. System.Web.HttpUtility.HtmlEncode works well in
IDE but fails on report server.

Could you send me please your testing project to help me find what's wrong?