Re: SMS_Inventory_Data_Loader Errors

From: Joseph Calabig [MSFT] (jcalabig_at_microsoft.com)
Date: 06/21/04

  • Next message: Kelly Bubach: "Clients not in AD aren't discovered" 
    Date: Mon, 21 Jun 2004 11:58:41 -0700

    Here's the normal scenario:
        - Inventory is on a weekly cycle
        - Inventory report comes up and Data Loader complained like below and a
    resync request is initiated
        - Resync request is sent to a client.
        - client sees the request. The next inventory cycle- a week from the
    last reporting time- will be a resync report.

    So, can you check the last two occurences of a bad report received from
    client, say UTRMBR06? This should be in the dataldr logs. You should
    increase the log size (say to 5 - 10 mb) if possible while diagnosing this.

    If the next occurence after an error is a success, then your client just
    recovered by sending a resync report. A resync request is a way for the sms
    infrastructure to correct itself after an error. I would expect that there
    could be an initial surge of these requests and it would die down as clients
    start recovering.

    But if the last two subsequent occurences are both rejections AND the are
    LONGER that the Inventory cycle, it means that the client never got the
    resync request. Other areas than Dataloader should be checked- MP perhaps
    or your site to client infrastructure since you have changed your ip
    addresses.
    Note that you can also have 2 consecutive rejections but the client report
    dates are LESS than the Inventory cycle. This means that the client
    generated another report and did not sense the resync request.

    Let's first see what kind of error your getting. 

    -- 
Thanks,
Joseph Calabig
This posting is provided "AS IS" with no warranties, and confers no rights.
"Paul Teheux" <anonymous@discussions.microsoft.com> wrote in message 
news:1f19401c4575f$341927f0$a501280a@phx.gbl...
> The messages look like the one below, normally I would get
> only a few a week, but since we changed the IP-addresses
> in out network, I get many messages per day and don't know
> how to solve them. It causes also problems with
> distributing software and client discovery.
>
> On 06/21/04 09:04:47, component SMS_INVENTORY_DATA_LOADER
> on computer UTRMBR06 reported:  SMS Inventory Data Loader
> failed to process the delta MIF file "XGPY5U5W1.MIF" and
> has moved it
> to "D:\SMS\inboxes\dataldr.box\BADMIFS\7SP83UJV.MIF".
>
> Possible cause: The file is corrupt or contains bad syntax.
> Solution: Review the immediately preceding status messages
> from this component for more details.
>
> If you ignore this problem, SMS will probably fix it and
> complete this operation later. If this error occurs
> repeatedly, refer to your SMS documentation or the
> Microsoft Knowledge Base for further troubleshooting
> information.
>>-----Original Message-----
>>Did it say in the logs that Data loader issued a resync
> request?
>>This resync request will automatically cause your
> client/s send full
>>inventory on the next Hardware Inventory cycle.
>>Once this full report is processed, you should stop
> getting these errors.
>>
>>-- 
>>Thanks,
>>Joseph Calabig
>>
>>This posting is provided "AS IS" with no warranties, and
> confers no rights.
>>
>>"Paul Teheux" <anonymous@discussions.microsoft.com> wrote
> in message
>>news:1e3fb01c45515$e78bceb0$a401280a@phx.gbl...
>>> I'm wondering what is causing all the errors in above
>>> mentioned Component Status?
>>> It fails many times each day about not being able to
>>> process Delta MIF files and moving them to
>>> sms\inboxes\dataldr.box\badmifs.
>>> Is there anyway to stop this?
>>>
>>
>>
>>.
>>
  • Next message: Kelly Bubach: "Clients not in AD aren't discovered"

    Relevant Pages

    • RE: View specific data in report
      ... I assume you have a query as the datasource for the report. ... only print the report for the client which is currently ... inventory ...
      (microsoft.public.access.reports)
    • Re: HINV Changes are not displayed in Resource Explorer
      ... to make sure the client's really trying to get the inventory data you just ... the client did not get the updated hinv policy. ... mofcomp completed successfully. ... The report came to the site server. ...
      (microsoft.public.sms.inventory)
    • Re: Software Inventory SMS 2.0
      ... "full/resync" report the next time SINV runs. ... You can also delete all your client rows from the SoftwareInventoryStatus ... > I'm assuming the SMS inventory client is intelligent to know what data ...
      (microsoft.public.sms.inventory)
    • Re: WMI Classes added to sms_def.mof do not report
      ... The client would have sent a report to the MP for ... Then you need to look at the inventory log on the MP to see if this has been ... > DataItemProperty table (no longer set for hinv reporting) ...
      (microsoft.public.sms.inventory)
    • Re: Help with table structure for manufacturing production counts
      ... I currently receive a weekly report from the plant managers that gives Model numbers, quantity built, and how many have each various options (ie: color, glass doors, casters, compressor hp, voltage etc). ... The buyers in the purchasing department use the data from this report to help them keep track of inventory of their purchased components and predict what they need to buy in the upcoming weeks. ... I began to set up a table to use to house the data that comes from the weekly production reports ...
      (microsoft.public.access.gettingstarted)
    Loading