10 Replies Latest reply on Sep 16, 2008 10:46 PM by Binskin

    Unable to push a simple batch file

    Binskin Apprentice

      This issue roles back to a previous problem i have had with the SP1 update, relating to old firewall policies attempting to be pushed out with new clients (old policy no longer exists, client references it, it fails - unable to complete security scans, unable to apply updates etc) the solution was to run a basic batch file, which i have done on my servers. But i now have the task of updating the remaining 70 client work stations of which i do not want to complete manually.

       

      LD Support created a basic 1 line batch:

       

      reg add hklm\software\landesk\managementsuite\winclient\vulscan /v FirewallBehavior /t REG_DWORD /d 6 /f

       

      Which updates the registry to point to a current firewall policy. For the life of me i have not been able to get this simple batch distributed, it continually fails with the 'Failed to download all additional files for a package', the log explains:

       

      17:13:32 Checking preferred server path http://MILAPP04/SoftwareDistribution/Reg_Update.bat instead of http://MILAPP04/SoftwareDistribution/Reg_Update.bat

      17:13:32 File (http://MILAPP04/SoftwareDistribution/Reg_Update.bat) is not in cache

      17:13:32 Checking preferred server path http://MILAPP04/SoftwareDistribution/Reg_Update.bat instead of http://MILAPP04/SoftwareDistribution/Reg_Update.bat

      17:13:32 ..\AdditionalFiles.cpp(63): (8DAC4026): Failed to download file http://LANDesk.Gateway@10.11.2.78/ldlogon/FileLists/taskmanifest.MILAPP04.656.56.ini : (800704D2)

      17:13:32 processing of package is complete, result -1918091226 (0x8dac4026 - code 16422)

       

      Ive read the articles that explain reset package hash, check iis settings etc all to no avail, it was explained the SP2 would resolve this issue but it looks like it does not from my initial testing.

       

      Any help would be greatly appreciated.

       

      Cheers - Ben

       

       

        • 1. Re: Unable to push a simple batch file
          phoffmann SupportEmployee

          This has nothing to do with package hashes.

           

          Package hash-problems would have lines in the log-file indicating that file X has been discarded because the hash didn't match.

           

          This is about (failing to) download(-ing) the task-manifest.

           

          Each software dist job has a task manifest - this file contains the "download these files"-list, along with locations and hash-values. Without that, the client doesn't know what files to grab.

           

          So in your case, the client is complaining about being unable to download the manfiest. Have a look in your Core's IIS-log about this file ... see what kind of return code you got on that request from this client.

           

          I've seen a few times now that the permissions (NTFS and/or IIS) on the directory were borked, and this lead to such error messages :).

           

          Paul Hoffmann

          LANDesk EMEA Technical Lead

          • 2. Re: Unable to push a simple batch file
            MarXtar ITSMMVPGroup

            This is definitely something you should troubleshoot since it is likely to cause you issues whn doing other jobs.  Until you do resolve it, try using a Custom Script to get the job done since it doesn't use the manifests.  You will be restircted to hitting machines that are currently on though.

             

            Attached file is an example script.

             

            Mark Star - MarXtar LANDesk Enhancements

            Home of Power State Notifier & Wake-On-WAN for LANDesk

            • 3. Re: Unable to push a simple batch file
              Binskin Apprentice

              Thanks for getting back to me, ive retried the job and checked the IIS log files and received the following:

               

              2008-09-15 12:06:35 W3SVC1 10.11.2.78 POST /LANDesk/ManagementSuite/Core/PreferredServer/preferredserver.asmx - 80 - 10.11.4.10 - 200 0 0
              2008-09-15 12:06:35 W3SVC1 10.11.2.78 HEAD /SoftwareDistribution/Reg_Update.bat - 80 - 10.11.4.10 2772-LANDeskDownloader 401 2 2148074254
              2008-09-15 12:06:35 W3SVC1 10.11.2.78 HEAD /SoftwareDistribution/Reg_Update.bat - 80 - 10.11.4.10 2772-LANDeskDownloader 401 2 2148074254
              2008-09-15 12:06:35 W3SVC1 10.11.2.78 HEAD /SoftwareDistribution/Reg_Update.bat - 80 - 10.11.4.10 2772-LANDeskDownloader 401 2 2148074254
              2008-09-15 12:06:35 W3SVC1 10.11.2.78 HEAD /SoftwareDistribution/Reg_Update.bat - 80 - 10.11.4.10 2772-LANDeskDownloader 401 2 2148074254
              2008-09-15 12:06:35 W3SVC1 10.11.2.78 HEAD /ldlogon/FileLists/taskmanifest.MILAPP04.656.56.ini - 80 - 10.11.4.10 2772-LANDeskDownloader 200 0 0

               

              Ill look further into IIS logs in the morning (10:30pm here in Sydney) but if anything jumps out please let me know.

               

              Cheers - Ben

              • 4. Re: Unable to push a simple batch file
                phoffmann SupportEmployee

                Well - the 401's are a problem.

                 

                401 == Unauthorized

                 

                You may want to make sure your share is set up to be an anonymous share :).

                 

                Paul Hoffmann

                LANDesk EMEA Technical Lead

                1 of 1 people found this helpful
                • 5. Re: Unable to push a simple batch file
                  Binskin Apprentice

                  Excellent, that bit is fixed, now the log looks like this:

                   

                  2008-09-15 12:32:23 W3SVC1 10.11.2.78 HEAD /SoftwareDistribution/Reg_Update.bat - 80 - 10.11.4.10 1388-LANDeskDownloader 200 0 0
                  2008-09-15 12:32:23 W3SVC1 10.11.2.78 HEAD /ldlogon/FileLists/taskmanifest.MILAPP04.656.56.ini - 80 - 10.11.4.10 1388-LANDeskDownloader 200 0 0

                   

                  But i still receive the same fail message

                   

                  The job log looks like:

                   

                  Mon, 15 Sep 2008 22:34:52 Checking preferred server path http://MILAPP04/SoftwareDistribution/Reg_Update.bat instead of http://MILAPP04/SoftwareDistribution/Reg_Update.bat
                  Mon, 15 Sep 2008 22:34:52 Path http://MILAPP04/SoftwareDistribution/Reg_Update.bat was redirected to http://MILAPP04/SoftwareDistribution/Reg_Update.bat
                  Mon, 15 Sep 2008 22:34:52 File (http://MILAPP04/SoftwareDistribution/Reg_Update.bat) is not in cache
                  Mon, 15 Sep 2008 22:34:52 Checking preferred server path http://MILAPP04/SoftwareDistribution/Reg_Update.bat instead of http://MILAPP04/SoftwareDistribution/Reg_Update.bat
                  Mon, 15 Sep 2008 22:34:52 Path http://MILAPP04/SoftwareDistribution/Reg_Update.bat was redirected to http://MILAPP04/SoftwareDistribution/Reg_Update.bat
                  Mon, 15 Sep 2008 22:34:52 ..\AdditionalFiles.cpp(63): (8DAC4026): Failed to download file http://LANDesk.Gateway@10.11.2.78/ldlogon/FileLists/taskmanifest.MILAPP04.660.56.ini : (800704D2)
                  Mon, 15 Sep 2008 22:34:52 processing of package is complete, result -1918091226 (0x8dac4026 - code 16422)

                   

                  [edit]

                  From a test machine ive also tried the following:

                   

                  http://LANDesk.Gateway@10.11.2.78/ldlogon/FileLists/taskmanifest.MILAPP04.660.56.ini - URL Fails

                  http://10.11.2.78/ldlogon/FileLists/taskmanifest.MILAPP04.660.56.ini - URL is Good

                   

                  Where doe the 'LANDesk.Gateway' account come from?

                  • 6. Re: Unable to push a simple batch file
                    phoffmann SupportEmployee

                     

                    Simply put, the client "always" thinks it's in Gateway mode ... so it logs as if it were. It's a design-logic thing, and can be safely ignored :).

                     

                    Try running a Filemon on the taskmanifest / the directory and re-start the job.

                     

                    Strange as it sounds, I don't trust the IIS log 100% ... I've seen it claim status 200 when the IIS-user didn't have permission to hit the file. Filemon should help you make sure :).

                     

                    Paul Hoffmann

                    LANDesk EMEA Technical Lead

                    • 7. Re: Unable to push a simple batch file
                      Binskin Apprentice

                      Paul,

                      Thanks for your continued assistance, ive run filemon with the resultant log attached. It seems to be able to access the file Ok, but then adds malformed data to the end of the filename, which it then is unable to find. Which is i guess why IIS reports its found it, which it has, but then something goes astray with the file name call.

                       

                      Message was edited by: Ben Rooney [attached files]

                      • 8. Re: Unable to push a simple batch file
                        phoffmann SupportEmployee

                        Huh - interesting. That's the

                        C:\Program Files\LANDesk\ManagementSuite\ldlogon\FileLists\taskmanifest.MILAPP04.661.56.ini\:Docf_|DocumentSummaryInformation:$DATA
                        

                         

                        reference you talk about? Not quite sure why that's happening.

                         

                        If you're on 8.8, I'd suggest hopping on to SP2, and see if that fixes it. If you're on 8.7, log a ticket with support, asking for the latest scheduler patch ... at this point, I'm wondering/thinking that there's something iffy with that on your Core, and hopefully this should fix it.

                         

                        If the behaviour remains the same, I'd suggest logging a ticket with support and VMWare'ing your Core server (including a backup of the DB, which we'd need) to see if we can duplicate the matter on our end. If we can, then we should stand a chance at finding out what's going on...

                         

                        ... not seen anything like this before. At least the Filemon trace explains why things fall over ... not quite sure about what's causing it though. Is IIS broken ...? Hard to say .

                         

                        Paul Hoffmann

                        LANDesk EMEA Technical Lead

                        • 9. Re: Unable to push a simple batch file
                          ahe Expert

                          Hello Ben, hello Paul,

                           

                          I've the same "mysterious entries", if I browse to the file...  I think this entries are no LANDesk fault, it's a filemon feature...

                           

                          • Start filemon.exe,

                          • put a file in the include field of the filemon filter (for example win.ini),

                          • start the scan,

                          • open the file with notepad.exe

                          • some entries in filemon arrived

                          • open the Windows Explorer and browse to windows directory

                          • a lot of mysterious entries arrived

                          • mark win.ini

                          • more mysterious entries arrived

                           

                          At first I thougt it is a alternate data stream in the file appended, but I can't find some...

                           

                          I've checked it with the new ProcessMonitor from sysinternals which replaced filemon and get the same... 

                           

                          Regards

                          Axel

                           

                          I found some hints here: http://forum.sysinternals.com/forum_posts.asp?TID=8958 It seems it is a alternate data stream scan from Explorer...

                          • 10. Re: Unable to push a simple batch file
                            Binskin Apprentice

                            Thanks guys for all of your assistance, ive come across a work around for the firewall policy update so it will no longer be an issue, but i guess my core issue i still have not been able to resole in being able to push batch files, i will raise job with support to have a look and hopefully get it resolved.

                             

                            Cheers - Ben