Every few weeks our newest Xibo fails to update sign content

Any help would be appreciated. We have a bunch of Xibo units that work fine and have been extremely reliable for years. Recently we ordered a new DSCS9 and ever since we have been having problems with it. Initially everything works, but after a few weeks it says “Unknown Display Status” and fails to receive new content. The first time this happened a power cycle fixed it, when it happend again I downgraded the Android client from 1.7_R64 to version 1.7_R63 but again after a few weeks time we encountered the same problem. Our server is running version 1.7.3

Here’s some logs:

895284 2020-02-10 21:02:19 Client DisplayManager Cannot set the next Layout from the Schedule. Schedule Invalid
895283 2020-02-10 21:02:19 Client DisplayManager Cannot set the next Layout from the Schedule. Schedule Invalid
884883 2020-02-03 22:04:38 Client ScheduleManager The Schedule has not been downloaded yet.
884882 2020-02-03 22:03:08 Client Register CMS has sent an error: The Server key you entered does not match with the server key at this address
884881 2020-02-03 22:03:07 Client ScheduleManager The Schedule has not been downloaded yet.
884880 2020-02-03 22:01:04 Client Register CMS has sent an error: The Server key you entered does not match with the server key at this address
884879 2020-02-03 22:00:43 Client Register CMS has sent an error: The Server key you entered does not match with the server key at this address
884878 2020-02-03 21:59:03 Client Register CMS has sent an error: The Server key you entered does not match with the server key at this address
884877 2020-02-03 21:58:44 Client Register CMS has sent an error: The Server key you entered does not match with the server key at this address
884792 2020-02-03 20:12:07 Client Register Error in Register: timeout
884791 2020-02-03 20:11:23 Client Register Error in Register: timeout
884763 2020-02-03 20:02:07 Client Register Error in Register: timeout
884614 2020-02-03 17:40:56 Client Register Error in Register: timeout
884613 2020-02-03 17:40:25 Client LayoutStatusUpdateDispatch - Run timeout

1.7 is out of support now so any issues you have there beyond configuration won’t be fixed anymore. You should ideally be looking to upgrade to version 2 where support and bug fixes are available.

The logs you’ve pulled out suggest that the Player has the wrong CMS key. You’d need to ensure that it’s entered correctly in the CMS connection wizard.

The other logs you have suggest the Player can’t connect to the CMS at all (with a timeout) so it would be worth checking the device’s network connection.

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.