What version are you on? Of course 8.7 but what Service Pack. Do you have SP4?
After applying SP4 did you redeploy your PXE reps or are you using the older version of the PXE rep?
SP4, and yes, I did redeploy my PXE reps. Landesk is looking into this now, since if I remove my software deploy component template completely, it works. Yet all of the software was installing successfully before it failed w\ the error at the end.
I too am experiencing this error.
I am also on LDMS 8.7 SP4 and have also redeployed PXE reps. This was actually working until a couple of days ago. Since then, my template gets to a reboot task and then gets the Call to the web service failed message. The Ldprovision.log on the client shows the same error described above in line 685.
To make this problem even more complex, it actually began to work without the errors late yesterday afternoon. I tested again this morning, and the problem was back.
Has anyone experiencing anything resolved this issue yet?
No, I haven't figured it out yet. I rebuilt the final template, and it seemed to be working fine, but then it stopped again. Landesk has an open ticket on this, but its been since Thrusday of last week with no results yet. We're getting pretty frustrated.
I am experiencing the same problem and can share your frustrations.
We are using v8.7 SP4 and as you can see from the attached ldProvision.log encounter the "file=.\ProvisioningWebSvc.cpp, line=685" error. This stalls the provisioning scripts at different stages and does not report the error through the Provisioning History GUI. The problem is intermittent, often scripts process without encountering this issue and at other times I can lose 90% of my deployment set.
We have an incident logged with LANDesk and have been asked to produce verbose logs of the problem by launching ldProvision.exe manually with the -V 255 argument. Unfortunately I have not recreated the problem using this method perhaps because I have only been working on one PC at a time. I am awaiting further suggestions from LANDesk.
In the interim does anyone have an update to this issue and/or know how to enable verbose logging for all provisioning tasks?
ldProvision.log 1.7 K
Landesk has ALL of my logs, i.e IIS, Landesk related, etc. They can't duplicate this. I suspect it might be related to particular models of machines, but I'm not sure. And it could just be the way our server was setup. Several weeks now, though, with no working provisioning. I'm beginning to move towards cutting my losses and switching to something else for imaging.
Out of curiousity - can you post the case # you have open with us? I'll see if I have a few minutes free to glance it over, maybe I can spot something.
As for this one - if you're failing on the last step, there's a few things you can do to eliminate / narrow things down.
1 - Set up a clean Test-Core (VMWare or something) - this is just so that you're not working with "environmental problems". Ideally, this should be NOT connected to your domain / corporate network, so as not to be affected by GPO's and such things.
2 - To begin with, create a simple Provisioning script. Doesn't need to image, just something like "create a partition" and then reboot.
3 - Observe if you have the problem. If the problem is centered around the "restart"-function again, and you've used the same hardware, it's likely that it's a hardware issue.
4 - Repeat steps #2 and #3 with a virtual client ... if things go smooth here, then again, this is most likely a hardware specific issue. If you bump into the problem again, we should be able to duplicate the problem if you can provide us your virtual environment (VMWare / VirtualPC / whatever).
IF the problem IS centred around your hardware, then most likely you'll need to send it in to us, so that we can reproduce and debug this locally with our engineering group. I have seen in the past issues where a piece of hardware would refuse the "normal" restart-command, though this is going back to DOS-days. Since Provisioning is PE-based, I cannot provide you with the alternative "restart.exe" I've used for such cases, since "what applies to DOS doth not apply to PE" (at least as far as executables are concerned).
I hope this helps?
LANDesk EMEA Technical Lead.
Ticket # is109231. The failure occurs at the last step, regardless of what that step was. It can be a reboot, a call to launch an executable, etc. Most frustrating part is that the step that occured immediately before the failure always succeeds. This is occuring during regular old windows, after the imaging/reboot/mini-setup, so I could probably use a reboot command in a script at the end, but since the failure occurs immediately after the last step...
In the ldProvision.log I noticed you are getting "Caught exception in main." It seems that I've seen this when running a task many times or having multiple tasks set up for the same machine. Try clearing the target machine out of all provisioning tasks (if you haven't already). In fact, if you can, just delete all the provisioning tasks you have set up, just to be sure. Then do an iisreset. Then set up the task again. I've seen this fix the error sometimes. I am not quite sure how to duplicate it consistently. If you do figure that out, please post the steps.
I see this same issue in my provisioning tasks recently, and have a temporary workaround until Landesk is able to see what it is.
Same issue as you, i get the error in my "Post-OS Installation" where the last task is a reboot. I'm using nested templates, and it sounds like you are too.
What worked for me was to add a "wait" command just after the reboot, and un-mark the option for "stop processing the template if this action fails." Set the wait to 1 second.
When my image comes back up into windows after the reboot (well, reboot + mini-setup), it shows a failure for the Wait command and continues on from there.
Seems that its only throwing the "caught exception in main" in WinPE.
Hope this works for you
I'll definitely try your suggestion. In the meantime, I've discovered it only happens w\ Optiplex 755s, at least for us. What model of machine are you using?
Pretty standard Dell show. I have HII working in Provisioning with
I feel obligated to post my provisioning script later, when its all scrubbed
Does the error occur w\ all of your models?
Oh sorry, yes it does.
And it happend out of the blue one day, after i modified a "post os install" template