Support Request: Screen with forbidden access in white

Description

Hello,

our customer has this sign on 3 android tablets under Sitekiosk. We have never seen this screen because we generaly work with the Windows version.

Can you tell us what is the cause of that screen and if we can resolve this problem at distance with Siteremote ?

Thank you very much!

KR
Denis

Answer: (3)

Re: Screen with forbidden access in white 6/21/2018 10:16 AM
Hello,

This is a general blocking sign from SiteKiosk Android that can appear when e.g. a surfing area restriction applies or when another Android app will start that is blocked.
Further information you will find in the SiteKiosk Android log (on SiteRemote or locally on the device at “…/SiteKiosk/Logs”.

Regards,
Michael Olbrich
Re: Screen with forbidden access in white 6/22/2018 3:32 PM
Hello,

we have test on a tablet, but the sign is in red when accessing to a restricted area and disapear rapidly. In this case, the sign is white and the tablet is blocked. May be is it a problem of the tablet and not of Sitekiosk ?

We have another problem with a message on Siteremote :


Otv-tab-33_Bière - Débordement du Registre de Messages
vendredi 22 juin 2018 10:26:05. (5 heures 4 minutespersistant(s))
Le serveur de SiteRemote a reçu un nombre très élevé d´ Entrées Registres dans peu de temps. Ceci a résulté dans l´activation de la limite de sortie interne. Pour conserver les ressources du serveur, plus d´Entrées Registres seront reçues et enregistrées, jusqu´à ce que le volume d´Entrées Registres soit diminué considérablemet.

Can you tell us if it is critical or not and what we can do to resolve the problem ?

KR
Denis
Re: Screen with forbidden access in white 6/22/2018 3:46 PM
The warning “Message Log overflow” just means that there where a irregular high number of SiteKiosk log file entries in a certain time (more than 10000 in 24h).
In that case SiteRemote stops the log transfer of the machine to SiteRemote for a while and throws that alert.

It is meant as help to check a machine which maybe has problems (which problems have occurred need to be analyzed by checking the error messages in the local log files or later at SiteRemote when more log messages have been transferred).


Note:
After solving the issue SiteRemote automatically receives the outstanding log information.
But it can take some hours or even 1-2 days (depends on how long the issue has occurred) until the log files on SiteRemote are up-to-date.
This depends on how much outstanding log information still must be transferred from the client to SiteRemote.
My Account
Login
Language (Tickets):