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: keep getting error when starting kiosk only when using Chrome

Descripción

Whenever using the same sitekiosk config but using the Chrome browser the kiosk will just keep failing to restart and go into emergency mode. If IE skin is used it starts correctly. Can't seem to find what the issue is. We can no longer use IE due to no longer compliant with application any longer.

Respuesta: (1)

Re: keep getting error when starting kiosk only when using Chrome 16/04/2021 16:26
Hello,

Thank you for your inquiry. Based on your files, the error that you are seeing when you start SiteKiosk cannot be easily identified. I had tested your configuration file and found no fault with it. Do you see this behavior between Start Once or Auto Start modes?

However, there might be some clues based on your log files. You will get an error ("[SiteKiosk] Notification: According to the windows monitoring rule") if your program window matches the criteria. See log excerpt below:


0 0000 2021-04-15 13:11:33 -0400 [SiteKiosk] Notification: According to the windows monitoring rule(Title:'*emote*' Class:'#32770') the window (Title:'LogMeIn Remote Control' Class:'#32770') will be closed
20 0000 2021-04-15 13:11:34 -0400 [SiteKiosk] Notification: Beginning deletion of temporary internet files.
20 0000 2021-04-15 13:11:34 -0400 [SiteKiosk] Notification: According to the windows monitoring rule(Title:'*' Class:'CabinetWClass') the window (Title:'Windows Update' Class:'CabinetWClass') will be closed
20 0000 2021-04-15 13:11:34 -0400 [SiteKiosk] Notification: According to the windows monitoring rule(Title:'*' Class:'CabinetWClass') the window (Title:'Computer' Class:'CabinetWClass') will be closed
20 0000 2021-04-15 13:11:34 -0400 [SiteKiosk] Notification: According to the windows monitoring rule(Title:'*' Class:'CabinetWClass') the window (Title:'Logfiles' Class:'CabinetWClass') will be closed
20 03ee 2021-04-15 13:11:34 -0400 [SiteKiosk] Screen Saver activated after 0 seconds
...............
20 0000 2021-04-15 13:11:37 -0400 [SiteKiosk] Notification: Window can't be closed. (Title:'LogMeIn Remote Control' Class:'#32770' HWND: 197306)


If you are part of a domain, then your domain security settings or anti-malware software could affect launching SiteKiosk. See example post - https://www.provisio.com/en-US/CustomerSupportCenter/ArticleDetails.aspx?ArticleID=25676 .

The other known specific cases where a problem can occur when starting SiteKiosk is:

1. SiteKiosk was installed without the appropriate Microsoft Visual C++ redistributable (only happens if you use the MSI file instead of SiteKiosk9.exe)

2. If you have reactivated the Windows account "Administrator" (with the name Administrator) and start SiteKiosk in this account

3. (May not be applicable) You are connected via Windows Remote Desktop at that time:

-Because: Windows RDP and SiteKiosk interfere with each other and SiteKiosk will not start in "Start once" mode. (you only see the Watchdog background when starting SiteKiosk in “Start once” mode).

- The only workaround is using another remote desktop application OR activating the “Auto start” mode and only access the machine via RDP again after reboot and SiteKiosk startup.

Otherwise, you can:

- Test a new configuration file with defaulted settings. If the issue , persist, then proceed to next step. if not, then edit your new configuration file to reflect the old one.

- Test on another computer, SiteKiosk newest version (no license is needed for testing), and use both older and new configuration files to observe the behavior.

- Test Start Once vs Auto Start modes and observe the behavior. If there are domain or other user restrictions, you will notice the deference.

- Last, either reinstall SiteKiosk on the affected computer or review your domain settings affecting SiteKiosk on this computer. You will only get this message,

"40 0400 2021-04-15 13:14:51 -0400 [SiteKiosk] SiteKiosk was not able to start properly for 10 times in 300 seconds or the SiteRemote Client service did not start in time, therefore the emergency screen has been started."

if SiteKiosk was unable to run properly or is being impacting by something else on the system. See FAQ on Emergency Screen:
https://www.provisio.com/en-US/CustomerSupportCenter/ArticleDetails.aspx?ArticleID=25180

Hopefully, these suggestions would help.

Best regards,
Andre.