7 Replies Latest reply on Aug 28, 2008 12:13 PM by MarXtar

    Failed to download additional files error after LD8.8 upgrade

    tdavenport Specialist

      I recently upgraded a client to 8.8 SP1. I performed SWD tests before I left and everything seemed to work fine. Recently, they've seen errors with SWD stating "Failed to download file" with codes "(800708CA)" and " -1918091226 (0x8dac4026 - code 16422)" . The application (obviously) fails to install. HOWEVER, the application is fully copied to to the sdmcache folder - they just never execute.

       

      I've read a couple of posts that reference this issue but neither have a solution. I've seen references to having the FQDN specified in the agent config and another reference to the agenht not getting the task manifest. Concerning the FQDN of the core server, only the core name is listed in the agent config (DNS is working fine BTW).  And in reference to the task manifest - well I'm not sure what I need to look for here. It sounds like it could be a symptom or is related to the issue but again, I'm not sure how to address this.

       

      I've created new Soft Dist Packages and re-hashed to no avail.

       

      In summary - the problem is that the appliaction is copied to the sdmcache folder but the install never runs. The error is "Failed to download file" with codes "(800708CA)" and " -1918091226 (0x8dac4026 - code 16422)"

       

      Any and all suggestions are welcome.

       

      Thanks in advance!

        • 1. Re: Failed to download additional files error after LD8.8 upgrade
          Rookie

          Hello,

           

          Just an idea, do you use multiple package servers? If you have recreated the package / changed it and have not syncronised between all your package servers you will get a hash fail which will cause this.

           

          Regards,

          • 2. Re: Failed to download additional files error after LD8.8 upgrade
            tdavenport Specialist

            What exactly do you mean by "syncronize between all you package servers"?  There are two package servers. They do not house the same packages.

             

            The first package server was the core. It has just a few applications. Space quickly became an issue so a new server was designated to be the package server (it is also configured as the preferred server. - Keep in mind, however, that we are specifying the URL (http) and not the UNC path in the distribution package. As I said before, the full package is copied to the SDMCACHE folder. It just never executes. Here is the full error.

             

            I JUST NOTICED THIS...IT COULD BE RELATED. Notice the two different  URLs for the package. The server named RIS01 is the actual package server BUT IT DOES NOT HAVE IIS LOADED. Only the core server (LDWEB01) has IIS. You cannot reach RIS01 via http directly. You have to go to http://ldweb01/ris01packages. LDWEB01 simply redirects to the RIS share. But if you look at the log, it appears as though the task is trying to got straight to http://RIS01/packages. I've checked the settings in the package and it points to the proper location (http://ldweb01/ris01packages/Star 13.13/Test/STAR Navigator 13.13 Test.msi). I've also check my preferred server settings. RIS01 is configured as the preferred server. The reason I have RIS01 configured as the preferred server is because the client was frequently creating packages that pointed to the UNC path of RIS01 instead of using the URL.

             

            Could the core be assuming that RIS01 is also a web server? This was never an issue in 8.7. Would 8.8 make this assumption. Again, http://RIS01 is an invalid address - but it appears in the log. http://ldweb01 is a valid address.

             

            Processing package : Star Test 13.13

            Wed, 27 Aug 2008 12:10:31 Checking preferred server path http://RIS01/ris01packages/Star 13.13/Test/STAR Navigator 13.13 Test.msi instead of http://ldweb01/ris01packages/Star 13.13/Test/STAR Navigator 13.13 Test.msi

            Wed, 27 Aug 2008 12:10:32 File (http://ldweb01/ris01packages/Star 13.13/Test/STAR Navigator 13.13 Test.msi) is not in cache

            Wed, 27 Aug 2008 12:10:32 Checking preferred server path http://RIS01/ris01packages/Star 13.13/Test/STAR Navigator 13.13 Test.msi instead of http://ldweb01/ris01packages/Star 13.13/Test/STAR Navigator 13.13 Test.msi

            Wed, 27 Aug 2008 12:10:34 .\AdditionalFiles.cpp(63): (8DAC4026): Failed to download file http://LANDesk.Gateway@172.16.70.70/ldlogon/FileLists/taskmanifest.LDWEB01.474.196.ini : (800708CA)

            Wed, 27 Aug 2008 12:10:34 processing of package is complete, result -1918091226 (0x8dac4026 - code 16422)

            • 3. Re: Failed to download additional files error after LD8.8 upgrade
              Rookie

              I was reffering to multiple servers holding the same packages.

               

              Sorry

              • 4. Re: Failed to download additional files error after LD8.8 upgrade
                tdavenport Specialist

                The problem is solved - Could this be it?

                 

                I have resolved the problem but it would be helpful if someone could confirm if this is truly the solution.

                 

                I changed the core server name in the agent configuration to the FQDN. So now the core server is CORENAME.DOMAINNAME.COM. I then deployed that agent. Everything seems to be working fine now. Files are copied and they execute from the SDMCACHE folder.

                 

                The only change was to insert the FQDN of the core server in to the agent. Previously, only the core server name was listed. Did this fix the problem or was there some other reason. I'd hate to think that simply redeploying an agent WITHOUT any changes would have solved the problem as well. The problem was happening on all machines so it wasn't a corrupted agent.

                • 5. Re: Failed to download additional files error after LD8.8 upgrade
                  MarXtar ITSMMVPGroup

                  It is a bit unusual for you to reference packages by http but specify a preferred server that doesn't have IIS.  I wouldn't be surprised if what is really happening is that the packages are coming from your core server via http as a failover after it tries to speak to your preferred server..

                   

                  If you have your core redirecting to the other server, then keep the core as your package server and don't specify the other server as your preferred server since the packages can't be accessed in that way.

                   

                  Mark Star - MarXtar LANDesk Enhancements

                   

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

                   

                  • 6. Re: Failed to download additional files error after LD8.8 upgrade
                    tdavenport Specialist

                    Yeah, I know that I'm trying to have it both ways. Again, the only reason I specified that server at all was because my client was repeatedly specifying a UNC path (in Dist Pack.) directly to the package server instead of using the URL for the core. He got away with that for a while until a domain migration a few months back. He had about 50 packages pointing to the UNC path.So, I set up a preferred server to accomodate him and save him the trouble of editing his Dist. Packages. I should probably do as you say and simply emphasize the importance of using a URL in his current and future packages.

                     

                    As far as the FQDN of the core in the agent config, do you think this is simply a coincidence that my problem went away. If so, will I see this problem agent again - perhaps when preferredserver.dat is copied down to managed devices again?

                    • 7. Re: Failed to download additional files error after LD8.8 upgrade
                      MarXtar ITSMMVPGroup

                      Hard to say for certain since that change may have affected LANDesk or potentially even may have been related to you using DFS.  Sorry, I can't be more certain because it is a fairly unusual setup you have there.

                       

                       

                      Mark Star - MarXtar LANDesk Enhancements

                       

                       

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