10 Replies Latest reply on Jun 20, 2009 10:09 PM by Mach6

    Trying to push a software distribution package

    Rookie

      This is what I have done so far.

       

      1.  Downloaded the installer file for Yahoo Messenger.  File is called msgr9us.exe  I downloaded to the core server.

      2.  Created a share on the core server called packages.

      3.  Created a distribution package on the core server called Yahoo Messenger Package.

      4.  Primay file for the package is \\member1\packages\msgr9us.exe

      5.  Added the /s switch as in install option.

      6.  Created a delivery method called Yahoo Messenger Delivery.  I am using the push method.

      7.  I created an associated scheduled task.

       

      I have two virtual machines.  The core server is called member1.  The target client is called 2k3srvr.  I watch both machines when I start the scheduled task.  I see the software distribution task start running on the target client 2k3srvr.  However, it quickly stops with a LanDesk Task Failed error message of:

       

      The task Yahoo Messenger Distribution to deploy the package Yahoo Messenger Package failed.

       

      This is all I get in response.  Obviously, not helpful at all.  So my questions are:  Is there a log or somewhere I can go to find an error code of some sort?  I don't even know how to begin troubleshooting this failure.

       

      When I ran msgr9us /s from the command line on the core server Yahoo Messenger installed silently without prompting me for any input.  It worked just fine.  However, when I try to push this out to the target client the installation doesn't even seem to begin.  The software distribution process starts on the client.  I can tell because an pop up message appears stating.  But then it fails.  Please help.

        • 1. Re: Trying to push a software distribution package
          Employee

          Hi Steve,

           

          There should be a log file available if you right click on the client device from within the task and choose Log File.  If that option's not there then the same log is found on the client under LANDesk\LDClient\Data.  It should be named something with the task id in it.

           

          Also, under LANDesk\LDClient\sdmcache you should see the file being downloaded (if that part's successful).  Of course, if you are using a run from source method instead of download from source then this wouldn't apply.

           

          Please attach the log file and let me know if anything is in your sdmcache folder.

          • 2. Re: Trying to push a software distribution package
            Rookie

            Thanks for the help.  By the way.  I gave up using UNC shares.  It seemed overly complicated as I am running Server 2003 and ASP.NET  and apparently would have to use null session shares.  I am going straight by the book now trying to use Best Known Methods.  So, I created a virtual directory to try installing my package from a web share on the core server.

             

            I am downloading from source, but the only thing that shows up in C:\Program Files\LANDesk\LDClient\sdmcache on the client is the taskmanifest file with the URL for the package and the hash value.  The package itself is not in the cache on the client.

             

            Here is what the log shows:

            Thu, 11 Jun 2009 08:37:42 Checking preferred server path http://member1/packages/msgr9us.exe instead of http://MEMBER1/packages/msgr9us.exe
            Thu, 11 Jun 2009 08:37:46 File (http://MEMBER1/packages/msgr9us.exe) is not in cache
            Thu, 11 Jun 2009 08:37:46 Checking preferred server path http://member1/packages/msgr9us.exe instead of http://MEMBER1/packages/msgr9us.exe
            Thu, 11 Jun 2009 08:37:47 Downloading file to C:\Program Files\LANDesk\LDClient\sdmcache\taskmanifest.MEMBER1.5.3.ini, attempt 0
            Thu, 11 Jun 2009 08:37:50 DownloadFile returned 0
            Thu, 11 Jun 2009 08:37:50

            Downloading file http://MEMBER1/packages/msgr9us.exe (wDeY8w3kkpbDJhnq6O7+uw==, 2)
            Thu, 11 Jun 2009 08:37:50 Downloading file 1 of 1 from 'http://MEMBER1/packages/msgr9us.exe'
            Thu, 11 Jun 2009 08:37:50 Checking preferred server path http://member1/packages/msgr9us.exe instead of http://MEMBER1/packages/msgr9us.exe
            Thu, 11 Jun 2009 08:37:50 The file http://MEMBER1/packages/msgr9us.exe (2 levels) was not in the TMC cache.
            Thu, 11 Jun 2009 08:37:50 The file http://MEMBER1/packages/msgr9us.exe (2 levels) was not in the TMC cache.
            Thu, 11 Jun 2009 08:37:50 Downloading file to C:\Program Files\LANDesk\LDClient\sdmcache\packages\msgr9us.exe, attempt 0
            Thu, 11 Jun 2009 08:37:50 DownloadFile returned 8d860016
            Thu, 11 Jun 2009 08:37:50 ..\AdditionalFiles.cpp(218): (8D860016): Failed to download file http://MEMBER1/packages/msgr9us.exe : (8D860016)

            Thu, 11 Jun 2009 08:37:50 ..\AdditionalFiles.cpp(277): (8D860016): Failed to download and hash all additional files
            Thu, 11 Jun 2009 08:37:50 processing of package is complete, result -1918091226 (0x8dac4026 - code 16422)

            It happens every time.  I can browse the URL from the client machine just fine.  I am completely baffled.  I hope you have some ideas.  I really want to get this working.

            • 3. Re: Trying to push a software distribution package
              Employee

              Steve,

               

              That log file is indicating that the problem is with the local system account accessing the share.  If your package server is the Core server then a really good way to set up a package share is to make it a subfolder under the ldlogon share.  Ldlogon is already set up with the appropriate permissions and settings for both UNC and HTTP distribution, so it's really easy to dump the files there.

               

              My share path is usually something like http://CoreServer/ldlogon/packages/PackageName1/FileToRun.exe.  I prefer HTTP because the Gateway will only work through HTTP (with very limited exceptions that aren't worth the difficulty of settings up).

               

              If it's possible, try moving the package to some subfolder under ldlogon and try again (either HTTP or UNC, but I always use HTTP) and let me know the result.

               

              Thanks!

              1 of 1 people found this helpful
              • 4. Re: Trying to push a software distribution package
                Rookie

                Excellent advice Mach.  We are getting SO close now!  I did just as  you suggested in the previous post.  This time the executable installation file actually downloaded to the client.  The client even launched the executable which is msgr9us.exe (Yahoo Messenger).  I saw the orange smiley face icon in the lower right corner of the taskbar which showed me it was trying to install.  But then the icon disappeared and the task showed up as failed in the scheduled task status window on the core server.  I looked at the log again as you suggested.  This is what shows up in the log now.

                 

                Processing package : Yahoo Package Distribution
                Fri, 12 Jun 2009 00:27:20 Checking preferred server path http://member1/ldlogon/packages/msgr9us.exe instead of http://member1/ldlogon/packages/msgr9us.exe
                Fri, 12 Jun 2009 00:27:20 Path http://member1/ldlogon/packages/msgr9us.exe was redirected to http://member1/ldlogon/packages/msgr9us.exe
                Fri, 12 Jun 2009 00:27:20 File (http://member1/ldlogon/packages/msgr9us.exe) is not in cache
                Fri, 12 Jun 2009 00:27:20 Checking preferred server path http://member1/ldlogon/packages/msgr9us.exe instead of http://member1/ldlogon/packages/msgr9us.exe
                Fri, 12 Jun 2009 00:27:20 Path http://member1/ldlogon/packages/msgr9us.exe was redirected to http://member1/ldlogon/packages/msgr9us.exe
                Fri, 12 Jun 2009 00:27:20 Downloading file to C:\Program Files\LANDesk\LDClient\sdmcache\taskmanifest.MEMBER1.11.4.ini, attempt 0
                Fri, 12 Jun 2009 00:27:22 DownloadFile returned 0
                Fri, 12 Jun 2009 00:27:22

                Downloading file http://member1/ldlogon/packages/msgr9us.exe (wDeY8w3kkpbDJhnq6O7+uw==, 3)
                Fri, 12 Jun 2009 00:27:22 Downloading file 1 of 1 from 'http://member1/ldlogon/packages/msgr9us.exe'
                Fri, 12 Jun 2009 00:27:22 Checking preferred server path http://member1/ldlogon/packages/msgr9us.exe instead of http://member1/ldlogon/packages/msgr9us.exe
                Fri, 12 Jun 2009 00:27:22 Path http://member1/ldlogon/packages/msgr9us.exe was redirected to http://member1/ldlogon/packages/msgr9us.exe
                Fri, 12 Jun 2009 00:27:22 The file http://member1/ldlogon/packages/msgr9us.exe (3 levels) was not in the TMC cache.
                Fri, 12 Jun 2009 00:27:22 The file http://member1/ldlogon/packages/msgr9us.exe (3 levels) was not in the TMC cache.
                Fri, 12 Jun 2009 00:27:22 Downloading file to C:\Program Files\LANDesk\LDClient\sdmcache\ldlogon\packages\msgr9us.exe, attempt 0
                Fri, 12 Jun 2009 00:27:25 DownloadFile returned 0
                Fri, 12 Jun 2009 00:27:25 LSWD or Executable Client Thread
                Fri, 12 Jun 2009 00:27:25 PackagePath:  [http://member1/ldlogon/packages/msgr9us.exe]
                Fri, 12 Jun 2009 00:27:25 Checking recently used server path http://member1/ldlogon/packages/msgr9us.exe instead of http://member1/ldlogon/packages/msgr9us.exe
                Fri, 12 Jun 2009 00:27:25 Path http://member1/ldlogon/packages/msgr9us.exe was redirected to http://member1/ldlogon/packages/msgr9us.exe
                Fri, 12 Jun 2009 00:27:25 Processing generic executable
                Fri, 12 Jun 2009 00:28:32 Launched application 'C:\Program Files\LANDesk\LDClient\sdmcache\ldlogon\packages\msgr9us.exe' ('/s') result 2
                Fri, 12 Jun 2009 00:28:32 Installation result 80070002
                Fri, 12 Jun 2009 00:28:32 processing of package is complete, result -2147024894 (0x80070002 - code 2)

                The most significant lines, I believe, are the last 3.  In the package information section of the of the distribution package properties I have http://member1/ldlogon/packages/msgr9us.exe as the primary file.  In the Install/Uninstall options section of the distribution package properties I entered /s in the command line since msgr9us.exe /s performs a silent/unattended installation.  That's what I am trying to learn to do.  I want to perform silent installations with no user input required using LanDesk.  One last thing.  The executable file of msgr9us.exe is in the sdmcache folder on the client.  So, we know it downloaded and tried to install.  Any ideas why the install failed or what the codes mean on the very last line of the log?

                • 5. Re: Trying to push a software distribution package
                  Rookie

                  Ha ha ha.  I love it.  Here is what I did, Mach.  I created a custom delivery method showing all feedback to the user rather than the standard push which doesn't show feedback.  I forgot that this little executable for Yahoo Messenger has to connect to the Internet to download the main installation files.  I will set up my virtual machine with Internet access and try it again.

                  • 6. Re: Trying to push a software distribution package
                    Rookie

                    Ok, Mach6.  One last issue.  The executable downloaded to the client.  The executable launched and downloaded the main installation package from Yahoo.  I added the /s switch to the package and the installation proceeded silently.  No user input was required.  Yahoo Messenger WAS installed on the client, and it works just fine.  There is a working shortcut to it now on the desktop of the client. I opened it and it ran fine.  HOWEVER... the result of the task still shows up as failed on the core server.  And when I look at the log I still show

                     

                    Fri, 12 Jun 2009 00:28:32 Launched application 'C:\Program Files\LANDesk\LDClient\sdmcache\ldlogon\packages\msgr9us.exe' ('/s') result 2
                    Fri, 12 Jun 2009 00:28:32 Installation result 80070002
                    Fri, 12 Jun 2009 00:28:32 processing of package is complete, result -2147024894 (0x80070002 - code 2)

                    Do you know why the task would report failed with these error codes even though it installed on the client?  Please help.

                    • 7. Re: Trying to push a software distribution package
                      Employee

                      Excellent!  Glad to hear it worked!

                       

                      The short answer on the problem is that the error code you are seeing tells us that Windows is reporting that the installation failed.  In this instance we are simply being the messenger and bringing the reported result back.

                       

                      This could be because there is an "error" that occurs which changes their exit code, but doesn't actually stop the installation.  Another could be that they simply don't use standard exit codes where 0 = success and anything else = failure.  In that scenario Windows might read the exit code, which in this case appears to be 2, and then pass that along, although internally Yahoo has 0 = succes with option A, 1 = success with option B, and 2 = success with option C.  I don't know which (if either) of my scenarios is accurate in this case, because Yahoo would have to tell us that, but the end result is that LANDesk is simply delivering the message it is receiving from Windows, which is pretty much delivering the information it gets from the Yahoo installer (based on the exit code).

                      • 8. Re: Trying to push a software distribution package
                        phoffmann SupportEmployee

                        Just to add to Mach6's great explanation -- we're working on a way to cope with "non standatd exit codes" - so this is in our radar. Office in particular seems to be a culprit here of late.

                         

                        "For the time being", you can intercept the non-0 exit codes via a batch-file (essentially, you kick off the install from the batch, and intercept whatever return code it throws at you ... then based on that, you can decide "yourself" (via the batch file) whether this is an "OK" or a "Not OK" return code, and send a custom one to the LDMS console.

                         

                        In order to pull off this stunt, I would strongly suggest you have a look at the "Understanding batch File distribution" white paper, which you can find here:

                        http://community.landesk.com/support/docs/DOC-2320

                         

                        - Paul Hoffmann

                        LANDesk EMEA Technical Lead

                        • 9. Re: Trying to push a software distribution package
                          Rookie

                          I want to give a huge THANK YOU for all the quick and useful help I have received in this forum.  Here is what I have learned.  I tried ignoring the following from Best Known Methods and learned the hard way.  The reason I couldn't download packages from a UNC share is because I was trying to use a UNC share on a Web server running IIS and ASP.  Best Known methods advises against this unless you complete a bunch of extra esoteric work.  Since then I have set my packages on a standard file server and have had no problems distributing from a UNC share.

                           

                          Here is my next project.  Pushing out a silent/unattended install of Office 2007 Pro (trial version) to a client using LanDesk.  So far so good.  I can see the files downloading.  I have also successfully tested a silent install using the config.xml locally.  In other words, the package was already on the machine.  I just moved the config.xml file to the same folder containing setup.exe.  I edited the config.xml file then just ran setup.exe and the silent install worked perfectly.  I am really enjoying learning LanDesk.  This is cool stuff.

                          • 10. Re: Trying to push a software distribution package
                            Employee

                            Uh oh, another one with the bug.  [-8  LANDesk is really a fun tool to use.  Too fun sometimes.  I think they need a 12 step program to help some of us out.