Рождественские праздники компании
Североамериканская штаб-квартира в Майами, США: 25 декабря 2015, 1 января 2016
Европейская штаб-квартира в г. Мюнстер, Германия: с 21 декабря 2015 по 3 января 2016
Ограниченная поддержка доступна в течение этого периода.
PROVISIO желаем вам веселого Рождества и счастливого Нового Года!

 

Сообщение об ошибке: Triggering a PRINT request to Adobe Reader gives no result

Воспроизведение

We have a webapplication which allows users to request a document. This document is produced in a backend system in PDF format and is sent to the browser (we use the IE11 mode) to a hidden frame.

We then use the SiteKiosk Object Model to request a print of the frame that holds the PDF (teh largest frame at that moment).

This normally results in Adobe Reader opening and printing the file. No interaction of the users is required (and that is the whole reason for the setup).

However when the PDF is a signed document (using a certificate from a Belgian signing authority), then the request to print has NO effect.

When the PDF is not signed, all print requests are excecuted properly.

We have checked the presence of the correct certificates on the PC, we have also check the printing of the PDF outside SiteKiosk under Adobe Reader (which works properly).

We would like to know how we can furher investigate this issue, as it affects our users daily.

It is also not a good answer to advise us to use Chrome mode, as the documentation of the SiteKiosk Object model for Chromium is virtually non existent. What documentation we could get from Provisio developpers on the SiteKiosk Object Model for Chromium is not up to date with the version of Sitekiosk we have 9.5.4033. We have tried to build a webapplication using the info we received, but this was not sufficient for our developpers to get it to work. So using Chromium is not an option. The printing part seems not as well implemented as in IE11 mode.

The vexing part is that printing works with non signed PDF's, so why is a print request ignored when a signed PDF is used ?

One could argue this is an Adobe Reader problem, but then how do you explain that A.R. prints properly when not used under the SiteKiosk protection ?

We feel this is caused by the fact that we run under SiteKiosk "protection" and need help in finding out why printing of signed PDF's fails.

Any tips for investigation are greatly appreciated,

Описание

We have a webapplication which allows users to request a document. This document is produced in a backend system in PDF format and is sent to the browser (we use the IE11 mode) to a hidden frame.

We then use the SiteKiosk Object Model to request a print of the frame that holds the PDF (teh largest frame at that moment).

This normally results in Adobe Reader opening and printing the file. No interaction of the users is required (and that is the whole reason for the setup).

However when the PDF is a signed document (using a certificate from a Belgian signing authority), then the request to print has NO effect.

When the PDF is not signed, all print requests are excecuted properly.

We have checked the presence of the correct certificates on the PC, we have also check the printing of the PDF outside SiteKiosk under Adobe Reader (which works properly).

We would like to know how we can furher investigate this issue, as it affects our users daily.

It is also not a good answer to advise us to use Chrome mode, as the documentation of the SiteKiosk Object model for Chromium is virtually non existent. What documentation we could get from Provisio developpers on the SiteKiosk Object Model for Chromium is not up to date with the version of Sitekiosk we have 9.5.4033. We have tried to build a webapplication using the info we received, but this was not sufficient for our developpers to get it to work. So using Chromium is not an option. The printing part seems not as well implemented as in IE11 mode.

The vexing part is that printing works with non signed PDF's, so why is a print request ignored when a signed PDF is used ?

One could argue this is an Adobe Reader problem, but then how do you explain that A.R. prints properly when not used under the SiteKiosk protection ?

We feel this is caused by the fact that we run under SiteKiosk "protection" and need help in finding out why printing of signed PDF's fails.

Any tips for investigation are greatly appreciated,

Ответ: (1)

Re: Triggering a PRINT request to Adobe Reader gives no result 15.11.2019 15:40
Hello,

Generally SiteKiosk 9.5 is out of support and also please understand that our free support cannot offer any assistance with creating your own object model code.

But here some general hints:
You may first check if it works when starting SiteKiosk in “Start once” mode (in the user account where it works outside of SiteKiosk) to exclude effects caused by user-dependent settings.
In case it works check outside of SiteKiosk while logged in as SiteKiosk user.
Here the information how to get access:
https://www.provisio.com/en-GB/CustomerSupportCenter/ArticleDetails.aspx?ArticleID=5826

Or maybe this Adobe Setting helps?
https://www.technipages.com/acrobat-reader-11-fix-there-was-an-error-opening-this-document-access-denied
https://community.adobe.com/t5/Acrobat-Reader/Windows-10-cannot-open-pdf-files-in-Reader-DC/td-p/7525324


Otherwise you may also check with selecting different printing behaviors at “Print” in the SiteKiosk configuration (e.g. show standard windows print dialog box) for testing.

>>>we have also check the printing of the PDF outside SiteKiosk under Adobe Reader (which works properly).<<
Why you don’t just also use this in SiteKiosk but added object model code?
If it works in IE it should also work in SiteKiosk without using any SiteKiosk Object Model code.

Last but not least you also should check the SiteKiosk log for errors at the time the problem occurs.

Regards,
Michael Olbrich