|
|
Rank: Newbie
Groups: Member
Joined: 8/5/2019
Posts: 4
|
We are using EO Total 2018 to convert our html pages to PDF. In one of our customer machines (Windows 2016 OS) we are seeing the following errors:
System.Exception: Failed to resolve LoadLibrary.
at EO.Internal.jq.b.d()
at EO.Internal.jq.b.a(bac[] A_0, String A_1, String A_2)
at EO.Internal.jq.a(Boolean& A_0, bac[] A_1, String A_2, String A_3)
at EO.Internal.jq.a(bac[] A_0, String A_1, String A_2)
at EO.Internal.jq.o.c()
at EO.Internal.jq.o.f()
at EO.Internal.jq.n()
at EO.Internal.jq.a(Boolean& A_0, bac[] A_1, String A_2, String A_3)
at EO.Internal.jq.a(bac[] A_0, String A_1, String A_2)
at EO.Internal.aqf.a(String A_0, String A_1)
at EO.Internal.av9.b()
at EO.Internal.av9.a(WindowsIdentity A_0)
at EO.WebEngine.Engine.Start(WindowsIdentity user)
at EO.Internal.s1.b()
at EO.Internal.ns.a(s1& A_0)
at EO.Internal.al1.a(av A_0, s1& A_1)
at EO.Internal.pd..ctor(av A_0, HtmlToPdfOptions A_1)
at EO.Pdf.HtmlToPdfSession.a(HtmlToPdfOptions A_0)
at EO.Pdf.HtmlToPdfSession..ctor(HtmlToPdfOptions A_0, Boolean A_1)
at EO.Pdf.HtmlToPdfSession.Create()
This is followed by:
System.Exception: Failed to start image manager
at EO.Internal.jq.o.c()
at EO.Internal.jq.o.f()
at EO.Internal.jq.n()
at EO.Internal.jq.a(Boolean& A_0, bac[] A_1, String A_2, String A_3)
at EO.Internal.jq.a(bac[] A_0, String A_1, String A_2)
at EO.Internal.aqf.a(String A_0, String A_1)
at EO.Internal.av9.b()
at EO.Internal.av9.a(WindowsIdentity A_0)
at EO.WebEngine.Engine.Start(WindowsIdentity user)
at EO.Internal.s1.b()
at EO.Internal.ns.a(s1& A_0)
at EO.Internal.al1.a(av A_0, s1& A_1)
at EO.Internal.pd..ctor(av A_0, HtmlToPdfOptions A_1)
at EO.Pdf.HtmlToPdfSession.a(HtmlToPdfOptions A_0)
at EO.Pdf.HtmlToPdfSession..ctor(HtmlToPdfOptions A_0, Boolean A_1)
at EO.Pdf.HtmlToPdfSession.Create()
The same code is working fine is 99% of our deployments. This is is the only machine where this is occurring.
In the working machines, we see there are 5 instances of rundll32.exe running after which the PDF gets generated. In the machine where the problem happens, only one instance of rundll32.exe starts and then ends quickly without making further instances. We are unable to reproduce this issue locally in any of our environments.
We initially thought the issue could be with the Symantec Antivirus software and hence disabled the same and tried. Still we are seeing the same behaviour. We have checked the windows event viewer but are not seeing any significant errors related to EO. Any idea what could be causing this only on this machine?
Our code is running as a .NET 4.6.1 windows service and the following EO DLLs are deployed on the EXE location:
EO.Pdf.dll
EO.Web.dll
EO.WebBrowser.dll
EO.WebEngine.dll
EO.Base.dll
Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
Please update to the latest build and see if it resolves the problem for you. This is an issue triggered by a Windows update from Microsoft and we have since worked around the issue in our newer builds.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 8/5/2019
Posts: 4
|
Do you have any idea after which windows update version this happens? Need to know this to convince our customer that this is because of the window update.
Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
We did not track the exact update number because the same change are being pushed down to different version of Windows in different updates. We first noticed this issue late last year when Microsoft released Windows 10 1809. We have since changed our code to work around this issue and the change should work on other version of Windows as well.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 8/5/2019
Posts: 4
|
Our customer is on Windows Server 2016 Standard on both the machines.
Machine with this issue: Version: 1607, OS Build Number: 14393.2312
Machine without this issue: Version: 1607, OS Build Number: 14393.2906
Do you still think this could be related to windows update?
We will be able to upgrade to the latest version only in our next release. But currently the customer would like to make it work in all the machines in their environment or atleast would like to know what is causing this. Any suggestions?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
We have no way of testing every builds on every possible Windows version with every possible update. We are aware of this issue and we have no new report of this same issue after we have resolved it. So we believe the same fix should work for your Windows as well. As a simple test, you can download the latest build from our download page and run the TabbedBrowser sample application to see if it is indeed resolved in your specific environment.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 8/5/2019
Posts: 4
|
Hi,
That is not helping us. Our local environment do have the same OS update version and hotfixes installed as that of our customer environment. But we are unable to reproduce the issue. Anyways, we will try out the version with the fix on our customer machine to check if that resolves the issue. But we are on EO Total 2018 and which update with this fix is compatible with this version? i.e., without any other breakages and also should work by replacing only the EO DLLs. Because using EO DLLs from Total 2019 won't work unless we rebuild our application and we are not sure what other breaking changes may be there.
Thanks.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
This issue was not resolved in EO.Total 2018. It was resolved in our first EO.Total 2019 build.
EO.Total 2019 and EO.Total 2018 are MOSTLY backwards compatible however they use two different versions of Chromium browser engine. EO.Total 2018 is based on Chromium V62 and EO.Total 2019 is based on Chromium V70. Just like the same web page can have subtle differences when loaded into different browsers/different versions of the same browser, you may observe subtle differences between the two versions as well. For the vast majority of the pages, nothing will be affected, however because changes do exist (in fact a lot of it made in the browser engine) so you should still test your application after you rebuild with the new version. We do not expect any serious issues, however if you do notice any issues, you can let us know and we will be happy to investigate.
Thanks!
|
|