Ticket ID: 26975 Erstellungsdatum: 18.06.2026 01:30 Produkt: SiteKiosk Online Client Anhang: -
Tickettyp: Support Anfrage Version: 1.8.186 Sprache: Englisch
Aufrufe: 3214 Letzte Änderung: 20.07.2026 22:46 Plattform:
Level: Geschlossen

Support Anfrage: Cannot re-launch site kiosk

Beschreibung

I am not able to relaunch the SiteKiosk software because it states that it is already running. I have restarted my device and the current project will not load. I have attached the log files from SPT-KIOSK04

Antwort: (3)
Re: Cannot re-launch site kiosk 18.06.2026 18:51
Hello,

Thank you for your inquiry. We are aware of this behavior, and a fix will be included in the next release, soon. See email with detailed steps on how rectify the issue. You can review Dashboard>>News for new updates.

You can schedule updates for your clients in Portal>>Control>>Updates. Allow 15 minutes for the update process. You can send Restart SiteKiosk or Machines jobs to devices that have not started updating to jump start the process.

Best regards,
Andre.
Re: Cannot re-launch site kiosk 22.06.2026 21:57
Hi Andre-your fix worked for me. I am getting the following alert though.

The SiteKiosk Online (USA) server received an unusual number of log entries within a short period of time. This resulted in the activation of the internal throughput limit. To conserve server resources, no more log messages will be received and recorded until the generated log volume is reduced significantly.

Do I need to do anything?

-Stephanie
Re: Cannot re-launch site kiosk 22.06.2026 22:44
Hi Stephanie,

This happens when there are a lot of system events on the device. Mostly those who are part of corporate domains will see many messages in Windows Event Viewer logs. You can investigate what restrictions are causing that many messages to overflow the log ingestion service or you can review what logs can be ignored in Portal>>Team>>Settings>>Log Message Settings, then Selection of Components. Remember to hit the Save button.

You can delete the overloaded messages by going to Portal>>Monitoring>>Device>>Overview. Before this step, it is best to address the underlying issue first.

Best regards,
Andre.
Kommentar hinzufügen
Mein Konto
Anmelden
Sprache (Tickets):