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

 

Запрос поддержки: Standard Windows Print Dialog Box does not open

Описание

After the upgrade to ver 9.8.5547, when a pdf is opened in the sitekiosk interface, the windows print dialog box no longer open after pressing the print icon.
It works if the PDF is opened in Adobe Reader DC but i can not controll where the PDF is opened.
I have one more Sitekiosk PC with ver. 9.7.5026 and all work fine.
The Adobe Acrbat Reader DC is the exact same version on both.

Ответ: (10)

Re: Standard Windows Print Dialog Box does not open 15.09.2020 9:42
I forgot to mention that the PC with Sitekiosk 9.8 has been updated to Windows version 2004.
The PC with Sitekiosk 9.7 has Windows version 1909
Re: Standard Windows Print Dialog Box does not open 15.09.2020 10:18
Hello,

I am sorry, but that is currently a known bug of that version. There is currently no exact date, when a fixed version will be available.

If you need that feature, you have to revert back to the older 9.7 version.
Re: Standard Windows Print Dialog Box does not open 15.09.2020 10:43
Ok, i see the latest 9.7 version is 9.7.5324.
Can i use this with without the PDF bug and on Windows version 2004?
Thanks
Re: Standard Windows Print Dialog Box does not open 15.09.2020 11:03
Hello,

there are no known problems with that version of SiteKiosk and Windows 10 2004.
Re: Standard Windows Print Dialog Box does not open 15.09.2020 16:17
Hi, i have removed the 9.8 and installed the 9.7 but the issue remains the same: the printer windows does not open!
It works only if i run sitekiosk logged as domain administrator user but i can't use in this way.
Then, i tried to make the user I use for SiteKiosk local administrator on the pc but it doesn't work.
Please i need a workaround/solution.
Thanks.
Pages (2): [1] 2 Next »