Hardware Inventory in Configuration Manager 2007 fails and the SMSexec.exe process shows high sustained CPU utilization

Applies to: Microsoft System Center Configuration Manager 2007 R3


When using system Center Configuration Manager 2007, processing of Hardware Inventory .MIF files fails and the SMSexec.exe process will show high sustained CPU utilization. Also, MIF files will backlog in the following folder:


The NextGroupKey value in the ArchitectureMap table will be unusually high (> 20,000).

Note: The following query can be used to examine the value of the NextGroupKey:

select NextGroupKey from ArchitectureMap where ArchitectureKey = 5  

If SQLTracing is enabled on the site server, you will see the following messages repeated:

SQL>>> select NextGroupKey from ArchitectureMap where ArchitectureKey = 5  
SQL>>>>> Done.
SQL>>> update ArchitectureMap set NextGroupKey = NextGroupKey + 1  where ArchitectureKey = 5 and NextGroupKey = 15080
SQL>>>>> Done. 

You can enable SQL tracing by setting the following value: 

On 64-bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS\Tracing\SQLEnabled = 1

On 32-bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing\SQLEnabled = 1

For more information on SQL Tracing see the following Knowledge Base article:

KB176517 - SMS: Troubleshooting inventory MIF backlog problems (http://support.microsoft.com/kb/176517).


This can occur if the global 'No count' option is enabled on the SQL server hosting the SMS database. If this is enabled, Configuration Manager 2007 cannot get the correct rowcount value from SQL and thus it cannot complete the cycle to extend the schema.


Disable 'No count' and processing will continue normally. The "No count" option can be found in the SQL Management Studio:  Properties of the SQL Server -> Connections -> 'no count'.  It should be unchecked.

More Information

The "No count" option is not enabled by default. Microsoft has not tested Configuration Manager 2007 with the SQL "no count" global option enabled and using this option is not supported. Regardless, you should determine whether other applications that are using the same SQL server require the "No count" setting to be enabled before disabling it.