New clients not updating

Running CMS 1.6.3
All Clients are Android 4.2 based and running at least v37 of the Android Client

I have roughly 13 displays. I setup the first 10 displays without a problem. Since then every display I try to add since will not download it’s scheduled content to the client. I tried to look through the log files but I don’t see anything that is standing out to me.

I opened a ticket with Spring Signage and was told that I must be exceeding the number of licenses I have purchased. However that is not the case, and even purchased additional licenses just to make sure. Still I cannot get the clients to download their content.

Here is part of the log file:

LogId
Date
Page
Function
Message
390 2015-03-14 11:49:21 DOMDocument::loadXML(): Premature end of data in tag log line 1 in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
389 2015-03-14 11:49:21 DOMDocument::loadXML(): Opening and ending tag mismatch: trace line 1 and log in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
388 2015-03-14 11:49:21 DOMDocument::loadXML(): Opening and ending tag mismatch: message line 1 and trace in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
387 2015-03-14 11:49:21 DOMDocument::loadXML(): Opening and ending tag mismatch: media line 1 and message in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
386 2015-03-14 11:49:21 DOMDocument::loadXML(): Opening and ending tag mismatch: trace line 1 and message in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
385 2015-03-14 11:49:21 DOMDocument::loadXML(): Opening and ending tag mismatch: message line 1 and mefia in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
384 2015-03-14 11:49:21 DOMDocument::loadXML(): Opening and ending tag mismatch: message line 1 and trace in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
383 2015-03-14 11:49:21 DOMDocument::loadXML(): Opening and ending tag mismatch: media line 1 and message in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
382 2015-03-14 11:48:56 DOMDocument::loadXML(): Premature end of data in tag log line 1 in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
381 2015-03-14 11:48:56 DOMDocument::loadXML(): Opening and ending tag mismatch: trace line 1 and log in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
380 2015-03-14 11:48:56 DOMDocument::loadXML(): Opening and ending tag mismatch: message line 1 and trace in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
379 2015-03-14 11:48:56 DOMDocument::loadXML(): Opening and ending tag mismatch: media line 1 and message in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
378 2015-03-14 11:48:56 DOMDocument::loadXML(): Opening and ending tag mismatch: trace line 1 and message in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
377 2015-03-14 11:48:56 DOMDocument::loadXML(): Opening and ending tag mismatch: message line 1 and mefia in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
376 2015-03-14 11:48:56 DOMDocument::loadXML(): Opening and ending tag mismatch: message line 1 and trace in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727
375 2015-03-14 11:48:56 DOMDocument::loadXML(): Opening and ending tag mismatch: media line 1 and message in Entity, line: 1
2
Warning
C:\www_walidigital\xibo\lib\service\xmdssoap.class.php
727

Update

I purchased some 1.7 (version 52) licenses to see what would happen.

I installed the 1.7 (version 52) client onto a new Android device. Set it up in the CMS and it does not work.

I unlicensed a current client, upgraded it to version 1.7 (version 52) and it works.

So still I am unable to get any new Android clients to work.

I’ve replied directly to your Service Desk ticket. I think it’s very likely an issue with the date and time on your new device, but if it isn’t that we’ll need some screenshot or photos of the client status screen so we can see what the client thinks is happening.

Just me not fully understanding schedules… I went there and deleted everything off of the calendar. Then rescheduled with only one campaign and it works just perfect now. That part about the calendar schedule just was not clear for me. I have it up and running just fine right now.

rosecitymed,

Is this posted to the wrong post??? If not I am not understanding what you problem is/was.

Ahmm…resecitymed I am pretty sure you didn’t want to post it here, but since it seems that it’s fine now, that’s good.
For the future reference, if you have questions, please create new topic and do not post in the few months old ones.

I’ll close this topic now :smiley: