Some task sequences may not run on the client computers in System Center Configuration Manager 2007 Service Pack 1-based systems
This article has been archived. It is offered "as is" and will no longer be updated.
Not all advertised task sequences are processed in Microsoft System Center Configuration Manager 2007 Service Pack 1 (SP1)-based systems.
This problem occurs because of a synchronization issue in execution manager. Some tasks are deleted before they are handled in the pending task sequence queue.
Service Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft System Center Configuration Manager 2007, available from this Microsoft web site: http://www.microsoft.com/downloads/details.aspx?FamilyID=3318741a-c038-4ab1-852a-e9c13f8a8140
For a list of issues resolved in this service pack, click on the following article number in the Microsoft Knowledgebase:
971348 List of hotfixes and updates that are contained in System Center Configuration Manager 2007 Service Pack 2
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must have System Center Configuration Manager 2007 Service Pack 1 (SP1) installed on the computer.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
System Center Configuration Manager 2007 SP1
|File name||File version||File size||Date||Time||Platform|
|Mp.msi||Not Applicable||9,233,408||30-Nov-2008||22:10||Not Applicable|
|Sccm2007ac-sp1-kb967359-x86.msp||Not Applicable||2,313,216||30-Nov-2008||22:10||Not Applicable|
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
If the following error message is logged in the PolicyAgentProvider.log file on the System Center Configuration Manager 2007 client, the asynchronous delivery queue has overflowed:
Event sink has been notified of an error (<80041061>). Description 0x80041061:This behavior occurs when the event consumer becomes too slow.
WBEM_E_QUEUE_OVERFLOW 2147749985 0x80041061
WBEM_E_QUEUE_OVERFLOW 2147749985 0x80041061
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in WindowsTo resolve this issue, change the following WMI registry values:
- Change the value of following registry key to 35000000: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM\Low Threshold On Events (B)
Note The default value is 10000000.
- Change the value of the following registry key to 55000000: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM\High Threshold On Events (B)
Note The default value is 20000000.
824684 Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 967359 - Last Review: 01/16/2015 03:43:52 - Revision: 3.0
Microsoft System Center Configuration Manager 2007
- kbnosurvey kbarchive kbautohotfix kbexpertiseinter kbsurveynew kbbug kbfix kbqfe KB967359