Hello,
I am getting since yesterday evening tons of messages:
Severity Type Site code Date / Time System Component Message ID Description Warning Milestone SRV 7/17/2015 12:38:05 PM CONFIGMGRSRV SMS_INVENTORY_DATA_LOADER 2703 SMS Inventory Data Loader failed to process the delta MIF file "XHY1PREIW.MIF" and has moved it to "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\dataldr.box\BADMIFS\68pa11j6.MIF." Possible cause: The file attempted to update inventory information in the SMS site database that does not already exist, or the file contains invalid syntax. Solution: The client inventory needs to be resynchronized, which will be done automatically. Look for the status messages 2714 and 2715, which indicate the resynchronization has begun. Severity Type Site code Date / Time System Component Message ID Description Warning Milestone SRV 7/17/2015 2:07:59 PM CONFIGMGRSRV SMS_SOFTWARE_INVENTORY_PROCESSOR 3707 SMS Software Inventory Processor failed to process software inventory file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\sinv.box\D2VH2KI7.SID" because the file does not have a corresponding discovery record. SMS Software Inventory Processor has moved this file to the Orphans directory as file "C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\sinv.box\Orphans\4zi1u1ta.SID" and will retry processing it later. When SMS Software Inventory Processor receives a software inventory file, it acquires the unique numeric ID for the file it is processing from the discovery data in the SMS site database. If this cannot be found, a discovery data record (DDR) is generated, and the software inventory file is temporarily moved to the Orphans directory, where SMS Software Inventory Processor retries the file every 10 minutes. Possible cause: SMS Discovery Data Manager is not running. Solution: Stop and restart SMS Discovery Data Manager. You can use SMS Service Manager, which is invoked from the SMS Administrator console, to stop and start components.
SMS_DISCOVERY_DATA_MANAGER is running!!
what could be the source of the issue?
How to resolve it?
Thanks,
Dom