SCCM Task Sequence Error Codes & Fixes
When performing a bare-metal image install in SCCM, occasionally an error will occur that will halt the initiation of a task sequence. Below are a few errors I have experienced, which I have compiled with my own [brief] explanation and what to do to fix it. This post will be updated as I come across new errors, explanations, alternate fixes, etc.
Fix: Restart with boot CD or PXE.
Cause: No file system
Fix: Using command support, format (quick) the disk or recreate the disk using diskpart.exe
Cause: Failed to find driver for PCI\VEN device
Fix: Review SMSTS.log for driver info. Likely need to add the PCI\VEN into an .inf or txtsetup.oem file
Cause: Error during TS user interface caused in memory
Fix: Restart with boot CD or PXE.
Cause: IP address is not on a subnet that connect to the SCCM server
Fix: Change the port the Ethernet cable is connected on. Restart with boot CD or PXE.
18 thoughts on “SCCM Task Sequence Error Codes & Fixes”
May 10, 2011 at 1:56 pm
0x80070490 = also attributed to trying to use a WIM image that does not specify OS bit-depth support (32/64). a.k.a. – using wim image 1 of 2 instead of 2 of 2 as the OS image.
May 10, 2011 at 1:58 pm
Thanks for sharing!
October 20, 2011 at 9:34 am
0x80070570= Corrupted wim file
October 20, 2011 at 9:58 am
Thanks for sharing Karl!
February 14, 2012 at 4:52 am
HI, i get a task sequence error (0x80070643) when runing a program from a list of advertised programs. can u please assist..
February 14, 2012 at 8:01 am
AJ, thanks for the note. I recommend posing this question on a support forum as I’m unable to personally attend to the question in detail. Head on over to the good folks at MyITForum :-) http://www.myitforum.com/forums/System-Center-Configuration-Manager-2007-f144.aspx
October 14, 2012 at 4:15 am
I really hope they managed to solve this one for you, but I just ran across this one myself half way through a task seq. After chasing a bunch of spurious error codes, it turned out it wasn’t a task seq problem, but a specific package problem. I deleted the package from the DP (and then waited the obligatory half hour) then repushed it, and the error disappeared. I’ve never come across a corrupt package in SCCM 2007 before, but there you go. Problem solved.
October 14, 2012 at 7:28 am
Great thank you for sharing the info!
October 8, 2012 at 3:48 pm
how about this error code – (0x800703F8). I took a look at the smsts.log for this client but couldn’t find anything related to that.
October 8, 2012 at 5:23 pm
Thank you Aravind for the comments. Unfortunately I do not know that error code to assist. I recommend posing your question in the Microsoft forums or in MyITForum for further troubleshooting assistance.
March 25, 2014 at 12:33 am
Hi, I got the following after booting from PXE: An error occurred while retrieving policy for this computer (0x80072EFE). For more information, contact your system administrator ……
October 9, 2014 at 9:17 am
Here is my list of errors and usual fixes in my environment (IT for a school district):
0x80070002 Permissions or too many systems trying to pull at the same time > retry
0x80091007 Can indicate a bad stick of RAM > try swapping/replacing ram and restart
0x8004005 Cannot reach management Point > Check connectivity & date & time on system, if still no luck, be sure ip address (subnet) has a boundary assignment
0x80070070 Not enough disk space or faulty hdd
0x80070490 Unable to locate hdd> replace hdd
We have also found that when we attempt to image a group of systems (20-40 at a time), a few systems will throw odd error codes. These will usually not re-occur if you simply wait a few minutes and restart the Imaging process on those systems. We attribute this to bandwidth issues or over load on the DP.
October 9, 2014 at 9:09 pm
Thanks Val for sharing the extra tips!
November 7, 2014 at 3:11 am
Hello, i can add:
0x80070008 means “Not enough space is available to execute this command”; you have to add Memory
November 7, 2014 at 6:04 am
Thanks for the addition!
April 16, 2015 at 12:12 am
Can anyone tell the solution for error 0x80220001?
April 16, 2015 at 8:26 am
Doing a quick Internet search, there may be an error with your unattended.xml file used for the configuration. If you are using one, temporarily remove it from use in the deployment. Also, the tricky thing about using an unattended.xml file is that it must be in the root location of the package’s folder – and cannot be in a subfolder. So watch out for that.
August 18, 2015 at 2:39 am
Has anybody seen error code….0×0001E240