|
|
Rank: Newbie
Groups: Member
Joined: 4/16/2008
Posts: 8
|
Hello ! In our production environment we have had issue on a v2015 EO.PDF (unable to generate large pdf files). To fix it, we decided to upgrade to the latest version as it often what you advise and see if it fix the issue. It worked great on our local test environment so we pushed it and we have an error there: Child process exited unexpectedly We tried to troubleshoot, I did the steps detailed here : https://www.essentialobjects.com/forum/postsm51733_Troubleshooting-Child-process-exited-unexpectedly.aspx#51733But unfortunately still the same issue. I will send you the logs from your GetLogs method after I finish this post. Unfortunately after reverting, none of the HtmlToPdf works anymore so we now have a major issue. Can you please advise? Do you need more info? Thank you very much.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,182
|
Hi,
What version of Windows are you running?
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 4/16/2008
Posts: 8
|
Thank you for your help
Microsoft Windows Server 2008 R2 Standard 6.1.7601 Service Pack 1 Build 7601
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,182
|
This is not supported. You will need at least Windows Server 2012 R2. The log shows several Windows API calls are missing on your system. Those APIs only exists on Windows Server 2012 R2 and newer.
|
|
Rank: Newbie
Groups: Member
Joined: 4/16/2008
Posts: 8
|
Fair enough the OS is supposed to be replaced for a while now..
Where could I have seen that this OS was not supported anymore?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,182
|
Hi, There is no current information on Windows 2008 because that support for that system has ended a long time ago. Because our product relies on Google's Chromium browser engine, what OS are supported directly depends on what OS Chromium supports. You can find supported OS information from Google here: https://support.google.com/chrome/a/answer/7100626?hl=enYou would first find out the Chromium version used by our product (you can load chrome://version in our TabbedBrowser sample application to find out), then use that version information to find out what OS is supported. For example, in the above article it states the latest version that supports Windows 7 is Chromium V109. Because our latest build is based on Chromium V111, it means the latest version does not officially support Windows 7 (in reality it may work but with some problems). Additionally, you can find Windows end of support timeline here: https://cloud.google.com/compute/docs/instances/windows/end-of-supportGenerally, everything will stopped being supported on a specific OS when Microsoft declares end of support on that OS. This is because frequently developers would need to work together with Microsoft to address some issues. That becomes impossible when Microsoft enters end of life for a specific Windows. As a result, all down stream products will stopped support it as well. Hope this helps. Please feel free to let us know if you have any more questions. Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 4/16/2008
Posts: 8
|
Just my two cents but a quick information on supported OS would have avoided this post.
I understand about the Chromium dependency and the logical limitation.
Our logic is more when and until when does it work rather than how.
Thank you for your help anyway !
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,182
|
I agree. Thank you very much for your valuable feedback.
|
|