No error with custom DLL - just blank
I've written and deployed a custom dll for reporting services to a production server and it's working fine. Now I'm deploying the dll to another server and the report is generating but the field where data coming from the dll is blank. I'm not getting #error, it's just a blank space. Is this an IIS issue? I've edited and then reverted the rssvrpolicy.config back to its original state to try to get an error but I'm just seeing a blank space. If anyone can point me in a direction of investigation I'd appreciate it. Thanks
April 28th, 2011 4:36pm

Hi MitchP_ny, I am trying to involve someone familiar with this topic to a further look at this issue. There might be some time delay. Appreciate your patience. Thank you for your understanding and support. Regards, Challen FuPlease remember to mark the replies as answers if they help and unmark them if they provide no help.
Free Windows Admin Tool Kit Click here and download it now
April 29th, 2011 6:15am

Mitch, Could you tell me a bit more about your DLL and what it's doing? The reason for this is that there are a number of security issues that could prevent the code from being called, the main two being: 1. Reporting Services executes custom code in Partial Trust. If you call certain APIs, you have to make some changes to the policy file in the RS folder. If even one function violates the policy file settings, then no function in the DLL will work. A quick and dirty way (for testing only) to disable the policy file altogether, is to change the <trust> tag in the Report Server's web.config file from <trust level="RosettaSrv" originUrl="" /> to <trust level="Full" originUrl="" />. If the DLL works after that, then you definitely have Code Access Security issues and a bad policy file setting. 2. The service account for RS may not have permissions to do something your code is doing, like access a file. A third, less likely possibility, could be if the server is running Reporting Services 2008 R2 in Sandbox mode, this will prevent custom code from running. A fourth possibility could be you recompiled the DLL and accidentally deleted the AllowPartiallyTrustedCallers attribute. Setting the trust level to "Full" will allow the code to run if this is the issue, also. If you suspect the issue is none of the above, you may want to add a "Test" function to the module, that just returns "Working" or something like that so you can see whether the issue lies in the configuration or in the code. If the test function works, then I'd suspect your other function may not be trapping an exception of some sort. You may want to attach to Report Server using Visual Studio and step through your code. If it's a policy issue, you won't be able to do this, so only do this if the test function works. Please let me know if you have any further questions. Thanks. Malcolm Stewart
May 2nd, 2011 10:20pm

The answer was granting the code permissions in the rssrvpolicy.config file
Free Windows Admin Tool Kit Click here and download it now
August 11th, 2011 2:28pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics