Hi,
Please can someone help with the error message below?
I’ve tried to fix it from a couple of other threads with a similar problem but can’t.
Thanks!
Hi,
Please can someone help with the error message below?
I’ve tried to fix it from a couple of other threads with a similar problem but can’t.
Thanks!
So the display ‘London’ didn’t connect to the CMS since 25.02, probably that’s why it’s out of date, when it re-connects it should download new content.
Display Bournemouth Second floor, seems to be currently logged in, depending on collection interval it should soon start to download new content from the CMS.
the (!) is not necessary a problem, as long as it doesn’t persists for too long.
If there are any problems with your displays, please show us a screenshot of status window on them.
Hi Peter,
The Bournemouth display has been displaying this error for weeks. Understand the London issue.
How do I screenshot the status window?
Thanks
David
if it’s Windows client, then please press 'i" on your keyboard while Xibo is running.
If it’s Android client, then on the action bar there is a button called ‘status’
Thanks Peter, i’ll grab a screenshot now.
Hi Peter,
My screenshot was a bit fussy but there were no specific errors apart from the Download status is sleeping?
Thanks
David
Could you perhaps use printscreen(Prt Sc) button to make it look a bit clearer?
It seems like, there is nothing in required files?
Could you please restart it, also make sure that CMS address and Key are correct (just in case)
Could you also please tell me what CMS and client versions are you using?
Peter,
FYI, we also have this problem. It is only resolved after rebooting the client. CMS 1.7.6, Android Client 1.7 R56-59 all have the same problem. It occurs randomly after changing a layout. If we have 5 screens in a display group, each getting the same update, 1 or 2 will do this almost everytime. The units that do it are random, and all are alike. Hardware, software, etc, all the same. Unfortunately, I do not have a screen shot of one of the devices when it does it. Also the Last Access time and date show that the units are still checking in at the correct intervals.