1 Reply Latest reply on Jan 10, 2018 4:28 AM by phoffmann

    Ivanti agent causing errors on local machine

    GabrielV Rookie

      Hi,

      I'm fairly new on the Ivanti software and since day one, we have a continuous issue with Ivanti agent.

      We are keep getting an error message with Dell OMCI driver. We do not have any Dell machines on our fleet.

       

      Log Name:      Application

      Source: Application Error

      Date: 09/01/2018 10:21:17

      Event ID:      1000

      Task Category: (100)

      Level:         Error

      Keywords:      Classic

      User: N/A

      Computer: xxx

      Description:

      Faulting application name: LDDellOMCI.exe, version: 10.1.30.401, time stamp: 0x59a01425

      Faulting module name: LDDellOMCI.exe, version: 10.1.30.401, time stamp: 0x59a01425

      Exception code: 0xc0000417

      Fault offset: 0x0002dc5e

      Faulting process id: 0x1660

      Faulting application start time: 0x01d38933957b6d8b

      Faulting application path: C:\Program Files (x86)\LANDesk\LDClient\LDDellOMCI.exe

      Faulting module path: C:\Program Files (x86)\LANDesk\LDClient\LDDellOMCI.exe

      Report Id: d37871fb-f526-11e7-9005-c821588ac5db

      Event Xml:

      <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

        <System>

          <Provider Name="Application Error" />

          <EventID Qualifiers="0">1000</EventID>

          <Level>2</Level>

          <Task>100</Task>

      <Keywords>0x80000000000000</Keywords>

          <TimeCreated SystemTime="2018-01-09T10:21:17.000000000Z" />

      <EventRecordID>9516</EventRecordID>

          <Channel>Application</Channel>

      <Computer>xxx.xxxDomain.ie</Computer>

          <Security />

        </System>

        <EventData>

          <Data>LDDellOMCI.exe</Data>

          <Data>xx.xx.xx.xx</Data>

          <Data>59a01425</Data>

          <Data>LDDellOMCI.exe</Data>

          <Data>xx.xx.xx.xx</Data>

          <Data>59a01425</Data>

          <Data>c0000417</Data>

          <Data>0002dc5e</Data>

          <Data>1660</Data>

          <Data>01d38933957b6d8b</Data>

          <Data>C:\Program Files (x86)\LANDesk\LDClient\LDDellOMCI.exe</Data>

          <Data>C:\Program Files (x86)\LANDesk\LDClient\LDDellOMCI.exe</Data>

      <Data>d37871fb-f526-11e7-9005-c821588ac5db</Data>

        </EventData>

      </Event>

       

      Any help will be much appriciated.

        • 1. Re: Ivanti agent causing errors on local machine
          phoffmann SupportEmployee

          So ...

           

          Welcome to the community!

           

          1 - You want to get into a habit of posting what version you're on (i.e. "EPM 2017.3 + SU1" for instance). That helps a lot.

           

          2 - For this particular issue, read up the article (+ comments) here -- Application Errors: ldHPSensors.exe and LDDellOMCI.exe .

           

          A bit of using the search function can also yield such results .

           

          As a general note (since you're relatively new to this) - there's LOTS of technical training / How-to's and such on the community too -- feel free to learn. Furthermore, there's freely available recorded webinars for all manner of topics that you can access here -- Momentum (check the schedule for new stuff, check the "on-demand" stuff for older sessions).

           

          There's LOTS to learn (yes, it takes a while. No - don't be intimidated - everyone has to start out at the same place) ... but chances are, if you're trying to do it, there's docs & such on how to do so in various ways. One thing to get used to is a general thing I've been stating for years -- "There's usually at least 3 different ways of achieving the exact same thing in LANDesk / Ivanti" ... so a lot of "chose your adventure" stuff tends to apply. The net result is usually the same - but how (and WHY) you get there - that's up to a lot of choice.

           

          Hope that helps!

           

          ==========

           

          Addendum:

           

          3 - I'd still suggest you poke support about this one - purely to communicate with them about what hardware you *DO* have, so that we can figure out (as needed) why that stuff makes it down / seems to run into issues on to non-Dell hardware. That one's a bit odd, I agree.