|
|
Rank: Newbie
Groups: Member
Joined: 4/15/2019
Posts: 1
|
I'm interested to find out if anyone has got pdf generation working using eo.pdf. If not, is it even possible?
Appreciate any feedback.
Thanks
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Hi,
A lot of our users use EO.Pdf in Azure. Which type of Azure service you use and what error did you get?
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 4/24/2019
Posts: 2
|
I'm having troubles using EO.PDF in Azure App Service as well.
When I call the function ConvertUrl, the parameter URL never gets hit and the website keeps pending on ConvertUrl until I get an error after minutes. On my local machine it's saying "Failed to resolve LoadLibrary" and I assume it's the same error on Azure, I just can't find a way to check that. The browser is giving me "502 - Web server received an invalid response while acting as a gateway or proxy server." on Azure, assuming that some sort of time out took place.
This was resolved on my local computer after I enabled the 32 bit application setting in my application pool. On Azure App Service however, I'm limited in options. There is an option to run your application in 32 bit mode, but it does not have the same effect as the as the 'enable 32 bits applications' option in the application pool apparently, as I'm still getting the same error.
I'm using EO.Total 2016. Was this perhaps fixed in a newer version?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,071
|
Hi,
The "Failed to resolve LoadLibrary" error would occur when you try to run an older version of EO.Pdf on a newer version of Windows. So you do need to update your EO.Pdf in order to resolve this particular issue. I am not exactly sure whether this is the root of the 502 error though. So you can update the DLL first and see if resolves this issue for you.
The 32 bit mode/64 bit mode option does not matter.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 4/24/2019
Posts: 2
|
Thank you for you answer.
Here is the thing though. Version EO.Total 2016 gives me the "Failed to resolve LoadLibrary" error on my local machine (Windows 10) when I do not enable the 32 bit option. But when I switch it to 32 bit, everything works flawlessly. So I assume the bit settings must have some sort of impact.
Thinking this would solve my problem, I set the application to 32 bit as well in Azure, but it still keeps pending until timeout whenever a PDF gets generated. I cannot immediately see what error it is throwing as it seems that Azure closes the connection due to a timeout before any log can be dumped.
I was aware of the incompatibility of older versions of EO.PDF and newer versions of Window, but I thought version 2016 didn't have this problem.
I'll try to and use the latest version to see if that solves the problem.
|
|