Unable to display scheduled campaign or layout to Xibo Windows Player

I installed Version 1.7.2 on CentOS and setup two Xibo players on a Windows 8.1 computers. It was working fine on the initial testing.

Then I modified the layout and added to a campaign. The scheduled campaign or layout never be able to display the updated layouts (in which I added added tickers, video, and images). I can preview the updated layout but just could not display it on the two Xibo players. Only the splash screen plays.

I have verified that there is at least one content in each region defined in the layout. Any idea how to resolve this so that the updated layout content can be shown on the xibo players.

Thanks

What does the client information screen say?

It shows the standard xibo splash screen.

Sorry no the Client Information Screen (ie press i on the client’s keyboard to bring that screen up)

I learned something new. I did not know the “i” know will bring up the information screen.

I can see the error message now and looks like there are some missing files. Not sure why. Below is the log information that I extracted from the information screen. Thanks… Hillman

LibraryAgent|3/18/2015 7:00:50 PM|Error|LibraryAgent - Run|Exception in Run: Could not find file ‘D:\temp\xiboClientLib\requiredFiles.xml’.
ScheduleManagerThread|3/18/2015 7:00:50 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:00:50 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:00:50 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:01:00 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:01:00 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:01:00 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:01:10 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:01:10 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:01:10 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:01:20 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:01:20 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:01:20 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:01:30 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:01:30 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:01:30 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:01:40 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:01:40 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:01:40 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:01:50 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:01:50 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:01:50 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:02:00 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:02:00 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:02:00 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:02:10 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:02:10 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:02:10 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:02:20 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:02:20 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:02:20 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:02:30 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:02:31 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:02:31 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:02:40 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:02:41 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:02:41 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:02:50 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:02:51 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:02:51 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:03:00 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:03:01 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:03:01 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:03:10 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:03:11 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:03:11 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:03:20 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:03:21 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:03:21 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:03:30 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:03:31 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:03:31 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:03:40 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:03:41 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:03:41 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:03:50 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:03:51 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:03:51 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:04:00 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:04:01 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:04:01 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:04:10 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:04:11 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:04:11 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:04:20 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:04:22 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:04:22 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:04:30 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:04:32 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:04:32 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:04:40 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:04:42 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:04:42 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:04:50 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:04:52 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:04:52 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:05:00 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:05:02 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:05:02 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:05:10 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:05:12 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:05:12 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:05:20 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:05:22 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:05:22 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:05:30 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:05:32 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:05:32 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:05:40 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:05:42 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:05:42 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout
ScheduleManagerThread|3/18/2015 7:05:50 PM|Error|ScheduleManager - LoadNewSchedule|Layout invalid: 8
UI Thread|3/18/2015 7:05:52 PM|Error|MainForm - ChangeToNextLayout|Prepare Layout Failed. Exception raised was: Default layout
UI Thread|3/18/2015 7:05:52 PM|Error|MainForm - ChangeToNextLayout|Layout Change to failed. Exception raised was: Default layout

Xibo has checked your layout and it is invalid - it could be missing some files as you suggested, or it could be invalid in some other way (empty region, no regions, etc).

In the CMS what is the status indicator next to that layout saying?

Currently the display has default layout set to a layout named “displayDefaultImage”.

On the layouts page, this layout has a tick mark under the status column. What else I can check to find out the missing file or the invalid region issue?

Hmm, if it has a tick then it should be good to run. On the client information screen, right hand pane, do you have any files that are not at 100%?

I installed 1.7.2 today, I got the same issue.

I am still investigating it.

If I use the default display profile, and change it directly in roaming folder, it’s OK.
I created a display profile, associated it with the display, then nothing downloaded(except empty backgound folder, schedule.xml and status.json) and nothing displayed, I checked the xml file, found the downloadstartwindow 142663680000,downloadendwindow1426636800000, and hash 5b… while the values in the xml from the default profiles are zero.

Is it a possible clue?

Thanks
Jianjian

That could be a clue - what does the required files status say on the client information screen?

The default should be 0 - downloadStart and downloadEnd window are new settings that allow you to specify when the player downloads content.

The fact you get both set to 4:48am means that your players will only update for that 1 minute each day

Required files status: outside Download Window 00:00 - 00:00

Empty

Can you try setting a download window on the default profile?

I think it might be an issue with opening and saving a display profile and ending up with a download window that is exactly equal.

Hi Dan

I have 4 display profiles totally.
two defaults, android, windows.
I created two profiles, windows-cef-ci60, windows-ie-ci60

If I associate the display with windows, the layout displayed Ok
but if I associate the display with windows-cef-ci60, the problem happened.

So what download window value you want me to try on the default profile?

Thanks
Jianjian

I think that editing line 288 of lib/pages/displayprofile.class.php to:

$value = ($value == '00:00') ? "0" : DateManager::getTimestampFromTimeString($value) * 1000;

Might solve the issue for future edits.

On the left upper panel of the client information screen, it is empty. I can only see a line “LayoutId:0. Runs from 1/1/0001 12:00:00 AM”. On the top title, the schedule status indicated is sleeping.

On the right upper panel, the title bar indicated that the Required Files Status: Outside Download Window 16:00 - 16:00. There is no file download information.

I modified the line that you suggested - $value = ($value == ‘00:00’) ? “0” : DateManager::getTimestampFromTimeString($value) * 1000;

Then I restart the httpd. Still unable to display the default layout page to my xibo client.

Any other hint to resolve this issue as now nothing can be send to the xibo display client?

If this cannot be fixed and I want to refresh the xibo system like a brand new install, besides to reinstall the whole CMS again, is there any way to reset the CMS to default setup.

Thanks

@cornerstone - no need to refresh your CMS!

After editing the line mentioned you will need to open the Default Profile for Windows (or whichever profile you have assigned to your display) and click Save.

Alternatively you can set a download window - i.e. 00:00 to 23:59

Hi Dan

The modification works.

Thanks a lot.

Jianjian

dan you saved my life!

I was evaluating Xibo: I’ve set up a Linux box as server, two Windows players (one on W7, the other on W8.1), and couldn’t figure out why sometimes it worked, and sometimes not, why I could play videos on the W7 player but not on the W8.1 one, why even a simple web page wasn’t able to be displayed, etc.

Your “patch” works like a charm!

Thank you again,
Georges

Where can I set the download window. i.e. 00:00 to 23:59? I hope this will fix my issue as well.

In the display profile in the CMS. If you haven’t already you’d need to create a default profile for your Windows clients first