Guys,

This is a mystery.  I have users in 1 office all having the same issue.  CCMEXEC  is running at 100% memory utilization on all the machines.  Once I kill the process everything returns to normal.  CCMEXEC.log has little to no information about what is causing the issue.  All I see in the log some 20 minutes after the issue starts are a bunch of "failed to load logging configuration for ccmmessaging and ccmexec"

Any thoughts ?

• Edited by steven powell1 Friday, June 19, 2015 2:43 PM edit

Is there anything in the windows event logs ?

Can you attached the CCMEXEC.log so we can see what is says

thanks Andrew.  Nothing in the windows log.  Couldnt see how to upload a file, so its here

http://expirebox.com/download/d1eac19450f5ea3a7f5206b2ba0320d0.html

10:12 is when I rebooted and saw the issue right after reboot. 

• Edited by steven powell1 Friday, June 19, 2015 5:53 PM

Here is what doesnt make sense.  The processes tab and performance tab both show the memory utilization and two different numbers 

Are those screenshots from the same point in time? ccmexec.exe is only using approx. 38MB of memory.

Also, try reviewing memory usage in Resource Monitor.

Jeff

• Edited by Jeff Poling Friday, June 19, 2015 8:59 PM

Hi,

Any task run when the issue occur? Like Windows update?

Windows Update Client for Windows 7: June 2015

I know it sounds crazy but those screen shots are within seconds of each other.  If I kill SMS agent host memory returns to a normal level.  THis lasts for 2 or 3 hours.  If I reboot the computer the problem starts back over again.

I am going to open a ticket with MS

 

Hello,

Did you get any solution or workaround from CSS support? This will also help the others in this forum

What happens if you clear the security eventlogs on one of the clients, does it improve?

Are you doing regular WSUS cleanups to purge expired and obsolete update metadata on a regular basis?  I would guess this is most likely the cause if not, especially if it climbs up during a software update scan...  Try running your WSUS cleanup steps and re-index SUSDB if you haven't done that as well and see if it subsides.