Rank: Newbie Groups: Member
Joined: 12/21/2017 Posts: 1
|
My work got a license for a much older version of your product. It worked fine on IIS 6 server (2003 box). Recently we migrated to IIS web app to server 2016 and the eo.pdf.html.dll fails to create pdf files. Interestingly, it works on the 2016 box outside of IIS. Could it be configuration on the IIS side that caused the issue? Or do we need to get the latest version of your product? Thanks.
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,221
|
Hi,
We would definitely recommend you to get a new license for the current version. Version 3 was released 2011 and Windows Server 2016 was released in 2016. So not only your version of EO.Pdf is not tested on Windows Server 2016 because it was released 5 years earlier, but a lot have changed during that five years, both on the OS side and on the browser engine (that EO.Pdf uses) side.
On the browser engine side, the current version uses a much newer browser engine. Your version uses a WebKit based browser engine that was released in 2011. The current version uses Google Chromium based browser engine, which has a much larger user base and is being much more actively developed. We also regularly refresh the browser engine to keep it up to date. Web browser evolves very fast these days due to several reasons: features, technical standards, security, etc. While the customers may not care about all of them, to everyone at least some of them matters. Take security as an example, the Chromium team has put in numerous security patches over the years --- they patch very quickly largely because the whole source is open and is widely and thoroughly scrutinized over and over. And this is one of the reason that we switch to such a widely used browser engine. So in away running the version you are running is like running Windows without installing any security patches for 5 years. It's definitely not a good idea.
On the OS side, Windows has continued to improve security and performance. As a result, the Chromium browser engine has moved to more efficient APIs that only exists in newer version of Windows and discontinued support for older version of Windows. The new updates introduced by MS, on the other hand, broke some API our older version were relying on and resulted in older versions of EO.Pdf having problems on Windows 10. So the old + new combination causes problem in both directions. As such the best way is keep both up to date.
Additionally, we only provide free tech support for one year with the initial order. After the first year if you wish to continue receive tech support, you can renew your subscription, which would cover both tech support and free version upgrade. So if you have never renewed your subscription, then your tech support would have expired a long time ago. A new order would restart the one year tech support period for you. So after that if you still run into any problems, we will be happy to assist you further.
Please feel free to let us know if you have any question.
Thanks!
|