That's a normal error and is not likely causing any problems. I'm not sure exactly what it indicates but I beleive that this error occurs when a device renews it's compliance.
I don't think it has something to do with a compliance renewal. I assume that the connection between Exchange ActiveSync and EMM is encoded with a self signed certificate, but this certificate can't be renewed on certain devices.
These errors are scattered throughout my logs since day one. I have sent my logs to mcaffee support and they pointed out what each of the errors I was seeing meant. Here is thier reply:
There are a ton of these errors and they are for the same device. They just mean the device failed to complete MDM check in and it continues to try for sometime, unsuccessfully. Reason why the device could not check in will vary and it may have been some issue that eventually went away, but you could look for it in the helpdesk based on app id and see if it’s working now or not.
Unsuccessful CheckIn for device ApplDQWFW0SFDFHW
There were also a few of the errors below in February and randomly throughout. These mean that a device is checking in and its policy has since changed, so the device will be non-compliant unless it gets the new policy. It should then download the new policy and these errors go away. This may have been triggered by a policy publish and then they usually go away when everyone has the updated policy.
CertificateCompliance Failed GenerationDate Match; 2/11/2012 4:05:44 PM - 2/14/2012 9:48:27 PM