SSRS 2014 policy changes?

Hello,

Is there a policy change for full trusted assemblies in ssrs 2014 in Native mode? I have an assembly that uses the File.Exists funtion. For this the assembly should be FULLTRUST in the config files:

msdn.microsoft.com/en-us/library/ms152828(v=sql.120).aspx
(cannot post an url so removed https:\\)

In ssrs 2012 it works file but I'm trying to run the assembly on a SQL 2014 machine but this does not work. Also in my visual studio 2013 the assembly is full trusted. I tried to add the assembly in the GAC and created an StrongNameMembershipCondition with PublicKeyBlob key but this does not work as well.

I'm out of options. hope that someone can help me with this.

Kind regards,
Ronald

July 7th, 2015 7:44am

Hi Ronald,

According to your description, the custom assembly in SSRS 2014 doesnt work but can work in SSRS 2012, right?

In your scenario, since you mention the assembly cant work in SSRS 2014, would you please share the error message for our analysis?

If you want to run and debug reports that reference your custom assembly in Report Designer, you should place your custom assembly in the Report Designer folder (%ProgramFiles%\Microsoft Visual Studio 12.0\Common7\IDE\PrivateAssemblies), then add code group for the assembly. In code group, please try to add path of assembly instead of PublicKeyBlob key, specify PermissionSetName as "FullTrust". You could refer to Placement of CodeGroup Elements for Extensions section of this article: Using Reporting Services Security Policy Files.

If you have any question, please feel free to ask.
 
Best regards,
Qiuyun Yu

Free Windows Admin Tool Kit Click here and download it now
July 7th, 2015 11:19pm

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

Other recent topics Other recent topics