Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, December 11, 2013 11:06 PM
I have a client that all their OSD Task Sequences keep failing at the Applying Operating System step. All the errors don't lead to anything for trouble shooting. I have included the SMSTS.log with the section were the Applying Operating systems starts. It never starts to download the image .wim file. I have checked permissions on the Network Access account and they are setup correctly.
The following error messages stick out and not sure what they are:
Invalid command line argument: /runfromnet
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,756) TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Task Sequence Engine failed! Code: enExecutionFail TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Task sequence execution failed with error code 80004005 TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Expand a string: OSDApplyOS.exe /image:KFC00069,%OSDImageIndex% /target:C: /runfromnet:False TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Expand a string: TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Command line for extension .exe is "%1" %* TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Set command line: OSDApplyOS.exe /image:KFC00069,%OSDImageIndex% /target:C: /runfromnet:False TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Start executing the command line: OSDApplyOS.exe /image:KFC00069,%OSDImageIndex% /target:C: /runfromnet:False TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
!! TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Expand a string: WinPE TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Executing command line: OSDApplyOS.exe /image:KFC00069,%OSDImageIndex% /target:C: /runfromnet:False TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Command line for extension .exe is "%1" %* ApplyOperatingSystem 11/21/2013 10:47:16 AM 1772 (0x06EC)
Set command line: "OSDApplyOS.exe" /image:KFC00069,1 /target:C: /runfromnet:False ApplyOperatingSystem 11/21/2013 10:47:16 AM 1772 (0x06EC)
FALSE, HRESULT=80070057 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,272) ApplyOperatingSystem 11/21/2013 10:47:16 AM 1772 (0x06EC)
Invalid command line argument: /runfromnet ApplyOperatingSystem 11/21/2013 10:47:16 AM 1772 (0x06EC)
ParseCommandLine(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,409) ApplyOperatingSystem 11/21/2013 10:47:16 AM 1772 (0x06EC)
Process completed with exit code 2147942487 TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
!! TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Failed to run the action: Apply Operating System. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
MP server http://server.domain.com . Ports 80,443. CRL=false. TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Setting authenticator TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Set authenticator in transport TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Sending StatusMessage TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Setting message signatures. TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Setting the authenticator. TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
CLibSMSMessageWinHttpTransport::Send: URL: US-BDDC-SCCM.keystone.KFC:80 CCM_POST /ccm_system/request TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Request was succesful. TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Set a global environment variable _SMSTSLastActionRetCode=-2147024809 TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Clear local default environment TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Let the parent group (Build the Reference Machine) decides whether to continue execution TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
The execution of the group (Build the Reference Machine) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Failed to run the last action: Apply Operating System. Execution of task sequence failed.
The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
MP server http://server.domain.com. Ports 80,443. CRL=false. TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Setting authenticator TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Set authenticator in transport TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Sending StatusMessage TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Setting message signatures. TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Setting the authenticator. TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
CLibSMSMessageWinHttpTransport::Send: URL: US-BDDC-SCCM.keystone.KFC:80 CCM_POST /ccm_system/request TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Request was succesful. TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 11/21/2013 10:48:05 AM 752 (0x02F0)
The command completed successfully. TSBootShell 11/21/2013 10:48:05 AM 752 (0x02F0)
Successfully launched command shell. TSBootShell 11/21/2013 10:48:05 AM 752 (0x02F0)
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,756) TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Task Sequence Engine failed! Code: enExecutionFail TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
**************************************************************************** TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Task sequence execution failed with error code 80004005 TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Cleaning Up. TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Removing Authenticator TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1614) TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Cleaning up task sequence folder TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Unable to delete file C:\SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218) TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Failed to delete directory 'C:\SMSTaskSequence' TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,518) TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Successfully unregistered Task Sequencing Environment COM Interface. TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Command line for extension .exe is "%1" %* TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
==========[ TsProgressUI started in process 1092 ]========== TsProgressUI 11/21/2013 11:02:16 AM 1028 (0x0404)
Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister TsProgressUI 11/21/2013 11:02:16 AM 1028 (0x0404)
Unregistering COM classes TsProgressUI 11/21/2013 11:02:16 AM 1028 (0x0404)
Unregistering class objects TsProgressUI 11/21/2013 11:02:16 AM 1028 (0x0404)
Shutdown complete. TsProgressUI 11/21/2013 11:02:16 AM 1028 (0x0404)
Process completed with exit code 0 TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Successfully unregistered TS Progress UI. TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
g_TSManager.Run(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,641) TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005 TSManager 11/21/2013 11:02:16 AM 1384 (0x0568)
Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.
All replies (8)
Friday, December 13, 2013 1:44 AM âś…Answered
My bet is that they are using boot images with older version of the client tools in them -- like 2007.
Jason | http://blog.configmgrftw.com
Thursday, December 12, 2013 12:39 AM
what's your task sequence look like and how are you deploying? from media, pxe, or deployment?
Thursday, December 12, 2013 2:14 PM
Also, what is the target OS?
Did they recently install SP1 or R2?
Have you tried recreating their boot images?
Jason | http://blog.configmgrftw.com
Thursday, December 12, 2013 5:00 PM
It is every task sequence. I created a basic image deployment task sequence just to test. This is from PXE.
Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.
Thursday, December 12, 2013 5:02 PM
Jason,
Windows 7 Enterprise x64. They are still on SP1 CU2. However, they have had this problem since RTM according to the guys I am talking to.
I haven't tried to recreate the boot images yet. I will have them do that today.
Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.
Thursday, December 12, 2013 11:33 PM
Just comparing two different log files from a successful image deployment in another environment and this client's environment I see this is where the issues start:
On the successful deployment after Set command line: "OSDApplyOS.exse"...... it continues. At this client every task sequence issues seems to start at that point with the following main error:
FALSE, HRESULT=80070057 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,272) ApplyOperatingSystem 11/21/2013 10:47:16 AM 1772 (0x06EC)
Here is some more of that sections errors:
!! TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Expand a string: WinPE TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Executing command line: OSDApplyOS.exe /image:KFC00069,%OSDImageIndex% /target:C: /runfromnet:False TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Command line for extension .exe is "%1" %* ApplyOperatingSystem 11/21/2013 10:47:16 AM 1772 (0x06EC)
Set command line: "OSDApplyOS.exe" /image:KFC00069,1 /target:C: /runfromnet:False ApplyOperatingSystem 11/21/2013 10:47:16 AM 1772 (0x06EC)
FALSE, HRESULT=80070057 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,272) ApplyOperatingSystem 11/21/2013 10:47:16 AM 1772 (0x06EC)
Invalid command line argument: /runfromnet ApplyOperatingSystem 11/21/2013 10:47:16 AM 1772 (0x06EC)
ParseCommandLine(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,409) ApplyOperatingSystem 11/21/2013 10:47:16 AM 1772 (0x06EC)
Process completed with exit code 2147942487 TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
!! TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Failed to run the action: Apply Operating System. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 11/21/2013 10:47:16 AM 1384 (0x0568)
Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.
Tuesday, January 7, 2014 4:11 PM
What should the Image version be with SP1?
6.2.9200.16384?
Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.
Friday, January 10, 2014 7:30 PM
Thanks Jason. I was finally able to have the client rebuild their boot images. Looks good now.
Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.