Configuration Manager 2007: CCMExec.exe may occupy high memory usage on client machines

Problem & Symptom

The CCMEXEC.exe occupies high memory usage on the problematic machines, which can reach 200 MB or more.

This problem may happen after you assign a configuration baseline rule that includes more than many software updates in Microsoft System Center Configuration Manager 2007.

Cause

Each time you restart the CCMEXEC.exe service, you may see the following information from the SDMAgent.log, which contain many pending Package Loader Jobs.

SDM Agent starting up... SdmAgent 1/5/2011 4:26:57 PM 2472 (0x09A8)

CTypeStore::RemoveStalePackages - 0 stale package(s) removed. SdmAgent 1/5/2011 4:26:57 PM 2472 (0x09A8)

CTypeStore::Initialize succeeded. SdmAgent 1/5/2011 4:26:57 PM 2472 (0x09A8)

CPackageLoader::InitializeJobState deserilalized X jobs. SdmAgent 1/5/2011 4:27:14 PM 2472 (0x09A8)

CPackageLoader::DeleteAgedOutJobs deleted 0 old jobs. SdmAgent 1/5/2011 4:27:14 PM 2472 (0x09A8)

 

Per using the following WQL query through the WMI namespace (root\ccm\xmlstore), you may find there are many obsolete package loader jobs exists

 

select * from xmldocument where storeid='Sdm Package Loader State Store'

Within the package loader job content, you can see it relates to the DCM baseline.

While in the SDMAgent.log, we can see the following error reported repeatly.

CPackageLoader::ParseDtsMessage error (0x80004005). SdmAgent 12/21/2010 7:25:08 PM 4736 (0x1280)

Error during SdmPackageLoader::HandleMessage (0x80004005). SdmAgent 12/21/2010 7:25:08 PM 4736 (0x1280)

CPackageLoader::ParseDtsMessage error (0x80004005). SdmAgent 12/21/2010 7:29:25 PM 4648 (0x1228)

Error during SdmPackageLoader::HandleMessage (0x80004005). SdmAgent 12/21/2010 7:29:25 PM 4648 (0x1228)

CPackageLoader::ParseDtsMessage error (0x80004005). SdmAgent 12/21/2010 7:33:53 PM 3648 (0x0E40)

Error during SdmPackageLoader::HandleMessage (0x80004005). SdmAgent 12/21/2010 7:33:53 PM 3648 (0x0E40)

 

 

The cause can be found in the KB 937532.

  https://support.microsoft.com/kb/937532

When you create a configuration baseline rule that includes more than 300 software updates in System Center Configuration Manager 2007, the configuration baseline is not evaluated correctly

Resolution

 

1. Remove the problematic DCM baseline.

2. Remove the existing obsolete package loader jobs(all existing instances) in WMI namespace root\ccm\xmlstore returned from the following WQL query.

select * from xmldocument where storeid='Sdm Package Loader State Store'