Please refer to the following picture to check the DLL version information.
The DLL file changed the digital signature because the digital signature file was out of date.
I think the change is not the reason which causes exceptions.
Yes I have the same version details but for Version 22.10.0.0 and 22.10.1.0 I had nothing to update with regards to the digital signature.
Do you mean I have to change something for 22.10.2.0 ?
I have checked the config of rssrvpolicy.config and it is still the same, the same public key for Aspose Cells (00240000048000009400000006020000002400005253413100040000010001002780c08eaa89ae
dfb00b1b96137cca3e15f32826e0e4fd1da3c98d1e3968a03a019aa7b7228b151f6e5dae4dcb00
f98479770f507626b04e786e5e93ec3757c1cc4ed1ac4b72c7649c4438e9d3a5f44d8b75220436
86a2e8c2a495e04b917e0505d3201015c828e3c15afc8a46ab78293574b9e0475df68627bbabc5
b564addd)
Could you please follow the guidelines to properly install latest (Dlls version) fix (Aspose.Cells for Reporting Services v22.10.2) and then give it a try to your scenario.
Thank you for this but as i said, everything was installed and running until version 22.10.1.
I have issues with the latest release (22.1.2) only
Can you please try to download your file with the link you have provided and see if this is working on your side ?
Yes, it works on our end. Anyways, we will look into your issue further and get back to you.
@hengert,
I rebuild the fixed version to test. It can run. Please try Aspose.Cells.ReportingServices.22.10.3.zip (6.0 MB)
again.
Test Env :
Microsoft Windows Server 2016 Datacenter
Microsoft SQL Server 2016 (RTM) - 13.0.1601.5 (X64)
Hi, I’m sorry I have the same issue as version 22.1.2
extensionfactory!WindowsService_0!5cf4!11/02/2022-08:25:17:: e ERROR: Exception caught instantiating ACCSV report server extension: System.IO.FileLoadException: Could not load file or assembly ‘Aspose.Cells.ReportingServices, Version=22.10.3.0, Culture=neutral, PublicKeyToken=e6b46033861b5318’ or one of its dependencies. Failed to grant permission to execute. (Exception from HRESULT: 0x80131418)
File name: ‘Aspose.Cells.ReportingServices, Version=22.10.3.0, Culture=neutral, PublicKeyToken=e6b46033861b5318’ —> System.Security.Policy.PolicyException: Execution permission cannot be acquired.
at System.Security.SecurityManager.ResolvePolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Boolean checkExecutionPermission)
at System.Security.SecurityManager.ResolveCasPolicy(Evidence evidence, PermissionSet reqdPset, PermissionSet optPset, PermissionSet denyPset, PermissionSet& denied, Int32& securitySpecialFlags, Boolean checkExecutionPermission)
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at Microsoft.ReportingServices.Diagnostics.ExtensionClassFactory.LoadAssembly(String name)
at Microsoft.ReportingServices.Diagnostics.ExtensionClassFactory.<>c__DisplayClass15_0.b__0()
at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.<>c__DisplayClass1_0.b__0(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.Run(ContextBody callback)
at Microsoft.ReportingServices.Diagnostics.ExtensionClassFactory.CreateExtensionObject(Extension extConfig, Boolean typeOnly)
We are sorry that you still find the same issue with latest version/fix. We will be looking into it soon.
Hi
Do you have an update on this issue ?
@hengert
Please describe in detail the user permissions on the service, we will simulate your user rights to rebuild a user for testing.
e.g.
Hopefully, we resolve this issue soon.
Hi @wangtao
I don’t think this is a permission issue.
As mentioned in the previous message the version 22.10.1 is starting perfectly fine but version 22.10.2 and 22.10.3 does not start. This is in the same environment with the exact same setup (I have tried right now to simply drop the v22.10.1 again in the folder and everything runs perfectly.
In addition we have already another licenced Aspose product on the same server which runs perfectly.
Both DLL have the same access rights as well.
I’ve tried to give Full control to the user and i still have the same issue
We’ll roll back the code to see if adding a way to get the code is causing this permission issue.
We will soon provide a rollback version for testing.
Ok thank you.
Sounds like a good plan
I have tried again and I still have the same issue.
I also see that the digital signatures has changed since version 2.10.1, do you think this can be related to our issue ?
Issuer: DigiCert SHA2 Assured ID Code Signing CA
Issuer: DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1
We build the test version without digital signatures. Please try it again.
Aspose.Cells.ReportingServices.22.10.0.5.zip (6.0 MB)
Hi, I am very sorry but this is still not working. I then assume it’s not linked to the digital signatures.
Can you please verify again that you have rollback to version 22.10.1 and not 22.10.2 ?