I am having a similar issue with provisioning in LDMS 9.0SP2
My error is the same but it is not related to the creation of a directory
The provisioning proses fails on a distribution of software, but its randomly. Never the same software distribution.
I put my error below.
2010-12-23 13:43:47(2776-2780) ldProvision.exe:Could not find tag response
2010-12-23 13:43:47(2776-2780) ldProvision.exe:Caught exception in main: code=80001802H, file=..\shared\src\LDProvisionResponse.cpp, line=279
2010-12-23 13:43:47(2776-2780) ldProvision.exe:Call web service GetStatusString()
2010-12-23 13:43:47(2776-2780) ldProvision.exe:Create process (C:\Program Files\LANDesk\Shared Files\httpclient.exe) with args ( -H"C:\ldprovisioning\header.txt" -o"C:\ldprovisioning\body.txt" -f"C:\ldprovisioning\result.xml" http://SRVSVCMGMTE01/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx)
2010-12-23 13:43:47(2776-2780) ldProvision.exe:start TryallWebService No=0.
2010-12-23 13:43:47(2776-2780) ldProvision.exe:end TryallWebService No=0.exitCode=0
2010-12-23 13:43:48(2776-2780) ldProvision.exe:Call web service SetActionStatus()
2010-12-23 13:43:48(2776-2780) ldProvision.exe:Create process (C:\Program Files\LANDesk\Shared Files\httpclient.exe) with args ( -H"C:\ldprovisioning\header.txt" -o"C:\ldprovisioning\body.txt" -f"C:\ldprovisioning\result.xml" http://SRVSVCMGMTE01/LANDesk/ManagementSuite/Core/ProvisioningWebService/WebService.asmx)
2010-12-23 13:43:48(2776-2780) ldProvision.exe:start TryallWebService No=0.
2010-12-23 13:43:48(2776-2780) ldProvision.exe:end TryallWebService No=0.exitCode=0
I think I am having a similar problem.
I'll see what I can find out in the logs.
Come on LANDesk Support. You don't want us to call you unless its "urgent", but you don't chime in when your users specifiy a specific problem that needs addressing!
How about some help here!!!
Suggested workaround until this problem is resolved:
Instead of using a 'delete file' or 'create directory' action..
Use an 'execute action' to use cmd and create the directory and delete the file through the command prompt.
/c md c:\tmp
/c del c:\tmp\file.txt
OK, now that I am past THAT problem, the provisioning fails on ANOTHER step that was working before SP2!!! This time installing a software package. No matter what one I put first after all the OS stuff it fails. Error 8000002H. A system error occurred.
See attached logs from the agent and core.
Is it just me, or should a service pack NOT totally destroy what used to be a working process?
In the last 2 work weeks I have deployed over 20 windows 7, de installation of windows 7 is never a problem but installing de needed software in the “system configuration” section fails in 95% of the cases and always with the error log pasted below.
De software distribution action in progress is always successfully installed and then I get the error, making the template quit and the installation unfinished.
Mostly it is not the same software distribution, sometimes in the beginning of the system configuration section sometimes at the very end. ( about 20 software packages need to be installed ). I have tried different templates, some with very few “system configuration” actions but almost always it fails somewhere and always on the line 279.
I am running out of ideas and found nothing on the forums.
I their someone who can point me in the right direction?
Where do I need to look?
Provisioning is one of the main reasons why we purchased LANDesk 1 year ago, and I cannot get it to work.
LANDesk version 9 SP2.
2011-01-05 13:20:33(3884-3888) ldProvision.exe:Could not find tag response
2011-01-05 13:20:33(3884-3888) ldProvision.exe:Caught exception in main: code=80001802H, file=..\shared\src\LDProvisionResponse.cpp, line=279
Actually, what I have also found is ANOTHER bug that I don't think is noted in these discussions.
It turns out that SP2 also broke the ability to use dependent packages - you will have to break them apart into separate items in your templates for them to work. This is not the same problem that they have a hotfix for (that fixes another problem where packages with other dependent packages would not show up as selectable when trying to choose a package).
This one was hard to track down since when the template got to the item for the package with dependencies, it would not log anything about that package. Nada. It would seemingly just skip over it, and sometimes hangs the template all together.
Also, I had to add an extra restart into the template, right before the first package in order for that first package not to fail.
So, overall, even after applying the 3 post-SP2 provisioning patches they have so far (that I know of), I personally have had to work around 3 distinct and critical bugs introduced by SP2.
I brought this to the attention of LANDesk already (phone call), but silence back. Probably inundated with all the problems they've created...
For Steve Lyon,
I wanted to let you know that we have duplicated the bug you mentioned for the Dependant packages and are working with Engineering on that issue.
Additionally, the issue of the tasks running without installing anything is related to the taskqueue process which Provisioning uses with SDClient. If sdclient or vulscan are running, and provisioning attempts to run a SWD action, nothing will get installed at that moment, because it queues the package to run after SDclient or Vulscan finish. At that point Provisioning will move to the next step and try to run the next SWD task which will also get queued.
These Queued status's come back as successful even though they have not yet completed. To keep this from happening and backing up. when doing an End-to-End provisioning task, you can modify the agent being installed to eb a "light" provisioning agent. This will Install the agent but will Delay SDClient or Vulscan from Running before your Software Distribution tasks kick off. To configure a "Light" Provisioning agent see the following article:
Otherwise, I have updated any additional comments in our open case.