Security problem V1.7.1 and Windows server 2008 R2 64 bits

Aspose.PDF Product Family
1

Hello,


I’ve just installed version 1.7.1 of the reporting pdf for reportingservices dll and I get a nice internal server error with exporting to aspose PDF. I’ve isntalled the dll with the provided msi on the server.

When I reinstall version 1.6.2 the export works.

What could be the problem ? What are the changes which can cause this security errors?

Maybe this can help you:


library!ReportServer_0-5!bac!07/29/2010-07:42:27:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: , Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. —> System.Security.SecurityException: Request for the permission of type ‘System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089’ failed.
at System.StubHelpers.StubHelpers.BeginStandalone(IntPtr pFrame, IntPtr pNMD, Int32 dwStubFlags)
at Microsoft.ReportingServices.Diagnostics.NativeDumperMethods.SetErrorText(String errorText)
at Microsoft.ReportingServices.Diagnostics.Dumper.<>c__DisplayClass2.b__0()
at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.<>c__DisplayClass4.b__3(Object state)
at System.Security.SecurityContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Security.SecurityContext.Run(SecurityContext securityContext, ContextCallback callback, Object state)
at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.RunFromRestrictedCasContext(ContextBody callback)
at Microsoft.ReportingServices.Diagnostics.Dumper.DumpHere(Exception optionalException, String assertionMessage, Boolean unhandledException)
at Microsoft.ReportingServices.Diagnostics.Dumper.RSExceptionHandler(Object sender, RSExceptionCreatedEventArgs e)
at System.EventHandler`1.Invoke(Object sender, TEventArgs e)
at Microsoft.ReportingServices.Diagnostics.Utilities.RSException…ctor(ErrorCode errorCode, String localizedMessage, Exception innerException, RSTrace tracer, String additionalTraceMessage, TraceLevel traceLevel, Object[] exceptionData)
at Microsoft.ReportingServices.Diagnostics.Utilities.ReportCatalogException…ctor(ErrorCode errorCode, String localizedMessage, Exception innerException, String additionalTraceMessage, Object[] exceptionData)
at Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException…ctor(Exception innerException, String additionalTraceMessage)
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.WriteErrorResponse(Int32 code, String shortHttpDescription, Exception exception, Boolean errorResponseAsXml)
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()
at Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
The action that failed was:
Demand
The type of the first permission that failed was:
System.Security.Permissions.SecurityPermission
The first permission that failed was:
<IPermission class="System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1"
Flags=“UnmanagedCode”/>

The demand was for:
<IPermission class="System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1"
Flags=“UnmanagedCode”/>

The granted set of the failing assembly was:
<PermissionSet class="System.Security.PermissionSet"
version=“1”>
<IPermission class="System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1"
Flags=“Execution”/>
<IPermission class="System.Security.Permissions.UrlIdentityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1"
Url=“file:///C:/Program Files/Microsoft SQL Server/MSRS10_50.MSSQLSERVER/Reporting Services/ReportServer/bin/Aspose.Pdf.ReportingServices.DLL”/>
<IPermission class="System.Security.Permissions.ZoneIdentityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
version="1"
Zone=“MyComputer”/>

— End of inner exception stack trace —;


En this is the text in de policy file of reporting service:




2

Hi,

Thanks for using our products.

Can you please share the source .RDL document so that we can test the scenario at our end. Please make sure the report does not contain any references to external data sources. It would be really nice if you could please create a sample report based over Microsoft's AdventureWorks sample database.

We apologize for your inconvenience.

3

Hi,


The problem is not report (.rdl) related. Every report has the problem. So it has no sense to upload one of my reports. It is a security issue before the rendering starts or in one of the first rows of the rendering. But my report it works with version 1.6.2 and not with version 1.7.1 of your ssrs pdf dll. So what is the difference in code of your dll. My report is the same.

Kind regards,

Don van Meel
4

Hello Don,

Please spare us little time as we need to figure out the actual reason of this problem. Once we have some definite information, we would be pleased to update you with the status of correction. We apologize for this inconvenience.