Next time it happens it would be best to open a case - to verify cause.... as TLange stated ... it could be Agent Issue.
Logging for ePO, Agent/ & MSME Product would need to be check to verify where the failure is happening.
that error indicates a setting coming down from the msme policy in epo is bad. this is then preventing the local plugin from applying the policy to msme. if you enable msme debug logging (set level to high) and then try a policy enforcement it should record the problem in one of the rpcserv logs.
After upgrade to 8.51 also got CManage::EnforcePolicies() - Failed - "MSME____8500" (error = -1000). In my case helped set at organization level/root polices to mcafee default , Then i forced on clients force check new polices. Then I created new polices based on mcafee default and assigned to exchange folder in tree
I had a similar issue. After some discussion with support, it turns out that upgrading the extensions in ePO can break things. They recommend removing the extensions completely and then adding them back in. This is the process I followed:
- Stop agent services on the exchange server
- Prevent any agent updates from ePO to MSME, essentially putting it in standalone mode.
- Backup up policies, assignments and reports for MSME in ePO
- Remove all MSME extensions from ePO
- Install MSME extensions in ePO and restart services on the exchange server. This should apply all default policies to MSME. This can be checked easily be changing the number of DAT files to retain and then enforcing a policy and task refresh.
- Once confirmed as working, update policies in ePO as required and push out to MSME. It is recomended to do one at a time and check enforcement as you go.
Mine is working perfectly now (apart from sending alerts emails but that is a seperate issue)