1 2 3 4 Previous Next 45 Replies Latest reply on Jul 14, 2017 2:00 AM by phoffmann

    Provisioning templates failing after using reboot commands

    1EarEngineer Specialist

      anyone else getting an

      FAILED error:[80000000H]An unknown error occurred. after using a reboot action while doing provisioning? Doesn't seem to matter what my next step is, distribute software, execute command, whatever follows after the going back into the OS after using the Reboot action, always produces FAILED error:[80000000H]An unknown error occurred. If I remove the reboot command, the other actions work fine.


      Running 9.6 SP2


      This is all being done in the System Config section. The device reboots, performs an auto login back to the OS, and then provisioning resumes, but whatever action is set to occur after the reboot action that just occurred, will fail with the above error. Here is my XML of the action. Strange even more is that even though the next action is set to continue if it fails, the task will fail, and stop.

       

      <action name="Reboot" version="4">

         <description />

         <action-type>Reboot_shutdown</action-type>

         <variables />

         <options>

          <option name="StopProcessingTemplateIfActionFails">false</option>

         </options>

         <parameters>

          <usepeer>True</usepeer>

          <usepref>True</usepref>

          <usesource>True</usesource>

          <type>reboot</type>

          <TimeOut>0</TimeOut>

         </parameters>

        </action>

       

      Message was edited by: Jason Lesko Added more info

        • 1. Re: Provisioning templates failing after using reboot commands
          Apprentice

          Hi Gru,

           

          using Reboot in System configuration section?

          is the Reboot Action itself successfully (is the device rebooting)

           

          in XML view...  is there the following:

           

          <action name="Reboot/shutdown" version="4">

             <description />

             <action-type>Reboot_shutdown</action-type>

             <variables />

             <options>

              <option name="StopProcessingTemplateIfActionFails">false</option>

             </options>

             <parameters>

              <usepeer>True</usepeer>

              <usepref>True</usepref>

              <usesource>True</usesource>

              <type>reboot</type>

              <TimeOut>2</TimeOut>

             </parameters>

            </Action>

          • 2. Re: Provisioning templates failing after using reboot commands
            1EarEngineer Specialist

            Sorry for not providing that in the original post, will make sure to go back and add that.

            This is indeed all being done in the System Config section. The device reboots, performs an auto login back to the OS, and then provisioning resumes, but whatever action is set to occur after the reboot action that just occurred, will fail with the above error. Here is my XML of the action. Strange even more is that even though the next action is set to continue if it fails, the task will fail, and stop.

             

            <action name="Reboot" version="4">

               <description />

               <action-type>Reboot_shutdown</action-type>

               <variables />

               <options>

                <option name="StopProcessingTemplateIfActionFails">false</option>

               </options>

               <parameters>

                <usepeer>True</usepeer>

                <usepref>True</usepref>

                <usesource>True</usesource>

                <type>reboot</type>

                <TimeOut>0</TimeOut>

               </parameters>

              </action>

            • 3. Re: Provisioning templates failing after using reboot commands
              Apprentice

              Hi Gru,

               

              create a new prov template.

               

              Wait 10s

              1st Reboot is a Reboot

              2nd Reboot is a Shutdown

               

              This Template will not damage a Client.  (hopefully)

               

              Try it an check...  Is there an Issue with your existing template, the Coreserver, the Client, or the something else

               

              In case this Template will work fine...  Add existing steps from your other template to this.

               

              Is easy in 9.6...  open both templates and copy and past from one template to the other

              • 4. Re: Provisioning templates failing after using reboot commands
                1EarEngineer Specialist

                Sorry for the delay. Holidays and all.

                New template created, it worked 1/4 times. There doesn't seem to be any particular reason as to when or why this happens, but we seem to experience this on any template that has a wait or reboot action in this.

                 

                I've reached out to support and the only thing I was able to get was to ensure our core isn't under load when this is happening, which it hasn't been. Until then, we've just been telling our guys to kick off the template again or if that doesn't work, go manual.

                • 5. Re: Provisioning templates failing after using reboot commands
                  five(9)s.GmbH.Support.Account Apprentice

                  Hi Gru,

                   

                  meanwhile you can work with (more than one or two) Reboot Actions in Provisioning...?

                   

                  Any changes in your Environment?

                   

                  Any Feedback from LD Support...   Or Solutions?

                  Best Regards

                  • 6. Re: Provisioning templates failing after using reboot commands
                    phoffmann SupportEmployee

                    A couple of general things that may help.

                     

                    • Request the latest patches from LD support (I don't remember seeing any stand out stuff around Provisioning, but since you've not stated what patch level you're on, it could be SP2 vanilla, and lots happened since then) .

                     

                    • Enable debug-logging (yep, you can do so in WINPE as well) by adding / importing a .REG file for instance. That will give a fair bit more info. Steps on how to do so can be found here -- How to enable Xtrace Diagnostic Logging -- (see my comment at the bottom).

                     

                    • The debug-logging will also add more logging to the various Provisioning Handlers (each action has its own 'mini' handler that does the action) - all the logs should be in X:\Provisioning\ in WinPE if I'm not mistaken (I'm not awake yet).

                     

                    ... granted, there's nothing "profoundly special" around a reboot action, but it's possible that we capture something useful to throw at a dev to make sense of. Who knows - maybe you've got some weirdly ornery piece of hardware that just enjoys being difficult or what not .

                     

                    That should help the support folks & so on out ... and maybe the handler-log will give you a Windows error code to search for (there's a VERY strong likelihood of any error code in the handler log being from Windows in this scenario).

                     

                    Hope that helps.

                    • 7. Re: Provisioning templates failing after using reboot commands
                      1EarEngineer Specialist

                      appreciate the help phoffmann but we are now on our latest CP patch. I've been working with support on this since Feb, and so far no dice. Hoping when we upgrade to 2016 this all gets fixed.

                      • 8. Re: Provisioning templates failing after using reboot commands
                        phoffmann SupportEmployee

                        I don't think there's going to be much of a muchness between the most recent 9.6 code and 2016 ... certainly not really much around something relatively trivial as a shutdown command.

                         

                        Hmm - have you looked at your IIS logs out of curiousity? Provisioning is sort of rather closely intermarried with IIS and it's possible that you're getting LANDesk errors as a knock-on effect of something else. Shutdown/reboot doesn't really have much to it, so I'm surprised that ...

                         

                        Hmmm ... say ... you may want to enable debug logging (.REG file can be imported in WinPE) ... I'm wondering if your *ACTUAL* problem doesn't actually happen before the reboot (essentially "somewhere" between the machine doing its last boot into Provisioning & the reboot) and for some reason the error only manifests around / gets thrown at the reboot action.

                        - How to enable Xtrace Diagnostic Logging

                         

                        I've seen stuff like this usually with software packages installs giving us "weird" return codes / exit values (though usually the symptom is that the Provisioning Task goes to a "completed" state) ... potentially possible that we're seeing something similar, but related to a failure here - and that by dint of the reboot action being the last logged action, that's what getting the failure.

                         

                        Worth checking out potentially (rest easy - rather than having to read ALL logs, you're mainly interested in checking the return code of each provisioning action - so should be in the last few lines of each handler log). If we find a miscreant action, you can then see what it is & what it gets back with ... that'd make more sense (to me at any rate) than something as commonplace as a reboot action causing you & you alone grief.

                         

                        (As an aside - here's a provisioning Webinar I hosted around imaging - the presentation has a bunch of useful www-links in it):

                        - [Tech Brief On-Demand Webinar 2016] Provisioning with LANDESK Management Suite

                         

                        Hope that helps / makes sense?

                        • 9. Re: Provisioning templates failing after using reboot commands
                          1EarEngineer Specialist

                          phoffmann,

                          This is the wierd part. The task never shows as failed in LD. As you can see below, it fails on the machine, but just sits in Active state in the console. Note the failed task is expected, there were no additional software needed for this particular model.

                          Hung.png

                          • 10. Re: Provisioning templates failing after using reboot commands
                            Rookie

                            That screenshot looks all too familiar. I have decided to go back to HII with LDM 2016 and one of my test models did this exact thing. My template has HII as the second to last task then a final reboot. I would never see the computer report reboot successful, thus leaving the task in limbo.

                             

                            Turns out the NIC driver used was not an exact fit. It installed, allowed an internet connection, but the computer would not say it was connected to the internet leaving a yellow triangle on the NIC icon.

                             

                            I removed the bad driver from the HII pool and ensured the correct driver was available, rebuilt HII and replicated to servers, and then the template finished successfully.

                             

                            Hope this may help!

                            -Holden

                            • 11. Re: Provisioning templates failing after using reboot commands
                              1EarEngineer Specialist

                              thanks, but we are not using HII, but rather DISM and the Lenovo driver cabs. There are 2 problems I see right now, 1) the task picks up after the reboot and windows autlogins however it fails immediately. 2) The failure for whatever reason doesn't get sent back to the core and the core thinks the device is waiting to come back online when in reality, it's already come back online, ran the task and failed.

                               

                              To make it even more frustrating, if I then cancel the hung task, and run our new tasks that contains the exact same steps as what is listed after the reboot, it goes through without issue.

                              • 12. Re: Provisioning templates failing after using reboot commands
                                phoffmann SupportEmployee

                                That's why I suggested that you enable full on debug-logging & see what's going on in the logs. If in doubt, don't trust what gets sent to the Core & check individual return codes (NIC drivers being one fine example of recurring shenanigan-causes). If "stuff goes wrong" there WILL be (or so far - always has been) a trace of it in the logs.

                                 

                                By knowing what ACTION is causing it, you can at least narrow the sucker down & focus that one down (may involve talking to our support / getting specific debug-code written from dev potentially), but at least you can check against a few instances & hopefully find that it's a "consistent misbehaviour on the same action" (in the cases WHERE it misbehaves).

                                 

                                {Also - grab the presentation that you can download from here - [Tech Brief On-Demand Webinar 2016] Provisioning with LANDESK Management Suite - I've covered a few useful bits of troubleshooting there, including the "do not delete folder" option }.

                                 

                                =============

                                 

                                Another thought is ... maybe there's a problem with the template itself (rather than "an action")? The sort I'm thinking here is that either due to "template getting upgraded over LD versions" or "your DB back-end having had a hiccup" a "something bad" happened to the template itself & it'd not be something that'd be visible without trawling through the template in XML form.

                                 

                                A - less painful, I find - way to check on that possibility would be to create a "fresh copy" of the template (I'm not suggesting you do it yourself, bribe the intern with the promise of a cup of coffee or so?) from the ground up, using the exact same actions / packages & so on. If that WORKS, then the problem isn't with your actions (big sigh of relief) but "something" that's gone bad with the template itself (at which point I usually strongly advise SQL admins to run DBCC / check in whether there's a maintenance plan set up in the first place, and so on).

                                 

                                Would that be a possibility?

                                 

                                I'm not throwing more work in your direction in an attempt to keep you busy. This stuff does happen (back-end stuff in the DB can break) and is a pain to figure out / nail down. I'm just getting suspicious if you've got "another template" (if I understood correctly) that does the exact same steps & that works fine. It's not something I suggest doing lightly, but I think it'd be worth a try ...?

                                 

                                Hoep that helps.

                                • 13. Re: Provisioning templates failing after using reboot commands
                                  JoeDrwiega SupportEmployee

                                  Have you tried running a reboot after installing your agent task but before installing software? Just a thought also what are your reboot settings for your agent that is in that task?

                                  • 14. Re: Provisioning templates failing after using reboot commands
                                    five(9)s.GmbH.Support.Account Apprentice

                                    Hi Paul,

                                     

                                    until we have this issue in at least five customer installations it seems to be a LANDESK issue. I have the problem at one of my customers where we hade a side-by-side migration to LDMS 2016 (no DB migration) recreating every single provisioning template by hand.

                                    Even Markus set up a fresh new core with a new template to reproduce the issue and it occurred there, too.

                                     

                                    Best regards,

                                    Torsten

                                    1 2 3 4 Previous Next