Appendix B - Troubleshooting
The OSD Toolkit is pretty easy to troubleshoot following the guidelines here:
Logging order
The following list is the order of logs to check:
If using iPXE, make sure that the iPXE WinPE Client succeeded by checking the 2PXiPXEWinPEClient.log in the X:\Windows\Temp directory.
Make sure that the BCEnabler.exe step was run and completed OK
For each package that is downloaded, the following order of logs are created/overwritten, please see Appendix D for successful log examples:
BITSACP_Startup.log is written to the directory where the TS logs to, in WinPE this is typically in X:\Windows\Temp\SMSTSLog\ folder.
Task Sequence does not use the ACP
When running a task sequence and you want to use the ACP, ensure the following:
If in WinPE, make sure that you have build the WinPE with the help of WinPEGen.exe
If not in WinPE, make sure that the BITSACP.EXE binary is present on the Windows computers running the Task Sequence.
If in WinPE, make sure that the ACP variable is set correctly, if it's not set, due to different paths in your TS, it's obvious as the smsts.log does not mention that its executing the TS ACP itself. If the TS ACP is called, it will have a line like this:
Using download program: BitsACP.exe
The full logging entry for a package should look as the following:
Trying https://someserver.your.biz/NOCERT_SMS_DP_SMSPKG$/CP100209.
Using download program: BitsACP.exe
BitsACP.exe X:\Windows\TEMP\SMSTSDownload.INI CP100209 C:\_SMSTaskSequence\Packages\CP100209
Command line for extension .exe is "%1" %*
Set command line: "BitsACP.exe" X:\Windows\TEMP\SMSTSDownload.INI CP100209 C:\_SMSTaskSequence\Packages\CP100209
Executing command line: "BitsACP.exe" X:\Windows\TEMP\SMSTSDownload.INI CP100209 C:\_SMSTaskSequence\Packages\CP100209
The next line is key, as that is the return code from the ACP:
Process completed with exit code 2147942421
The return code is in decimal, but convert it to hex, and the value is this: 80070015, the 8007 indicates that it’s a Windows return code of some sort, so remove that and convert back 15 from hex to dec (21). The console command "net helpmsg <nr>" will tell you what it really means:
In this case, there is also a logfile, called BITSACP_Startup, that contains the error itself and some more information:
So open up the log an it will have the following lines (as an example):
Command-line arguments:
BitsACP.exe BITS Pro Downloader
X:\Windows\TEMP\SMSTSDownload.INI
CP100209 BITS Pro Downloader
C:\_SMSTaskSequence\Packages\CP100209
Checking to see if we are running in WinPE.
Initializing COM...
Failed to Create BITS COM Object.
The error that it cannot Create a BITS COM object is due to the fact that the BCEnabler.exe Enable command is not executed before the ACP is run.
The following log applies in WinPE (This is mentioned in the guide above)
Run "BCEnabler.exe Enable" EACH TIME you enter WinPE
If you have a complicated TS, make sure that the ACP is set AFTER BCEnabler command line has run.
Before ending the WinPE session, and after the OS image is applied, make sure you run BCEnabler.exe to move the cache etc. into the full OS.
BITSACP fails to download package
This can happen for many reasons, but a typical one is that the Network Access Account is not set. This can be spotted in the main BITSACPSVC_<PackageID>.log file:
Connecting with path: /NOCERT_SMS_DP_SMSPKG$/AP200003
Successfully set QueryInterface on Download Job...
Connecting to server...
Trying to connect...
Server replies with Status: 401
The server requires authentication. Sending searcing credentials...
Trying NAC: _SMSTSReserved1-000
UserName:
Empty value for account
NAC is not valid, cannot authenticate, add valid NAC please:000
Returning: FALSE
Returned from GetPropFindXML
Failed to get HTTP XML Data with PROPFIND webdav request.
Last updated
