Welcome Guest Search | Active Topics | Sign In | Register

PDF Export Error: "The request was canceled" Options
ckmba
Posted: Thursday, May 7, 2026 4:24:35 PM
Rank: Member
Groups: Member

Joined: 4/25/2013
Posts: 18
Hello Essential Objects Team,

We are currently testing our application running in an AWS container using a Windows Server 2022 (Full) Windows container. We are using EO.Pdf version 24.2.81.0.

When exporting HTML to PDF, we encounter the following exception when font styling is present:

`HtmlToPdfException: The request was canceled`

We have confirmed that:

* Exporting very simple HTML without font styling succeeds
* Adding font styling causes the request to be canceled
* This behavior closely matches the issue described in the following forum post from 2023: https://www.essentialobjects.com/forum/postst11598_EOPdf-20025-The-request-was-canceled-error.aspx

In our container environment, standard system fonts such as Arial and Segoe UI are not present by default, and we have not found a Microsoft-supported, container-safe way to reliably restore those fonts at image build time. We understand that previous guidance referenced installing fonts on the server, but this is not trivial in Windows container environments.

Our questions are:

1. Has this issue been addressed or improved in more recent versions of EO.Pdf (post‑2023)?
2. Is installing system fonts still the recommended solution in containerized Windows environments?
3. Does EO.Pdf officially support Windows containers, and if so, is there guidance or configuration recommended to avoid this font-related failure?
4. Are there alternatives supported by EO.Pdf (e.g., embedded fonts, different rendering options, or configuration flags) that avoid relying on OS-installed fonts?

Any guidance on supported approaches for running EO.Pdf in Windows containers would be greatly appreciated.

Thank you for your time and assistance.

Best regards,
RM
eo_support
Posted: Thursday, May 7, 2026 5:38:01 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,496
Hi,

We have not made any changes particularly for this issue. However the Chromium browser engine might have --- so the easiest way to find out is to run the latest build in your environment and see if it resolves the issue for you. If the problem still occurs, please send us the runtime log and we will investigate further:

https://www.essentialobjects.com/doc/common/collect_logs.html

Based on our previous investigation, installing font is the recommended solution for container image that does NOT include those fonts (which is the case for Nano Server and Windows Server Core) because it does not require modification of individual input HTML files. However you should be able to avoid such issue using @font-face CSS directive to directly supply the font data in the CSS. This will satisfy the browser engine thus avoid triggering a fault check.

Hope this helps.

Thanks!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.