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.
Error: 0x800701E7
Cause: Unknown.
Fix: Restart with boot CD or PXE.
Error: 0×80070032
Cause: No file system
Fix: Using command support, format (quick) the disk or recreate the disk using diskpart.exe
Error: 0×80070490
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
Error: 0×80070241
Cause: Error during TS user interface caused in memory
Fix: Restart with boot CD or PXE.
Error: 0x80072EE7
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.
#1 by zx9hippo on May 10, 2011 - 1:56 pm
0×80070490 = 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.
#2 by Nicolas Moseley on May 10, 2011 - 1:58 pm
Thanks for sharing!
#3 by Karl on October 20, 2011 - 9:34 am
0×80070570= Corrupted wim file
#4 by Nicolas Moseley on October 20, 2011 - 9:58 am
Thanks for sharing Karl!
#5 by AJ on February 14, 2012 - 4:52 am
HI, i get a task sequence error (0×80070643) when runing a program from a list of advertised programs. can u please assist..
#6 by Nicolas Moseley on February 14, 2012 - 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
#7 by Barry Duncan on October 14, 2012 - 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.
#8 by N. Moseley on October 14, 2012 - 7:28 am
Great thank you for sharing the info!
#9 by Aravind on October 8, 2012 - 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.
#10 by N. Moseley on October 8, 2012 - 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.