image.png (33.4 KB)
Hi Team,
we update Aspose.PDF version 22.5 after up gradation get this error.
Aspose.PDF does not require Aspose.Imaging. Please clean and build your application again. Hope this helps you.
If you still face problem, please remove DLLs from your Visual Studio application and share it here for testing. We will investigate the issue and provide you more information on it.
Hi
having a similar issue, only when Aspose.PDF.dll is deployed to the server global assembly cache. works as expected from the website bin folder.
we do not have Aspose.Imaging
hi
when aspose.pdf.dll is deployed to the global assembly cache on our IIS vm, the convertion to pdf fails with the error: Could not load file or assembly ‘Aspose.Imaging, Version=22.12.0.0, Culture=neutral, PublicKeyToken=716fcc553a201e56’.
However when the dll is placed in the web site bin directory, the same code works fine.
We are using Aspose.PDF 23.1.0.0, and are not using nor deploying Aspose.Imaging.
The server also hosts SharePoint 2013 web application.
We will surely look further into this matter, can you please share some steps to reproduce the issue along with a sample project .zip format? We will test the scenario in our environment and address it accordingly.
Hi
thanks for helping out!
attaching a zip file that contains a simple web application, where in Default.aspx there is a convert button that generates a pdf file from a html content.
when aspose dlls are deployed to global assembly cache, it gives the mentioned error.WebApplication1.zip (34.8 KB)
In order to replicate the issue, should this sample application be hosted over local IIS server? Also, can you please share how you are writing the assemblies to GAC? Please share the OS Name and version as well so that we can further proceed accordingly.
Hi
Got the error in local IIS and by running a virtual web application from VS.
In our case the assemblies are being deployed through a SharePoint WSP package installation, but a manual installation with gacutil works too.
The issue occured on the following OS versions:
- Windows server 12 R2
- Windows server 2016 Datacenter
thanks!
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): PDFNET-53614
You can obtain Paid Support services if you need support on a priority basis, along with the direct access to our Paid Support management team.
thank you.
is there an estimate on when the fix will be released?
any way to be notified when it does?
The ticket will be investigated and resolved on a first come first serve basis and as soon as we resolve it, we will notify you in this very forum thread. Please spare us little time.
We are sorry for the inconvenience.
Hi
while we wait for the new release, perhaps there’s something I can change in my code to make it work?
I’d also tried to recreate the same error from a console application, but it worked as expected…
Thank you!
The issue may be related to the internal components of the API that may invoke some dependency which is not accessible from GAC. Nevertheless, we are unable to suggest any code or workaround at the moment without completing the analysis and investigation against this issue. We will surely inform you once we make some progress towards ticket resolution. Meanwhile, can you please share complete Stack Trace information along with a screenshot of the issue?
hi
the error is: “Could not load file or assembly ‘Aspose.Imaging, Version=22.12.0.0, Culture=neutral, PublicKeyToken=716fcc553a201e56’ or one of its dependencies. The system cannot find the file specified.”:“Aspose.Imaging, Version=22.12.0.0, Culture=neutral, PublicKeyToken=716fcc553a201e56”
Stack trace (obfuscated):
at #=zHZWXbwinUeD6rnWaOdU40dvtwxlXTxnkXg==.#=zGw4fIzlfsTle(Byte[] #=zzwbyzik=, #=zsuN0E29n8Tgn$KF40EhkeyyYLem5 #=zsQCs17M=, RectangleF #=zVp2KayY=)
at #=zMZNr8oapqaqlC9L410shZH00LxuY.#=z4cpjz0lbYX$(Byte[] #=zzwbyzik=, #=zsuN0E29n8Tgn$KF40EhkeyyYLem5 #=zsQCs17M=, RectangleF #=z18iurEg=)
at #=zP3YRc2y4O5VkuXt1bISDS$EGUef0.#=zgBNPGOo=(#=zMZNr8oapqaqlC9L410shZH00LxuY #=zM058koblKNyS$Psorg==, #=zqLKcA_TOVXC1Ue0kR8KUndmqezXG #=zKKU1JXo=, Single #=zTs4mOZg=, Single #=zzOAb8HA=, #=zWAEJ3jtPS$VpQf7ejPsWTpmZKDgIByFm6g== #=zhWH6GKL6JuLu)
at #=zVdjEAn2FwLiEiZxEnMvJjlqdf7p63PNlLQ==.#=zgBNPGOo=(#=zMZNr8oapqaqlC9L410shZH00LxuY #=zM058koblKNyS$Psorg==, #=zqLKcA_TOVXC1Ue0kR8KUndmqezXG #=zKKU1JXo=, Single #=zTs4mOZg=, Single #=zzOAb8HA=, #=zWAEJ3jtPS$VpQf7ejPsWTpmZKDgIByFm6g== #=zhWH6GKL6JuLu, Boolean #=z$ksgoaNr6Exwc$kKg==, #=zu$mUGXwit7$StS5CR6hJgNPAQKxkkQ6pCQ== #=z7ZT4RRU=)
at #=zMZNr8oapqaqlC9L410shZH00LxuY.#=zIsq4OJ7JfOLpj7IghMM_arA=(#=zkkQSKn3nOGqRg3emWnswmtZ39xVmoTkjOHD9Nbw= #=zJqrxMxxEtAHm, Boolean #=z$ksgoaNr6Exwc_$kKg==, #=zu$mUGXwit7$StS5CR6hJgNPAQKxkkQ6pCQ== #=z7ZT4RRU=)
at #=zMZNr8oapqaqlC9L410shZH00LxuY.#=zqs1Nsl_OwomM(#=zFYMub2PYppPWvRZk1aBc3h732xFOYXhP3w== #=zQFpFp0g=, Boolean #=z$ksgoaNr6Exwc_$kKg==, #=zu$mUGXwit7$StS5CR6hJgNPAQKxkkQ6pCQ== #=z7ZT4RRU=)
at #=zMZNr8oapqaqlC9L410shZH00LxuY.#=z71T7b1kNhLCUEo83Qw==(#=zUgcHRgkGcZJEAGPYQA== #=zDnNX1VTi0$QJj4ebNw==, Boolean #=z$ksgoaNr6Exwc_$kKg==, #=zu$mUGXwit7$StS5CR6hJgNPAQKxkkQ6pCQ== #=z7ZT4RRU=)
at #=zMZNr8oapqaqlC9L410shZH00LxuY.#=z02pelOo=(#=zNjlWLo0Uqgq0klcQ$E9vl8jijYiQPmCw4g== #=zbrWfd9A=, #=z1Pvpz_b3XjM6YmW8WQ== #=zDnNX1VTi0$QJj4ebNw==, Boolean #=z$ksgoaNr6Exwc_$kKg==, #=zu$mUGXwit7$StS5CR6hJgNPAQKxkkQ6pCQ== #=z7ZT4RRU=)
at #=zHtWHjwSi9ACeLdTNOO$S8H_k8UUciEQVWw==.Render(#=zqLKcA_TOVXC1Ue0kR8KUndmqezXG #=zKKU1JXo=)
at #=zibTLUiAuWQe2ZqNhnQDQ0sjpF5JpID4ptg==.#=zT2V0hVqZsOQv(#=zmi6wjj_1kmV7W0Q1Lakm61U= #=zM058koblKNyS$Psorg==, #=zgTZRhVLC2$8c7GCdsHgj5cRsLSc8[] #=zKJsuM3zB240t, #=zqLKcA_TOVXC1Ue0kR8KUndmqezXG #=zKKU1JXo=, TimeSpan #=zvEIkGHA=)
at #=z8kaEPai0rejy3NSQRP1WmpgQfNkO.Render(#=zqLKcA_TOVXC1Ue0kR8KUndmqezXG #=zKKU1JXo=, TimeSpan #=zvEIkGHA=, #=zkL2N_LFOWv$zAqs4NfXMok4=[] #=zy$n8R5o=, #=zJyk3lV9wHmxMB1yyOqXzq7g=[] #=zNp$kY1s=)
at #=z8kaEPai0rejy3NSQRP1WmpgQfNkO.Render(#=zqLKcA_TOVXC1Ue0kR8KUndmqezXG #=zKKU1JXo=, TimeSpan #=zvEIkGHA=, #=zJyk3lV9wHmxMB1yyOqXzq7g=[] #=zNp$kY1s=)
at #=zoegp_AF$JTNN1_eLw4ra1i0lKMDv.Render(#=zqLKcA_TOVXC1Ue0kR8KUndmqezXG #=zKKU1JXo=, #=zRiQhpog= #=zK25zLUg=, TimeSpan #=zvEIkGHA=)
at #=zoegp_AF$JTNN1_eLw4ra1i0lKMDv.Render(#=zqLKcA_TOVXC1Ue0kR8KUndmqezXG #=zKKU1JXo=, #=zRiQhpog= #=zK25zLUg=)
at #=zdC5doTx$zovnNK0LK2cAeg5pvXKE.#=zp0XpeY2gqux1(Stream #=z2dm1gXlKOZwL, Document #=zK3TEFQJAmGKl, HtmlLoadOptions #=zIACBIkN0WZvq, String #=z9Hi0XMrVPBN5)
at #=zdC5doTx$zovnNK0LK2cAeg5pvXKE.#=zyWtiP0s=(Stream #=z2dm1gXlKOZwL, Document #=zK3TEFQJAmGKl, HtmlLoadOptions #=zIACBIkN0WZvq, String #=z9Hi0XMrVPBN5)
at #=zdC5doTx$zovnNK0LK2cAeg5pvXKE.#=zyWtiP0s=(Stream #=z2dm1gXlKOZwL, Document #=zK3TEFQJAmGKl, HtmlLoadOptions #=zIACBIkN0WZvq)
at Aspose.Pdf.Document.#=zQ3PSCiY=(Stream #=zh6teFeQ=, LoadOptions #=zvGSqhXY=)
at Aspose.Pdf.Document…ctor(Stream input, LoadOptions options)
at Infowise.SharePoint.Settings.DAL.Print.AsposePdfProvider.WritePdf(SPSite site, String content, Boolean isLandscape, Stream stream, String title)
at WebApplication1._Default.btnConvert_Click(Object sender, EventArgs e) in C:\Users\genadyv\source\repos\WebApplication1\WebApplication1\Default.aspx.cs:line 32
at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Thank you for looking into it!
This is the first time we are using your components in our products, and at this point the next release of our product depends on this fix, are you able to give me an estimate timeframe for this being resolved?
Thanks for sharing further details. We are afraid that we are unable to share any ETA at the moment as investigation of the ticket is not yet done. As soon as it is complete, we will share updates with you. Please spare us some time.
We are sorry for the inconvenience.
Hi,
it’s been almost a month, and several of our components releases are delayed…
I’ve tried using the latest version of Aspose.PDF (23.2.0), nd the issue still exists.
Do you have any updates regarding the fix?
thank you
The issue is currently under the phase of the investigation. It is speculated that the issue is related to the obfuscation. Also, there are other issues in the queue prior to this ticket. We will surely work on fixing this ticket on first come first serve basis and let you know once the ticket resolved. We apologize for the inconvenience.