8 Replies Latest reply on Jun 19, 2009 10:12 AM by Bd0g

    What log file do I need to look at...

    Apprentice

      ...If my inventory scanner is stopping half way through on 1 client?

       

      88sp2

        • 1. Re: What log file do I need to look at...
          zman Master

          Add a /DEBUG switch to the inventory scan shortcut and open the ldiscn32.exe.log file from c:\program files\landesk\ldclient\data\

          • 2. Re: What log file do I need to look at...
            Apprentice

            This is what is at the end of ldiscn32.log.  Does this indicate there were no errors?

             

            Mon Jun 15 09:09:34 2009: total files  :   25371
            Mon Jun 15 09:09:34 2009: total WinExe :   419 files,   6.22647275 seconds
            Mon Jun 15 09:09:34 2009: total NoWinExe :   682 files,   0.00398486 seconds
            Mon Jun 15 09:09:34 2009:   Buffering data: Number of Files =  25371
            Mon Jun 15 09:09:34 2009:   Buffering data: Multimedia Files - Total Size =    17.6 MB
            Mon Jun 15 09:09:34 2009:   Buffering data: Multimedia Files - Number of Files =   1081
            Mon Jun 15 09:09:34 2009: Software scan finished.
            Mon Jun 15 09:09:34 2009: Scanning MIF files.
            Mon Jun 15 09:09:34 2009: Clean up communications links.
            Mon Jun 15 09:09:34 2009: Clean up windows sockets.
            Mon Jun 15 09:09:34 2009: Exiting out at end of scanner.

             

            I do see some failed statements though, what do they mean?

            Mon Jun 15 09:09:02 2009: Initializeing DMI
            Mon Jun 15 09:09:02 2009: DMIAPI32 load failed.
            Mon Jun 15 09:09:02 2009: DeInitializing DMI

             

            Mon Jun 15 09:09:19 2009:   Buffering data: Last Software Scan Date = 1245071359
            Mon Jun 15 09:09:19 2009: GetLongPathName failed with 0 : GetLastError : 2

            Mon Jun 15 09:09:19 2009: GetLongPathName failed with 0 : GetLastError : 2

            ...  <Lots of these>

            Mon Jun 15 09:09:19 2009:   Inflating C:\Program Files\LANDesk\LDClient\Data\LDAPPL3.INI

            • 3. Re: What log file do I need to look at...
              Master

              Jeremiah,

               

              Based on your debug log it is failing on software scanning. The inventory scanner is using the ldappl3.ini file that is local to the client pulled from the core server. Here is what I suggest:

               

              1. On the core, delete all of the ldappl3 files except the ldappl3.template file.

              2. In the console under Software License Monitoring, select the "Make available to clients" button. (To recreate all the deleted ldappl3 files)

              3. On the client, delete all the ldappl3 and invdelta.dat files from C:\program files\landesk\ldclient\data

              4. Run the inventory scan

               

              Let me know if it still crashes.

               

              Thanks!

              • 4. Re: What log file do I need to look at...
                Apprentice

                It is still stopping.  I am wondering if it is because of something I added.

                 

                Is there anyway to tell what is it messing up on?

                • 6. Re: What log file do I need to look at...
                  Master

                  I agree with Zman, if your seeing this only on one or two machines typically the WMI is corrupted.

                  1 of 1 people found this helpful
                  • 7. Re: What log file do I need to look at...
                    Apprentice

                    I have run all things mentioned.  It says that WMI is working, but there were a few warnings.

                     

                    Not that, wmi is not also an issue, but it is what would be messing up software inventory scans?

                     

                    Is there a way to find out what SW scans could be stopping the process?

                    • 8. Re: What log file do I need to look at...
                      SupportEmployee

                      The way to tell where the inventory scanner stopped was as described by ZMan above. Running the scanner with /debug and getting the log out of ldclient\data.

                      The last line in the log is the last thing the scanner did. So if it is still stopping on uncompressing ldappl3.ini, then its possible your client has some corrupt ldappl3 files.

                      Try deleting all ldappl3 files from these three locations(where present):

                      C:\Program Files\LANDesk\LDClient\Data\

                      C:\Program Files\LANDesk\LDClient\Data\SDMCache

                      C:\Program Files\LANDesk\LDClient\sdmcache

                       

                      Then run a full inventory scan, and keep the debug on to see if it makes it further or still fails in the same place.

                      If it does, look at the ldappl3.ini and compare it to the one on the core in ldlogon. Make sure they are the same.