Client stops working and getting DCOM error in event viewer

Question

Hi
I am getting these errors after upgrading the client from 2007 to 2012.. the client works for a certain amount of time then stops functioning as expected. Logs not moving and get error when manually cycling policy etc from client.
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{F80A8D57-D338-43FF-A5E6-5D093EA80775}
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18).  This security permission can be modified using the Component Services
administrative tool.
I have checked the DCOM permissions for launch and activate for system account and they are set to allow...
its not happening on all clients which is strange

Answer 1

Hi Jason,
The service is running and the ccmexec.log does not stop but its rolled over since the issue occurred. About 30% of the logs continue logging and the rest stop with no action.I done a WMIDiag and I could see issues with missing namespaces and DCOM errors.
I am unistalling the client and reinstalling which fixes the issue for a short period of time, then I will do a WMIDiag once its working then monitor. Once it breaks I will do another WMIDiag and fetch the logs in to see if there are any indicators to why
this is happening.
Is there anything else you would do at this point?
From one client.. WMIDIAG
An example of missing instance and all were missing in this class!
root/ccm/Policy/machine, 'Select * From CCM_Service_HostedClass WHERE Description = "CPApplet Client Action" AND CLSID = "{F80A8D57-D338-43FF-A5E6-5D093EA80775}"' did not return any instance while AT LEAST 1 instance is expected.
From another client and on both
76815 12:03:57 (0) ** => This is an issue because there are still some WMI classes referencing this list of providers
76816 12:03:57 (0) **    while the DCOM registration is wrong or missing. This can be due to:
76817 12:03:57 (0) **    - a de-installation of the software.
76818 12:03:57 (0) **    - a deletion of some registry key data.
76819 12:03:57 (0) **    - a registry corruption.
76820 12:03:57 (0) ** => You can correct the DCOM configuration by:
76821 12:03:57 (0) **    - Executing the 'REGSVR32.EXE <Provider.DLL>' command.