Environment:
LDMS - 9.x versions
Description:
In a Provisioning template, you added an action "Inject Script" in order to add the Unattend.xml file and you get an error message in the injectscripthandler.exe.log file telling (cf. article How to troubleshoot Provisioning Template Action Handlers to get this log);
2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:CreateHeaderFile - X:\ldprovision\setupinstall.header.txt
2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:CreateBodyFile - X:\ldprovision\setupinstall.body.txt
2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:Args = -V -H"X:\ldprovision\setupinstall.header.txt" -o"X:\ldprovision\setupinstall.body.txt" -f"X:\ldprovision\setupinstall.result.xml" http:/myserver/landesk/managementsuite/core/ProvisioningWebService/WebService.asmx
2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:going to call x:\cba8\httpclient.exe -V -H"X:\ldprovision\setupinstall.header.txt" -o"X:\ldprovision\setupinstall.body.txt" -f"X:\ldprovision\setupinstall.result.xml"http://myserver/landesk/managementsuite/core/ProvisioningWebService/WebService.asmx
2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:start Try httpclient No=0.
2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:end Try httpclient No=0.exitCode=0
2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:Exit Code of InstallCallHTTPClient = 0
2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:FindElement returned 0, value is false
2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:invalid result
2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:FindElement returned 0
2013-06-13 18:07:28(1072-1044) InjectScriptHandler.exe:An internal error has occurred with the management product
Solutions:
1- Double-Check if the Variables of the unattend.xml are correct (Tip: Try to replace the variables by some real values to isolate the issue first)
2- It may be due to some permissions on LDLOGON folder on the Core Server, then follow these instructions;
a - Add the "Network Service" account to the LDLOGON folder permissions with Full Control and propogate the rights to all subfolders.
b - Add the "Network Service" account to the LDLOGON share with Full Control.
c - Restart IIS on the Core Server.
d - Retry the OS deployment