For future researchers: I ran into this problem yesterday, with these errors in smsts.log:
reply has no message header marker TSPxe 7/13/2016 11:34:08 AM 1644 (0x066C) DoRequest (sReply, false), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,7299) TSPxe 7/13/2016 11:34:08 AM 1644 (0x066C) SendReport (L"mp:[http]MP_DdrEndpoint", L"MP_DdrEndpoint", L"{00000000-0000-0000-0000-000000000003}", 0, true, sReportBody.c_str()), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,7704) TSPxe 7/13/2016 11:34:08 AM 1644 (0x066C) oClientDDR.SendDDR(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,568) TSPxe 7/13/2016 11:34:08 AM 1644 (0x066C) Failed to send DDR (0x80004005) TSPxe 7/13/2016 11:34:08 AM 1644 (0x066C) SendDDR (&m_oHttpTransport, m_sSiteCode.c_str(), sMediaGuid.c_str(), m_sClientIdentity), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,952) TSPxe 7/13/2016 11:34:08 AM 1644 (0x066C) failed to send the DDR (0x80004005) TSPxe 7/13/2016 11:34:08 AM 1644 (0x066C)
In our case, it had nothing to do with the time or certs. The database was out of disk space! Expanded the disk and all is well this morning. Too bad the error isn't a little more helpful about the problem...