1 2 Previous Next 27 Replies Latest reply on Feb 15, 2013 1:32 PM by mbaney

    Deploy action fails in provisioning

    Apprentice

      I have a situation where the deploy action in my provisioning script fails. This started all of the sudden and now i can't seem to deploy any images anymore.

       

      I have tried fault finding this as much as possible. When it fails i then manually enter the commands in from the command prompt using the \\server\ldmain osd directory and it works perfectly copying the exact command in the provisioning script. The only difference i can see is inside the provisioning script the XML shows the images.exe app running from the c:\ldprovision directory.

       

      What i don't get is that win pe has an x:\ not a c:\ so i wonder if this is part of my problem. I have tried to substitute this in different ways but i still get a fail. No matter how I attempt this it fails.

       

      My staff have spent many hours on the phone to LANDESK support and can not get to the bottom of the problem. I am now doing more in depth analysis and still coming up with blanks. Every other command seems to run perfectly fine. I am sure the drives are mapped, the permissions are correct (well atleast i assume so as i can run it from cmd).

       

      I am at a bit of a lost end here now. It nearly appears as those imagew.exe inside winpe and my image are not compatible? I have recaptured the machine to rule this out but same issue.

       

      I am using a brand new out of the box 9.5 install.

       

      Ideas would be appreciated

        • 1. Re: Deploy action fails in provisioning
          Frank Wils ITSMMVPGroup

          Can you post a screenshot of the Deploy Action in Provisioning and the x:\ldprovision\ldprovision.log file?

           

          Frank

          • 2. Re: Deploy action fails in provisioning
            Apprentice

            2013-01-12 14:24:08(904-896) ldProvision:*********  Begin an action - Deploy_image

            2013-01-12 14:24:09(904-896) ldProvision:Do EnvironmentCheck

            2013-01-12 14:24:09(904-896) ldProvision:Is WinPE Action=1, Is WinPe Environment=1

            2013-01-12 14:24:09(904-896) ldProvision:Report might reboot status to core.

            2013-01-12 14:24:09(904-896) ldProvision:Call web service SetActionStatus()

            2013-01-12 14:24:09(904-896) ldProvision:Start TryallWebService Attempt:0.

            2013-01-12 14:24:09(904-896) ldProvision:End TryallWebService Attempt:0. ExitCode:0

            2013-01-12 14:24:09(904-896) ldProvision:Session Data: <variables/>

            2013-01-12 14:24:09(904-896) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\DeployImageHandler.exe" http://SPANNER/LdLogon/Provisioning/windows/DeployImageHandler.exe)

            2013-01-12 14:24:09(904-896) ldProvision:Process exit code:0

            2013-01-12 14:24:09(904-896) ldProvision:The file (X:\ldprovision\DeployImageHandler.exe) was successfully downloaded

            2013-01-12 14:24:09(904-896) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\DownloadHandler.exe" http://SPANNER/ldlogon/provisioning/windows/DownloadHandler.exe)

            2013-01-12 14:24:09(904-896) ldProvision:Process exit code:0

            2013-01-12 14:24:09(904-896) ldProvision:The file (X:\ldprovision\DownloadHandler.exe) was successfully downloaded

            2013-01-12 14:24:09(904-896) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\MaptoPreferredHandler.exe" http://SPANNER/ldlogon/provisioning/windows/MaptoPreferredHandler.exe)

            2013-01-12 14:24:09(904-896) ldProvision:Process exit code:0

            2013-01-12 14:24:09(904-896) ldProvision:The file (X:\ldprovision\MaptoPreferredHandler.exe) was successfully downloaded

            2013-01-12 14:24:09(904-896) ldProvision:Download handler ok.

            2013-01-12 14:24:09(904-896) ldProvision:Launching action handler [DeployImageHandler.exe] with parameters ["]

            2013-01-12 14:24:09(904-896) ldProvision:handler launched.

            2013-01-12 14:24:14(904-896) ldProvision:Reporting action status: 5 to core

            2013-01-12 14:24:14(904-896) ldProvision:Call web service GetStatusString()

            2013-01-12 14:24:14(904-896) ldProvision:Start TryallWebService Attempt:0.

            2013-01-12 14:24:15(904-896) ldProvision:End TryallWebService Attempt:0. ExitCode:0

            2013-01-12 14:24:15(904-896) ldProvision:StatusString = The action failed.

            2013-01-12 14:24:15(904-896) ldProvision:Call web service SetActionStatus()

            2013-01-12 14:24:15(904-896) ldProvision:Start TryallWebService Attempt:0.

            2013-01-12 14:24:19(904-896) ldProvision:End TryallWebService Attempt:0. ExitCode:0

            2013-01-12 14:24:19(904-896) ldProvision:End of action - Deploy_image

            2013-01-12 14:24:19(904-896) ldProvision:Last action failed

            2013-01-12 14:24:19(904-896) ldProvision:**********************************  End processing actions  **********************************

            2013-01-12 14:24:19(904-896) ldProvision:ldProvision ended

             

            The relevant bits....

            • 3. Re: Deploy action fails in provisioning
              Apprentice

              Hi everyone, i thought i would post a solution here.

               

              I came into work early and managed to get onto one of the osd specialists, thanks Roy.

               

              It turns out my provisioning scripts from earlier version of LMS 9.0 started to play up after SP3 because of the introduction of preferred servers. Basically, I wasnt using preferred servers, I was mapping drives, and then OSD wanted to map the mapped drives which didnt work....

               

              THe solution was to add preferred servers, delete any manually mapped drives and let the new and improved osd do more work. It simplfies things, just complicated it in the first instance.

               

              Anyway, thanks Roy, your a champ.. Issue sorted. I thought it may be useful to others to not get caught in the same trap.

              • 4. Re: Deploy action fails in provisioning
                Rookie

                It works for me too, thanks for this solution. Don't use mapped network, landesk can't lauch the imagew in LM9.5

                • 5. Re: Deploy action fails in provisioning
                  mbaney Apprentice

                  Hi,

                   

                  I am having the exact same issue.  I upgraded to 9.5 and now provisioning will not work.  I removed the network mapping action from the provisioning template but am having the same error as above.  I believe I have setup the preferred correctly – I have set the server name, read-only credentials and tested them with UNC and HTTP (it says it can’t validate the credentials because the server allows anonymous, so I assume this OK).  I also specified an IP address range.  Since I only have 1 server (core) I didn’t setup any replication, sources, or write credentials.  Any ideas of what else I am doing wrong?  Below is my ldprovision.log as well as a screen shot of my install template.

                   

                  Thanks,

                  Brad

                   

                  template.png

                   

                  2013-02-06 01:16:43(1820-1824) ldProvision:*********  Begin an action - Deploy_image

                  2013-02-06 01:16:43(1820-1824) ldProvision:Do EnvironmentCheck

                  2013-02-06 01:16:43(1820-1824) ldProvision:Is WinPE Action=1, Is WinPe Environment=1

                  2013-02-06 01:16:43(1820-1824) ldProvision:Report might reboot status to core.

                  2013-02-06 01:16:43(1820-1824) ldProvision:Call web service SetActionStatus()

                  2013-02-06 01:16:43(1820-1824) ldProvision:Start TryallWebService Attempt:0.

                  2013-02-06 01:16:43(1820-1824) ldProvision:End TryallWebService Attempt:0. ExitCode:0

                  2013-02-06 01:16:43(1820-1824) ldProvision:Session Data: <variables/>

                  2013-02-06 01:16:43(1820-1824) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\DeployImageHandler.exe" http://LANDESK00/LdLogon/Provisioning/windows/DeployImageHandler.exe)

                  2013-02-06 01:16:43(1820-1824) ldProvision:Process exit code:0

                  2013-02-06 01:16:43(1820-1824) ldProvision:The file (X:\ldprovision\DeployImageHandler.exe) was successfully downloaded

                  2013-02-06 01:16:43(1820-1824) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\DownloadHandler.exe" http://LANDESK00/ldlogon/provisioning/windows/DownloadHandler.exe)

                  2013-02-06 01:16:43(1820-1824) ldProvision:Process exit code:0

                  2013-02-06 01:16:43(1820-1824) ldProvision:The file (X:\ldprovision\DownloadHandler.exe) was successfully downloaded

                  2013-02-06 01:16:43(1820-1824) ldProvision:Create process (x:\cba8\httpclient.exe) with args (  -f "X:\ldprovision\MaptoPreferredHandler.exe" http://LANDESK00/ldlogon/provisioning/windows/MaptoPreferredHandler.exe)

                  2013-02-06 01:16:43(1820-1824) ldProvision:Process exit code:0

                  2013-02-06 01:16:43(1820-1824) ldProvision:The file (X:\ldprovision\MaptoPreferredHandler.exe) was successfully downloaded

                  2013-02-06 01:16:43(1820-1824) ldProvision:Download handler ok.

                  2013-02-06 01:16:43(1820-1824) ldProvision:Launching action handler [DeployImageHandler.exe] with parameters ["]

                  2013-02-06 01:16:43(1820-1824) ldProvision:handler launched.

                  2013-02-06 01:16:46(1820-1824) ldProvision:Reporting action status: 5 to core

                  2013-02-06 01:16:46(1820-1824) ldProvision:Call web service GetStatusString()

                  2013-02-06 01:16:46(1820-1824) ldProvision:Start TryallWebService Attempt:0.

                  2013-02-06 01:16:46(1820-1824) ldProvision:End TryallWebService Attempt:0. ExitCode:0

                  2013-02-06 01:16:46(1820-1824) ldProvision:StatusString = The action failed.

                  2013-02-06 01:16:47(1820-1824) ldProvision:Call web service SetActionStatus()

                  2013-02-06 01:16:47(1820-1824) ldProvision:Start TryallWebService Attempt:0.

                  2013-02-06 01:16:48(1820-1824) ldProvision:End TryallWebService Attempt:0. ExitCode:0

                  2013-02-06 01:16:48(1820-1824) ldProvision:End of action - Deploy_image

                  2013-02-06 01:16:48(1820-1824) ldProvision:Last action failed

                  2013-02-06 01:16:48(1820-1824) ldProvision:**********************************  End processing actions  **********************************

                  2013-02-06 01:16:48(1820-1824) ldProvision:ldProvision ended

                  • 6. Re: Deploy action fails in provisioning
                    Apprentice

                    Hi Chef

                     

                    That looks like the same error I had.

                     

                    I need to add two preferred servers, one being the landesk server (the one which imagew.exe runs from) and the server the images are stored on.

                     

                    What was unusual to me (and I still dont understand why) but when we added the preferred servers the ip rangers we used were something very odd, there were starting 1.1.1.1 ending 1.1.1.2 . I have no idea why but this is what Roy told me to use and it works.

                     

                    Perhaps try this tip?

                    • 7. Re: Deploy action fails in provisioning
                      mbaney Apprentice

                      Hi Ryan,

                       

                      Thanks for the suggestion.  I just gave it a try and it didn’t seem to make a difference.  Did you configure any of the other stuff such as write credentials?  Perhaps I will try housing the images on another server.  For the second server, did you have to install IIS on it?  I am assuming it’s not a LANDesk server but a plan old file server.

                       

                      Thanks,

                      Brad

                      • 8. Re: Deploy action fails in provisioning
                        Apprentice

                        My Second server is just a fileserver using UNC, not IIS. Instead of using read only i used administrator priviledges... it just worked that way.

                         

                        From your logs it look like the drives are called and mapped successfully using X:\ldprovision\MaptoPreferredHandler.exe" . to me it looks like it is failing on the DeployImageHandler.

                         

                        So I am thinking the settings inside the Deploy Image may be your issue.

                         

                        My settings here are very simple. Point the UNC image file path to the \\server\directory\image.TBI (not to a mapped drive) Validate, (and then i remove the /x as i do not want it extend partitions on its own).

                        • 9. Re: Deploy action fails in provisioning
                          Apprentice

                          Maybe post your Deply Image Commad Screen Shot....

                          • 11. Re: Deploy action fails in provisioning
                            mbaney Apprentice

                            Does this look about the same as yours?

                            • 12. Re: Deploy action fails in provisioning
                              Rookie

                              Hi,

                              Same for me, please post your MaptoPreferredHandler.exe.log

                               

                              Regards

                              • 13. Re: Deploy action fails in provisioning
                                mbaney Apprentice

                                lddwnld.dll version is too old or missing.  Aboring download

                                could not map or unmap drive.  Error code: -1

                                • 14. Re: Deploy action fails in provisioning
                                  Rookie

                                  Did you look at the log of your upgrade if something wrong ?

                                   

                                  Try to copy lddwnld.dll from your sources installation to C:\Program Files (x86)\LANDesk\ManagementSuite\

                                  1 2 Previous Next