[Forum FAQ] Three helpful ways for analyzing Inventory issues in System Center 2012 Configuration Manager

Question

To troubleshoot issues related to Inventory, we can view the related logs or force a full inventory to analyze the reason. In these article, we mainly introduce
the detailed ways to enable Verbose and Debug logging,
save the inventory report and force a full inventory on the client.
How to force a full inventory on the client
1. Open wbemtest and connect to “root\ccm\invagt”.
Figure 1.
2. Click “Enum Classes…”and then click “OK”.
Figure 2.
In the Query Result, you can view the cache for each entry. (Figure 3)
{00000000-0000-0000-0000-000000000001}
 Hardware Inventory
{00000000-0000-0000-0000-000000000002}
 Software Inventory
{00000000-0000-0000-0000-000000000003}
 Heartbeat
{00000000-0000-0000-0000-0000000000010} File Collection
Figure 3.
3. You can highlight the entry that contains the action you want to force a full to be sent and click “Delete” to delete it:
Figure 4.
4. Close all wbemtest dialog boxes and initiate the appropriate action in the Client Agent Action to perform a full inventory.
Figure 5.
How to enable
Verbose and Debug logging
It is also helpful to trace the flow if you enable Verbose and Debug logging on the client,
Management Point and Site Server.
To set verbose/debug logging on an SCCM client or
Management Point, you can simply edit (or create) the following registry keys:
HKLM/Software/Wow6432Node/Microsoft/CCM/Logging/@Global/LogLevel to 0
HKLM/Software/Wow6432Node/Microsoft/CCM/Logging/DebugLogging/Enabled to True
Figure 6.
Figure 7.
On the site server, you edit the following registry key to enable verbose logging and then restart the SMS_Executive (or the state system
component):
HKLM/Software/Wow6432Node/Microsoft/SMS/Components/SMS_STATE_SYSTEM/Verbose Logging – Reg_DWORD set to 1
Figure 8.
How to save the inventory report
To force the ConfigMgr client to save off a copy of the report that it sends to the Management Point, you can create an empty folder/directory under the inventory temp directory
called archive_reports.sms.
Then edit the following registry value to point to the inventory temp directory:
HKLM\Software\Microsoft\SMS\Mobile Client\Inventory\ Temp Directory
Figure 9.
Figure 10.
From the figure 9, you can see that the temp directory path is C:\Windows\CCM\Inventory\Temp. After we run the hardware inventory Cycle again, you can see the report file is
saved in the path we have defined automatically. (Figure 10)
(Note: Please delete the
archive_reports.sms folder when have finished the troubleshooting steps to save disk space.)
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Answer 1

Hi,
I have troubleshooted this error message several times and can say that this is a generic error message. The reason can be different in your Case. As suggested in the error message you should first check all the steps in the following kb article.
http://support.microsoft.com/kb/2742275/tr
In most of my cases the performance counter corruption was the reason of this error message there fore I would suggest you to first check the System and application event logs for performance counter corruption. Right click on the System event > Find
and search for corrupt.
Additionally it is also mentioned in one of the MS kb articles that deploying winrm policies on Hyper-V Host is forbidden in a SCVMM environment. 
If this is the reason in your Case you should disable it. No other chance.
Regards,
Cengiz Kuskaya