{"id":1043,"date":"2013-10-16T11:09:02","date_gmt":"2013-10-16T09:09:02","guid":{"rendered":"http:\/\/sccmfaq.wordpress.com\/?p=1043"},"modified":"2013-10-16T11:09:02","modified_gmt":"2013-10-16T09:09:02","slug":"sccm-2012-troubleshot-hardware-inventory-import","status":"publish","type":"post","link":"https:\/\/blog.hosebei.ch\/?p=1043","title":{"rendered":"SCCM 2012 – Troubleshot Hardware Inventory import"},"content":{"rendered":"

Hey, here is Martin again, in this Blogpost I would like to explain, how you can resolve Problems with Hardware Inventory and BADMIF and also Delta Mismatch Errors.<\/p>\n

I tested around with some WMI classes, and ended up with Errors in “SMS_INVENTORY_DATA_LOADER”, all of them coming up with Message ID 2700 and text:<\/p>\n

Inventory Data Loader failed to read the delta MIF file “D:\\Program Files\\Microsoft Configuration Manager\\inboxes\\authdataldr.box\\Process\\XH1X3RT45.MIF” and will move the file to the BADMIFs directory.<\/p><\/blockquote>\n

\"BadMIF<\/a><\/p>\n

This led me to check, if there are more Information in the dataldr.log, and surprisingly, there were:
\n\"Dataldr.log\"<\/a>
\nMost important Information in this log is, which MIF I should check, and on which line the MIF could not be read through SCCM:<\/p>\n

Compilation failed~syntax error on line 30, token ‘,’
\nCannot process MIF XH7T9DDUL.MIF, moving it to D:\\Program Files\\Microsoft Configuration Manager\\inboxes\\authdataldr.box\\BADMIFS\\ErrorCode_4\\ss753bg7.MIF<\/p><\/blockquote>\n

I’m then going to open the file ss753bg7.MIF to see, which line produced the error:
\n\"BadMIF\"<\/a>
\nSo as a said, I tested around, and this WMI Class “WmiMonitorID” was from those testings. So, Problem found, I easily remove this WMI class from the Hardware Inventory, I also deleted it:
\n\"Remove<\/a><\/p>\n

After a Machine Policy Update, and another Hardware Inventory Cycle, the Hardware Inventory should be written again to the SCCM Database. In my case, the next Problem was coming up with the Delta Mismatch Errors. I can’t tell you, how this Problem is produced, but I found a way through TechNet Forums, to create a full Hardware inventory which solves the Problem with the Deltas. First, the Error Messages in the System Center 2012 Configuration Manager Console:<\/p>\n

Inventory Data Loader failed to process the delta MIF file “XHWPE4KKD.MIF” and has moved it to “D:\\Program Files\\Microsoft Configuration \\Manager\\inboxes\\authdataldr.box\\BADMIFS\\DeltaMismatch\\kvw1avzj.MIF.”<\/p><\/blockquote>\n

\"BadMIF<\/a>
\nThis message is coming over and over again. To solve this, I simply followed the Description from Torsten in a SCCM TechNet Forum (unfortunately I can’t find the link to this post anymore\u00a0:(). Open wbemtest.exe as local Administrator on the particular system, in my case, it was the Domain Controller:
\n\"Check<\/a>
\n\"wbemtest\"<\/a>
\nClick on connect, and connect to Root\\ccm\\InvAgt:
\n\"Connect<\/a>
\nClick on “Enum classes” and in this opening Dialog, select “Recursive” and click on OK:
\n\"Superclass<\/a>
\nNavigate then to the “InventoryActionStatus” and double click this entry:
\n\"Query<\/a>
\nYou have then opened the Object editor for InventoryActionStatus, simply click on “Instances” to view those:
\n\"Instances\"<\/a>
\nSelect the Instance with ID ending on 000000000000001 and click on delete, to delete this instance:
\n\"Delete<\/a>
\nClose all open Dialogs from wbemtest, and go to your logfile Location of your SCCM Client and open InventoryAgent.log, and then start a Hardware Inventory Cycle or wait until the scheduled cycle is done. You should find the following entry which tells you, that a Full Inventry was created:<\/p>\n

Inventory: Version number mismatch; will do a Full report.<\/p><\/blockquote>\n

\"Hardware<\/a><\/p>\n

Hope this helps \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"

Hey, here is Martin again, in this Blogpost I would like to explain, how you can resolve Problems with Hardware Inventory and BADMIF and also Delta Mismatch Errors. I tested around with some WMI classes, and ended up with Errors in “SMS_INVENTORY_DATA_LOADER”, all of them coming up with Message ID 2700 and text:<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,19],"tags":[],"class_list":["post-1043","post","type-post","status-publish","format-standard","hentry","category-client-agent","category-general"],"_links":{"self":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/1043","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1043"}],"version-history":[{"count":0,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/1043\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1043"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1043"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1043"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}