3 Replies Latest reply on Mar 31, 2009 3:07 PM by jan.buelens

    Provisioning Templates can not be loaded




      i got a problem with provisioning templates. When i start a machine and boot into Win PE Provisioning and then choose a template

      it always retries to load the template for 40 times but does not start it. When i look into my console on the server there is an scheduled task

      with the status waiting but it doesn't work. In the ldprovision log i get these messages:


      "STARTUP ProvisioningService ERROR 25.03.2009 07:55:37 Logging started
      STARTUP TemplateFinder ERROR 25.03.2009 07:55:37 Logging started
      STARTUP TemplateFinder ERROR 25.03.2009 07:55:37 Logging started
      ERROR TemplateFinder  25.03.2009 07:55:37  : couldn't find task for computer 308
      ERROR ProvisioningService  25.03.2009 07:55:37  : Unable to find template for computer IDN 308"


      If you create a scheduled task manually from the template and start it with an machine inside, it fails without putting the device

      in the status delayed.


      Has anybody an idea how i can solve the problem?

      Could it be a problem with a license?



      Thanking you in anticipation.



      Best regards,


        • 1. Re: Provisioning Templates can not be loaded
          bnelson Employee

          Sounds like you have the machine already in the pending mode for another provisioning script to run. Make sure there are no templates slated to run on that machine and then try it again.

          • 2. Re: Provisioning Templates can not be loaded
            pk Employee

            I doubt it's a problem with a license.  From your description, your manually selecting to boot into WinPE provisioning?  That's fine, but if things are working properly and you have the machine targeted for a provisioning job it should automatically boot into provisioning after you select to PXE boot.


            Regardless, if it's having trouble finding the machine in the DB, you could try deleting it's current entry and manually adding it back in (name and MAC address) under Configuration --> Bare Metal Server.

            • 3. Re: Provisioning Templates can not be loaded

              I've had this behaviour when there was something wrong with the template. I had software distribution actions in the System Configuration section of my template. The package definitions pointed to a path that no longer existed. The provisioning agent counted up to 40 retries and then said it couldn't load the template - not exactly brilliant in terms of error handling. I was able to run other templates so I knew it had to be something specific with my template. By a process of elimination, I determined that it was the software distribution that caused the problem. Fixed the package source and my template worked again.


              If this behaviour can be caused by a problem with a software distribution action, then maybe, other problems with individual actions (such as inject script and the script no longer exists) can cause similar behaviour. Try a really trivial template to build up your confidence again. If that works, eliminate actions from the template you're trying to get to work until the template loads...