I have downloaded EO.Total 2019.2.91.0 installer.
May I know where can I get License key for that?

Must I need to renew my license to get license key for EO.Total 2019.2.91.0?
I am using 2018 version Eopdf tool before but got many issues on MS Window now.

Please can you advise us if the new version of EO.Total 2019.2.91.0 is compatible with the latest Microsoft Window Update?
I am asking, because our current EO.PDF version 2018 doesn't work with the latest Microsoft Window Update anymore.

Thank you for your reply.

We use 2018 version. It was ok before.
After window update, we got this issue("Failed to start image manager") where in this code HtmlToPdf.ConvertUrl(...).
I closed Autivirus software but I got other Issue may be "Failed to upload library.....".
I tried with EnableEOWP way as I found on google but can't work.
I just want to know if I renew my license and I use 2019.2.91.0 version, can I generate the report well?

Hi,

Thank you for your reply.

we got this Error ("Failed to start image manager") where in this code HtmlToPdf.ConvertUrl(...).

We use Windows 10, version 1903(OS Build 18362.476) on our local.

We use Windows Server 2016, Version 1607 (OS Build 14393.2363) on our server.

Thanks,

Thanks you for your reply and instruction.

It works well on Window 10 now. We are still trying on Server 2016.

Hi,

I got this error "Child process exited unexpectedly." in the statement "HtmlToPdf.ConvertUrl(.......)"
on Window Server 2016 by hosting on IIS.

Why got this error? Please, help how should I solve this error.
We have renewed already our license. We use 2019 license key and all of 2019.
Please, We are waiting your reply.

Thanks.


Error : Stacktrace

at EO.Internal.i3.a(Exception A_0, Boolean A_1)
at EO.Internal.i3.a(o1 A_0)
at EO.Internal.i3.a(Boolean& A_0, axv[] A_1, String A_2, String A_3)
at EO.Internal.i3.a(axv[] A_0, String A_1, String A_2)
at EO.Internal.at6.b()
at EO.Internal.pf.a(Action A_0)
at EO.WebEngine.Engine.Start(WindowsIdentity user)
at EO.Internal.ru.b()
at EO.Internal.mw.a(ru& A_0)
at EO.Internal.aj9.a(at A_0, ru& A_1)
at EO.Internal.ob.e()
at EO.Internal.ob..ctor(at A_0, HtmlToPdfOptions A_1)
at EO.Pdf.HtmlToPdfSession.a(HtmlToPdfOptions A_0)
at EO.Pdf.HtmlToPdfSession..ctor(HtmlToPdfOptions A_0, HtmlToPdfSession A_1)
at EO.Pdf.HtmlToPdf.b.a()
at EO.Internal.aj9.a[a](aox A_0)
at EO.Pdf.HtmlToPdf.ConvertUrl(String url, PdfDocument doc, HtmlToPdfOptions options)
at EO.Pdf.HtmlToPdf.ConvertUrl(String url, String pdfFileName, HtmlToPdfOptions options)
at EO.Pdf.HtmlToPdf.ConvertUrl(String url, String pdfFileName)
at GenerateReport.ReportGenerating(String outputFileName, String url) in c:\Projects\websites\ODDiagnosis\ROE\WebApp\GenerateReport.aspx.cs:line 1738
at GenerateReport.GernerateReportFromPACEAdminPortal() in c:\Projects\websites\ODDiagnosis\ROE\WebApp\GenerateReport.aspx.cs:line 218

Hi,

Sorry about the delay because of Thanksgiving holiday here. Have you tried to enable EO worker process? This usually is due to third party security/AntiVirus application incorrectly kills our child process.

Thanks!

Hi,

Please see this page for details on how to enable EO worker process:

https://www.essentialobjects.com/doc/common/eowp.aspx

There are several ways to enable it, the method we recommend for you is to call this method:

https://www.essentialobjects.com/doc/eo.base.runtime.initworkerprocessexecutable.aspx

Instead of simply setting EO.Base.Runtime.EnableEOWP to true.

When you call the above method, you can try to follow these steps:

1. Manually create a folder on your web server, preferably OUTSIDE of your application folder. For example, you can create an folder "c:/EO";
2. Place eowp.exe inside that folder;
3. Find out the IIS user account under which your application is running, grant that user executable permission to folder "c:/EO";
4. Add code to call InitWorkerProcessExecutable in your Global class's Application_Start event handler and pass the full path "c:/EO/eowp.exe" as argument;

You should never declare EnableEOWP property in your own code. This is our property, not yours. You can't declare a property in your own code and expect setting it has any effect on our library.

After you follow these steps, you can try to call ConvertUrl and use tasks manager to see if you see eowp.exe in your running processes. If you do see eowp.exe there, then it means EO worker process has been successfully enabled.

Hope this helps.

Thanks!

Hi,

This step may need to be done by your system administrator or hosting company and the exact step can vary slightly depending on version of Windows you are running. Since this is more a generic Windows administration issue rather a direct programming issues related to our product, we can only explain you the basic concept here, you can then search online for the exact steps or contact your hosting company to do the actual change for you.

When your web application is hosted on IIS, IIS would run your application under a certain user account configured by you. For example, the worst configuration would be to run your application under "Administrator", this way if you accidentally have a bug in your code that would wipe out the system drive, you could do so since your code is running under Administrator. Obviously this is a bad configuration. So typically IIS would configure to run your application under a much less privileged account. For example, an user in the IIS_IUSRS group. For demonstration purpose, say it's running under account MIS_WEBSITE.

Now since your application is running under MIS_WEBSITE account, if you put eowp.exe at "c:/EO/eowp.exe" and try to start it (by our code) but MIS_WEBSITE account does not have execute permission on "c:/EO" folder, then the step in our code that starts child process "c:/EO/eowp.exe" will fail. To resolve this issue, you must make sure MIS_WEBSITE does have execute permission on "c:/EO" folder. Obviously here "c:/EO" folder is just an example. You can put it anywhere. The key is your code must have permission to launch process from that folder.

Hope this clears up.

Thanks!

Dear EO,

Do you have any update to solve this issue?

We can't generate the report on Microsoft Server 2016.

otherwise, If you are building a new version for this issue, let us know.


We are looking for your reply.

Thank you so much,
MIS Admin