1 2 Previous Next 18 Replies Latest reply on Apr 23, 2015 5:41 PM by dblansky

    16395 Error

    hunter13 Apprentice

      I have created a brand distribution job and task, I pushed it to a 1000 machines. I have a large number of machines that come back with error 16395 (The package is already installed), This is the first time this package has ran on any of these computers and the strange thing is that all the computers that have error 16395 did run the task and it was successful. Has anyone else seen this behavior and if so how do I make sure it doesn't happen again. We are seeing this a lot since we to 9.6 sp1.

        • 1. Re: 16395 Error
          Specialist

          What package are you trying to install? Do you have any dependencies? What files or registry entries are you using to detect completion? How are you installing it-is it a batch, MSI, EXE?

          • 2. Re: 16395 Error
            hunter13 Apprentice

            I'm using a batch file to push out a few files to everyones computer, not trying to installing anything. No dependencies and I'm not looking at any registry entries to detect completion. Once the batch file is done coping the files it does look for a file to make sure it worked. We are getting the 16395 error before the batch file even runs

            • 3. Re: 16395 Error
              Specialist

              what deployment method are you using? run from source or download & execute?  Using the Local System account or another account? 

              • 4. Re: 16395 Error
                hunter13 Apprentice

                I'm using a policy push, run from source as a local system account

                • 5. Re: 16395 Error
                  Specialist

                  you might want to use a network account - the local system account may not have access to the source where the batch file is saved.

                  • 6. Re: 16395 Error
                    Specialist

                    Or change to download & execute - then the local system account should work fine.

                    • 7. Re: 16395 Error
                      hunter13 Apprentice


                      The local account works, the job runs but it still comes back with error code 16395. Out of a 1000 computers around a 100 come back with that error

                      • 8. Re: 16395 Error
                        Markus.Gonser ITSMMVPGroup

                        Hi hunter13,

                        the requested error code means following:

                         

                        IDS_SDCD_PKG_ALREADY_INSTALLED - 16395

                         

                        It is a LANDESK internal error code.

                        https://community.landesk.com/support/servlet/JiveServlet/download/2013-1044-1149-1173/LANDesk+Error+Codes.pdf

                         

                        best regards

                        Markus

                        • 9. Re: 16395 Error
                          masterpetz ITSMMVPGroup

                           

                          Hi hunter13,

                           

                           

                           

                          We have the same problem at one of our customers and I found out why it happens and opened a case for that because from my point of view it shouldn't happen. Let me explain how to reproduce.

                           

                           

                           

                          - create an accelerated push task or policy supported accelerated push (accelerated is important)

                           

                          - put a device in the task and start it, wait for successful completion

                           

                          - Now add another device (take an offline one, easier to reproduce) to this task and say “Start now – Devices that did not succeed”

                           

                          - the task starts for the new device

                           

                          - do a policy sync on the already successful device, you should now see the updated successful status to already installed client

                           

                           

                           

                          The problem is the new push behaviour in 9.6 that any accelerated push is handled like a policy. With SP1 there is a new accelerated push timeout with a default of 30 minutes. After 30 minutes, the push task is no longer available for devices that come online after this time.

                           

                          If you start your task now to devices that were not successfully and there are devices in this task which were already successful and they randomly start their policy sync through the local scheduler in this 30 minutes, the status changes. That’s the reason why some devices are still “Successful” and some have “Already installed”, some do the policy sync and some not.

                           

                          I hope it was understandable…

                           

                           

                           

                          Kind regards

                           

                          Christian

                           

                           

                           

                           

                           

                          • 10. Re: 16395 Error
                            hunter13 Apprentice

                            Christian

                             

                            Thank you so much, I hope they can get it resolved. Do you know is there away to change the default timeout? I have also noticed with the policy pushes that it takes forever for machines to fail. We have roughly 1200 machines and when I push a policy push out to all the computers before 9.6 I would expect at least 300 machines to fail right away because these people are not in the office or their computers are not turned on. Now it takes 30 minutes to a hour before any of these machines fail.

                            • 11. Re: 16395 Error
                              Specialist

                              that makes some more sense to me now.  I don't really use the Accelerated Push option - I was looking through all my tasks to see if I could find one with that error code & still have yet to find one.  That doesn't mean it hasn't happened, but I have a lot of tasks to go through!

                               

                              Thanks for the info masterpetz... 

                              • 12. Re: 16395 Error
                                masterpetz ITSMMVPGroup

                                Hunter13,

                                 

                                you can find the option for the timeout settings in the Tab "Scheduled Tasks" under the little gear and here it is "Default scheduled Task Settings".

                                 

                                Regards

                                Christian

                                • 13. Re: 16395 Error
                                  Specialist

                                  I really don't understand why this feature is implemented when there are already "detections" that can be set.

                                  • 14. Re: 16395 Error
                                    masterpetz ITSMMVPGroup

                                    Hi Casper,

                                     

                                    Our customer really needs this Feature and push is one of the key Features that always works as install Software on Clients, if the Client is not reachable, do nothing. With 9.6 this behaviour was changed. If a client was offline while the push task runs it fails. When it comes back online the next day and do the policy sync, it checks if there is a policy AND a push available and will do the installation even if it Fails the day before. For some of our customers this is a no go because they are only allowed to do mass rollouts out of business hours and with the new push behaviour this is not possible. LANDESK implemented with SP1 the mentioned Feature how long a push is available for the Clients. If this time runs out, the push will not be executed, by Default it is 30 minutes. This feature has nothing to do with the detection in the packages!

                                     

                                    Kind regards

                                    Christian

                                    1 2 Previous Next