Vacaciones de Navidad de la empresa
Desde el 21 de Diciembre 2015 hasta el 3 de enero 2016, nuestra oficina en Münster trabaja con un equipo mínimo. Soporte limitado está disponible durante este período.
Deseamos a ustedes y sus familas Feliz Navidad y un próspero año nuevo.

 

Soporte de pedidos: Issue with 3rd part application

Descripción

Hello,

We are currently evaluating SiteKiosk in order to decide whether to commit to a purchase or not.
Our intent is to run our visitor software "Pronestor Visitor" within SiteKiosk to ensure a secure environment.

After the intial setup I've ran into an issue with running the visitor software. Running it through the configurator > Applications > Test works fine, however when i set it to start automatically and start sitekiosk I'm greeted with the below error.

---------------------------
RegistryLicensedApplication Error
---------------------------
Error executing application: 'C:\\Flags\en-US.png'
Details : vid System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement)
at System.Drawing.Image.FromFile(String filename)
at Selfregistration.Panels.CLanguageController..ctor()
at Selfregistration.Panels.LanguagePanel.InitializeLanguageButtons()
at Selfregistration.Panels.LanguagePanel..ctor(MainForm pMainForm)
at Selfregistration.MainForm..ctor()
at Selfregistration.MainForm.Main()
---------------------------
OK
---------------------------


As far as I can tell, Prontestor Visitor is unable to find its "Flag" folder where some resources are located, causing it to stop from running. Potentially due to it being ran in a different context?
I've tried to paste the entire installation folder into SiteKiosk root folder, but the result was the same.

Would you have any kind of resultion to this error? I was thinking of symlinks or similar but seeing the double slash made me unsure what actually is going on...

Kind Regards,
Christian

Respuesta: (8)

Re: Issue with 3rd part application 14/08/2019 13:40
Hi,

the solution is quite easy. As SiteKiosk is operated within a locked down user account, there is no access to that part of the file system where your software is installed. To handle this, you have to do some configuration changes:

1) log in as administrator
2) start the program SystemSecurity.exe which is located in the installation folder of SiteKiosk (e.g. C:\Program Files (x86)\SiteKiosk)
3) choose the customize option and adjust the access to the filesystem as needed
4) apply the changes

After that, please start SiteKiosk in auto start mode.

Regards Martin
Re: Issue with 3rd part application 14/08/2019 14:58
Hello Martin,

Would there be any way to receive a time limited trial of the registered version?
Following your mentioned steps prompts me with the message that any changes performed in the SystemSecurity program will get discarded.

Kind Regards,
Christian
Re: Issue with 3rd part application 14/08/2019 15:12
Hi Christian,

please send your request to sales-europe(at)provisio.com. They will create a time limited test key for you.

Regards Martin
Re: Issue with 3rd part application 15/08/2019 8:02
Hello Martin,

Unfortunately I'm still left with the same error.
I've also tried to enable the standard windows user profile as well as deactive the SystemSecurity both resulting in the same error as before. I am enabling the auto-boot to ensire that the restricted account is being used, but it appears that there is no difference cause the same error is being thrown even when running with the "run once option" from the administrator account / normal user with elevated permissions to enter the configuration tool.

I noticed that after restarting SiteKiosk and entering the configuration tool that the test applicatoin button also fails after the restart. However when i simply re-add the program the test button works fine again. There is a difference in the error being thrown however when clicking the test button; As you can see below a longer path is being displayed.

---------------------------
RegistryLicensedApplication Error
---------------------------
Error executing application: 'C:\Program Files (x86)\SiteKiosk\ConfigServer\Flags\en-US.png'
Details : vid System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement)
at System.Drawing.Image.FromFile(String filename)
at Selfregistration.Panels.CLanguageController..ctor()
at Selfregistration.Panels.LanguagePanel.InitializeLanguageButtons()
at Selfregistration.Panels.LanguagePanel..ctor(MainForm pMainForm)
at Selfregistration.MainForm..ctor()
at Selfregistration.MainForm.Main()
---------------------------
OK
---------------------------

As there is no upload button, I've gone ahead and uploaded my logfiles to dropbox. If of interest you can download them with the below link:
https://www.dropbox.com/s/u5m9cxhba59f6ez/Logfiles.zip?dl=0

Would you have any solution for this?

Kind regards,
Christian
Re: Issue with 3rd part application 15/08/2019 11:31
Hi,

from the log files you can see that the window and dialog management is closing some windows which are opened by your application:

0 0000 2019-08-14 11:40:58 +0200 [SiteKiosk] Notification: According to the windows monitoring rule(Title:'*' Class:'CabinetWClass') the window (Title:'proNestor Visitor' Class:'CabinetWClass') will be closed
20 0000 2019-08-14 11:40:58 +0200 [SiteKiosk] Notification: According to the windows monitoring rule(Title:'*' Class:'CabinetWClass') the window (Title:'Alla objekt på Kontrollpanelen' Class:'CabinetWClass') will be closed
20 0000 2019-08-14 11:40:58 +0200 [SiteKiosk] Notification: According to the windows monitoring rule(Title:'*' Class:'IEFrame') the window (Title:'SiteKiosk Help - Internet Explorer' Class:'IEFrame') will be closed
20 0000 2019-08-14 11:41:00 +0200 [SiteKiosk] Notification: Window can't be closed. (Title:'SiteKiosk Help - Internet Explorer' Class:'IEFrame' HWND: 853096)

This will probably stop your application. Please see the SiteKiosk help for handling exceptions for the monitoring rules: https://www.provisio.com/helpconsole/SiteKiosk%20Help/en-US/default.htm?windows___dialoge.htm
With changes on this the program shall be operable.

Regards Martin
Pages (2): [1] 2 Next »