Company Christmas Holidays
North American Headquarters in Miami, USA: Dec 25, 2015, Jan 1st 2016
European Headquarters in Muenster, Germany: Dec 21, 2015 until Jan 03rd 2016
Limited support is available during this period.
We at PROVISIO wish you Merry Christmas and a Happy New Year!


Support Request: Log explanation


Good evening,

on a specific machine everyday I have quite the same error logs hanging around.

As reported in the attachment, some logs repeatedly create on the same hour and minute everyday, we have no scheduled job (apart from the scheduled restart, done via SiteRemote) nor the machine is shutdown via power interruption, there are process done by sitekiosk that can cause those log creation (ex. Previous SiteKioskNG instance has not been shutdown properly)?

After the scheduled restart at 04:00 AM, the machine cannot load some DLL, can those error be created because the user SiteKiosk hasn't enough permission?

Last but not least, after 15 min SiteKiosk restart himself, clearing everything, but on this particular machine this procedure lasts 5 to 10 minutes, on the other machine it last about 15 seconds. Those machine are same model and version. Any ideas on what can cause this delay in the restart?

Thanks in advance,

Answer: (5)

Re: Log explanation 8/31/2020 9:24 AM

All errors with [Windows/Application] and [Windows/System] are just forwarded from the Windows Event log of that machine. Therefore, you will have to check its cause on the operating system level.

E.g. [Windows/Application] [21/08/2020 04:00: Microsoft-Windows-Perflib] Impossibile caricare la DLL dei contatori flessibili "C:\windows\system32\sysmain.dll" (codice di errore Win32 126).
Applies to the performance counters on Windows.

You may first check if it helps to rebuild the Performance Counter Library on the Windows computer (locally as admin via command line) with "LODCTR /R"

The “SiteRemote Client” service of SiteKiosk uses WMI queries to request Windows system / performance information for sending them to SiteRemote.
Therefore it is necessary to have WMI Services properly running.

You should also check the other error messages with [Windows/Application] and [Windows/System] (e.g. on the Microsoft website) if they interfere with the operation of the kiosk system.
For further details you may also check this directly in the Windows Event log on that machine.

[SiteKioskNG] Previous SiteKioskNG instance has not been shutdown properly.

This Log entry appears if the SiteKioskNG instance (Chromium CEF Browser) doesn’t close within 60 seconds. Then the watchdog does kill this old instance before the new instance is started and writes this entry to the log.

SiteKiosk (and also the browser instance) will e.g. be restarted when pressing Logout or when the screen saver activates.

The log entry “Previous SiteKioskNG instance has not been shutdown properly.” may appear more often on systems with lower performance or also sometimes on systems with good performance because the Windows system is busy with other tasks. But if the SiteKiosk browser is finally restarted you should not worry about it too much.

>>> Last but not least, after 15 min SiteKiosk restart himself,<<<
For this you may first check / compare the screen saver settings in the SiteKiosk configuration (idle time).

Michael Olbrich
Re: Log explanation 9/2/2020 11:33 AM
Thanks for the logs explanation.

I've executed the command "LODCTR /R" but this morning I had the same error log on the machine.

I've checked WMI Services and they are up&running.

For the restart time, I will check the configuration file and modify it.

Re: Log explanation 9/2/2020 12:42 PM

The command "LODCTR /R" was just an idea how to solve the Performance Counter error in the event log.
Otherwise you will have to continue to search for answers at the operating system level and contact Microsoft if necessary.
The same applies to the other warnings and errors from the Windows Event log.
All errors with [Windows/Application] and [Windows/System] are just forwarded from the Windows Event log of that machine.
These have nothing to do with SiteKiosk and concern the operating system.

Michael Olbrich
Re: Log explanation 9/3/2020 10:42 AM

my last comment was only an update on my current situation, nothing else intended :)

I'm now investingating further in the Windows logs viewer to understand better the situation, I'm aware that this problem is Windows related.

Re: Log explanation 9/3/2020 10:55 AM
No problem. Thank you for your feedback.