Solution: The ConfigMgr 2007 SMS Agent Host Service (CCMExec.exe) may become unresponsive when Thread Pool ETW tracing is enabled

Solution: The ConfigMgr 2007 SMS Agent Host Service (CCMExec.exe) may become unresponsive when Thread Pool ETW tracing is enabled

  • Comments 4
  • Likes

imageHere’s an issue we’ve seen a couple times before so I thought I’d give you a heads up here in case you happen to run across it.

Symptoms

The System Center Configuration Manager 2007 (ConfigMgr) SMS Agent Host Service (CCMExec.exe) may become unresponsive or even crash on a regular basis, sometimes as frequently as every hour. You may also see the errors below:

Application Event Log:

Event ID: 1000
Faulting application name: CcmExec.exe, version: 4.0.6487.2000, time stamp: 0x4ab33e4d
Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58
Exception code: 0xc0000005
Fault offset: 0x0009ce04
Faulting process id: 0xc58
Faulting application start time: 0x01cc50371f1d9317
Faulting application path: D:\SMS_CCM\CcmExec.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 93ccc0f5-e058-11e0-9746-984be1753436'

System Event Log:

Event ID: 7031

Description: The SMS Agent Host service terminated unexpectedly. It has done this 38 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service.

Application Event Log:

Event ID: 1035
Windows Installer reconfigured the product. Product Name: SMS Management Point. Product Version: 4.00.6487.2000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
Event ID: 1035
Windows Installer reconfigured the product. Product Name: Configuration Manager Client. Product Version: 4.00.6487.2000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
Cause

This can potentially occur in some scenarios where CAL tracking is enabled (the default) and Thread Pool Logging is enabled.

Resolution

There are two possible ways to resolve this issue:

1. Disable Thread Pool ETW tracing. To do this you’ll need to use logman.exe to stop the Data Collector Set that contains the Thread Pool provider.

a. To list all of the running Data Collector Sets use this command:

logman.exe -ets

b. One of the sets should have the words Thread Pool in the name. If not, you’ll have to query each set individually using the command below until you find the one that has the Thread Pool provider. It will be the one that has a GUID of {C861D0E2-A2C1-4D36-9F9C-970BAB943A12}.

logman query COLLECTOR_SET_NAME -ets

c. Use the following two commands to disable Thread Pool ETW tracing, substituting the Data Collector Set name you discovered above:

logman stop COLLECTOR_SET_NAME -ets
logman delete COLLECTOR_SET_NAME -ets

2. Alternatively, you can disable CAL tracking in ConfigMgr by renaming the DLL that handles that component.

On a 64-bit system this will be at C:\windows\syswow64\ccm\ccm_caltrack.dll. If the server is a Management Point, it will be at \SMS_CCM\CCM_Caltrack.dll

Stop the SMS Agent Host service, rename the DLL, and then restart the service. You will see a warning/error line in one of the client logs when the service starts but there should not be any additional errors and the client should not be affected in any other way.

You should only have to do one of the two options above.

Senthilkumar Pandurangan | System Center Support Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • I hate when MS solutions to crashes involve disabling features they tout about in the product.  Your solution to this issue is morbidly stupid and doesn't fix any actual cause.  If CAL tracking, a useful feature to some install bases of your product has an issue, fix it!!  Don't disable it you twit.

  • I agree with you! This bug must be fixed!

  • Hello Folks,

    This bug has now been resolved by following SCCM Advanced Client 2007 Hotfix:

    support.microsoft.com/.../2724939

    Enjoy!

    Best Regards

    Anders Horgen

  • I tried to install the hotfix, but it's saying I have wrong language version installed. Installed is english, downloaded english. Googled it and some have had similar trouble with AV (Trend Micro). I have FEP. Renaming that caltrack file then.