The error you mention is because someone deleted part of the MySQL database from the filesystem. It’s the table that records proof of play statistics.
The Players will be sending those up to the CMS indefinitely trying to flush those out, and the CMS will error each time, which is why the bandwidth isn’t recorded.
You need to run the following SQL on your database:
DROP TABLE `stat`;
CREATE TABLE `stat` (
`statId` int(11) NOT NULL AUTO_INCREMENT,
`type` varchar(20) NOT NULL,
`statDate` int(11) NOT NULL,
`scheduleId` int(11) NOT NULL,
`displayId` int(11) NOT NULL,
`campaignId` int(11) DEFAULT NULL,
`layoutId` int(11) DEFAULT NULL,
`mediaId` int(11) DEFAULT NULL,
`widgetId` int(11) DEFAULT NULL,
`start` int(11) NOT NULL,
`end` int(11) NOT NULL,
`tag` varchar(254) DEFAULT NULL,
`duration` int(11) NOT NULL,
`count` int(11) NOT NULL,
`engagements` text,
PRIMARY KEY (`statId`),
KEY `statDate` (`statDate`),
KEY `displayId` (`displayId`,`end`,`type`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
The above is specific to version 2.3.10. You shouldn’t use it for any other version. If you’re unsure how to run that, please see How can I run a SQL command when using a Docker Install?
That will fix the error. If you don’t want proof of play statistics, then turn them off in the Display settings profile. The Players will need to flush out what they have recorded before they will stop sending in records, so if this has been going on for some time, that table will continue to grow for a while.
You can run the following to empty it periodically:
TRUNCATE `stat`;
OPTIMIZE TABLE `stat`;
It’s not OK to just delete files from shared/db. They form part of a database, they aren’t raw log files.
Other reasons Windows may show different bandwidth to the CMS is if you’re embedding webpages, streaming video etc that doesn’t pass through the CMS.