Installing Hotfix 977384 or 2513499 with ConfigMgr 2007 logs error on execmgr and incorrectly reports as failed

Installing Hotfix 977384 or 2513499 with ConfigMgr 2007 logs error on execmgr and incorrectly reports as failed

  • Comments 2
  • Likes

imageHi everyone, Joao Madureira here.  I’m a Senior Support Escalation Engineer here at Microsoft and I wanted to take a minute to tell you about an issue we’ve been getting a couple calls on just in case you happen run into it as well.  It’s not really a problem, it just appears to be one on the surface so it might cause you some unneeded concern if you see it.

The issue is that when running an advertisement in System Center Configuration Manager 2007 to install hotfixes 977384 or 2513499, it can generate errors in Execmgr and the advertisement shows as failed even though it was actually successfully installed.

This happens because when we install those hotfixes they restart the CCMexec.exe process, thus Execmgr cannot monitor the MSI to see if installed successfully.  Here are examples of the kinds of errors you may see:

CcmExec.log

WM_QUIT received in the main message loop. CcmExec 7/12/2011 2:31:43 PM 2304 (0x0900)
Shutting down CCMEXEC... CcmExec 7/12/2011 2:31:43 PM 2304 (0x0900)
BEGIN ExecuteSystemTasks('PreShutdown') CcmExec 7/12/2011 2:31:43 PM 880 (0x0370)
Invoking system task 'StatusAgentShutdown'. CcmExec 7/12/2011 2:31:43 PM 696 (0x02B8)
END ExecuteSystemTasks('PreShutdown') CcmExec 7/12/2011 2:31:44 PM 880 (0x0370)
BEGIN ExecuteSystemTasks('Shutdown') CcmExec 7/12/2011 2:31:44 PM 880 (0x0370)
Invoking system task 'SchedulerShutdown'. CcmExec 7/12/2011 2:31:44 PM 696 (0x02B8)
Invoking system task 'MtrMgrShutdown'. CcmExec 7/12/2011 2:31:44 PM 696 (0x02B8)

Execmgr.log

Command line = "C:\Windows\System32\msiexec.exe" /i "C:\Program Files (x86)\SMS_CCM\Cache\CHD0000B.1.System\SCCM2007-SP2-KB2513499-ENU.msi" /quiet, Working Directory = C:\Program Files (x86)\SMS_CCM\Cache\CHD0000B.1.System\ execmgr 7/12/2011 2:31:28 PM 2176 (0x0880)
AdvertisementId = "CHD20003";
ClientID = "GUID:A926CDB6-AB08-4621-A7D8-1F190A17D8FB";
CommandLine = "\"C:\\Windows\\System32\\msiexec.exe\" /i \"C:\\Program Files (x86)\\SMS_CCM\\Cache\\CHD0000B.1.System\\SCCM2007-SP2-KB2513499-ENU.msi\" /quiet";
DateTime = "20110712193128.152000+000";
MachineName = "SCCM-CHD";
PackageName = "CHD0000B";
ProcessID = 2792;
ProgramName = "test";
SiteCode = "CHD";
ThreadID = 2176;
UserContext = "NT AUTHORITY\\SYSTEM";
WorkingDirectory = "C:\\Program Files (x86)\\SMS_CCM\\Cache\\CHD0000B.1.System\\";
};
execmgr 7/12/2011 2:31:28 PM 2176 (0x0880)
Raised Program Started Event for Ad:CHD20003, Package:CHD0000B, Program: test execmgr 7/12/2011 2:31:28 PM 2176 (0x0880)
Request in running or report status found for program test package CHD0000B execmgr 7/12/2011 2:32:42 PM 3980 (0x0F8C)
Service stopped while program test is running execmgr 7/12/2011 2:32:42 PM 3980 (0x0F8C)
OpenProcess failed for process 2508, error 80070057 execmgr 7/12/2011 2:32:42 PM 3980 (0x0F8C)
Can not continue monitoring the program after service restart because the process exited. Assume failed execmgr 7/12/2011 2:32:42 PM 3980 (0x0F8C)
Looking for MIF file to get program status execmgr 7/12/2011 2:32:42 PM 3980 (0x0F8C)

You can ignore these errors as this is expected behavior.  Because CCMexec stops monitoring the installation when it is restarted, it assumes the installation failed even though it actually completed successfully.

Joao Madureira | Senior Support Escalation Engineer

App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
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/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
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/

clip_image001 clip_image002

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • To work around these errors, one could call a script which fires off the updates asynchronously. For example, in PowerShell, you could use the Start-Job cmdlet to create an async job.

    Cheers,

    Trevor Sullivan

    http://trevorsullivan.net

  • One of our package engineers just found another way to install this ConfigMgr Client Hotfixes without an error: If you specify the correct MIF Name on the Reporting Tab on the Package and configure the "After running" behavior to "Program restarts computer" (the computer will not be restarted, just the ccmexec Service restarts) then the Advertisement Status will be "successful". The correct MIF Name could be found on the Hotfix.MSP File on Properties -> Details -> Revision number. The first GUID is the correct MIF name. If you create the Hotfix Package with the Hotfix Installation on the Site Server, the MIF Name and the after running Option on the Program will setup correctly.

    Regards, Jürg