OSD Task Sequence Error: Unable to apply (0x80070035)

I recently created a new MDT 2010 Update 1 UDI task sequence, and it's been testing fine in my local SCCM site.  It seems to be failing when run on a child primary site and I'm not sure why.  The only difference I can think of is that users in the child primary site are in Beijing, so they'd be selecting the option to add the Chinese language pack, input locale, timezone, etc...

 

Here's a snip from the smsts.log:

 

Starting to apply image 1 from Win7Combined.wim to C:\	ApplyOperatingSystem	8/12/2010 12:20:44 AM	1924 (0x0784)
Wiping C:\	ApplyOperatingSystem	8/12/2010 12:20:44 AM	1924 (0x0784)
Set "C:\_SMSTaskSequence" to not be wiped	ApplyOperatingSystem	8/12/2010 12:20:44 AM	1924 (0x0784)
Set "%OSDStateStorePath%" to not be wiped	ApplyOperatingSystem	8/12/2010 12:20:44 AM	1924 (0x0784)
Set "%_SMSTSClientCache%" to not be wiped	ApplyOperatingSystem	8/12/2010 12:20:44 AM	1924 (0x0784)
Set "%_SMSTSNewClientCachePathToCleanup%" to not be wiped	ApplyOperatingSystem	8/12/2010 12:20:44 AM	1924 (0x0784)
Skipping C:\_SMSTaskSequence for wipe	ApplyOperatingSystem	8/12/2010 12:20:44 AM	1924 (0x0784)
Calculating expected free space.	ApplyOperatingSystem	8/12/2010 12:20:44 AM	1668 (0x0684)
Reporting deletion progress.	ApplyOperatingSystem	8/12/2010 12:20:44 AM	1668 (0x0684)
Successfully wiped C:\	ApplyOperatingSystem	8/12/2010 12:20:44 AM	1924 (0x0784)
Applying image to C:\	ApplyOperatingSystem	8/12/2010 12:20:44 AM	1924 (0x0784)
Applying image 1 to volume C:	ApplyOperatingSystem	8/12/2010 12:20:44 AM	1924 (0x0784)
WIM retry: C:\Windows\winsxs\x86_microsoft-windows-ime-korean-hwresource_31bf3856ad364e35_6.1.7600.16385_none_502bcdd40d7e6385\mshwkorrIME.dll (0x80070040)	ApplyOperatingSystem	8/12/2010 12:30:44 AM	1772 (0x06EC)
WIM error:C:\Windows\winsxs\x86_microsoft-windows-ime-korean-hwresource_31bf3856ad364e35_6.1.7600.16385_none_502bcdd40d7e6385\mshwkorrIME.dll. 
The network path was not found. (Error: 80070035; Source: Windows)	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1772 (0x06EC)
WIMApplyImage( hVolumeImage, const_cast<LPWSTR>(pathTargetVolume.c_str()), WIM_FLAG_VERIFY), HRESULT=80070035 (e:\nts_sms_fre\sms\framework\tscore\wimfile.cpp,512)	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1924 (0x0784)
Unable to apply (0x80070035)	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1924 (0x0784)
this->imageFile.ApplyVolumeImage(imageIndex, this->targetVolume), HRESULT=80070035 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,707)	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1924 (0x0784)
ApplyImage(), HRESULT=80070035 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1416)	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1924 (0x0784)
Apply(), HRESULT=80070035 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1456)	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1924 (0x0784)
Installation of image 1 in package SD20001A failed to complete.. 
The network path was not found. (Error: 80070035; Source: Windows)	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1924 (0x0784)
installer.install(), HRESULT=80070035 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1527)	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1924 (0x0784)
Closing image file \\sbjsccm1.mydomain.com\SMSPKGE$\SD20001A\Win7Combined.wim	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1924 (0x0784)
Entering ReleaseSource() for \\sbjsccm1.mydomain.com\SMSPKGE$\SD20001A\	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1924 (0x0784)
reference count 1 for the source \\sbjsccm1.mydomain.com\SMSPKGE$\SD20001A\ before releasing	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1924 (0x0784)
Released the resolved source \\sbjsccm1.mydomain.com\SMSPKGE$\SD20001A\	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1924 (0x0784)
InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName, bOEMMedia ), HRESULT=80070035 (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,373)	ApplyOperatingSystem	8/12/2010 12:31:09 AM	1924 (0x0784)
Process completed with exit code 2147942453	TSManager	8/12/2010 12:31:09 AM	212 (0x00D4)
!--------------------------------------------------------------------------------------------!	TSManager	8/12/2010 12:31:09 AM	212 (0x00D4)
Failed to run the action: Apply OS Image: Format Disk = Yes. 
The network path was not found. (Error: 80070035; Source: Windows)	TSManager	8/12/2010 12:31:09 AM	212 (0x00D4)

Thoughts on the error?

 

August 12th, 2010 6:10pm

"The network path was not found."

Something affected or prevented the network connectivity to "\\sbjsccm1.mydomain.com\SMSPKGE$\SD20001A\"



Free Windows Admin Tool Kit Click here and download it now
August 12th, 2010 8:29pm

HI,

Make sure the necessary ports is opend in firewall:

http://technet.microsoft.com/en-us/library/bb632618.aspx

August 20th, 2010 9:23am

It could be a permission problem or your DP's just not synchronized yet. :) If you've already enabled command prompt support in your boot image it's easier to figure out the problem during the process.
Free Windows Admin Tool Kit Click here and download it now
August 20th, 2010 10:50am

It could be a permission problem or your DP's just not synchronized yet. :) If you've already enabled command prompt support in your boot image it's easier to figure out the problem during the process.
August 20th, 2010 10:50am

It could be a permission problem or your DP's just not synchronized yet. :) If you've already enabled command prompt support in your boot image it's easier to figure out the problem during the process.
Free Windows Admin Tool Kit Click here and download it now
August 20th, 2010 10:50am

It could be a permission problem or your DP's just not synchronized yet. :) If you've already enabled command prompt support in your boot image it's easier to figure out the problem during the process.
August 20th, 2010 10:50am

i've had this issue recently also (random) on Precision M6500, what I do know about it is that prior to happening for some reason, the ip address was dropped   (which was picked up at the start of the task sequence) and therefore no network activity, therfore it fails,

what is interesting here is that it's failing right at the start (about 5 pips in) of downloading the wim file so network activty WAS working but is then dropped,

my suspicion however is that this is related to the version of network driver in the boot.wim file, once I know more about this I'll post it...

cheers

niall

Free Windows Admin Tool Kit Click here and download it now
August 20th, 2010 11:14am

I can only assume that a DP wasn't synchronized, as the problem eventually went away.  Oddly though, the built-in report "All active package distributions" didn't show any packages being processed.  Thanks for all the feedback.
August 24th, 2010 6:03pm

I am facing the same issue Niall. Initially systempicked the IP however after about 10 pips in , network connectivity is lost.

Did you find any solution or clearification about this issue?

Free Windows Admin Tool Kit Click here and download it now
September 13th, 2012 1:24pm

i have similar issue too.. the machine gets IP address fine (172.20.x.x) at the beginning of apply image step. just about after 75% of applying image section the TS fails.

i have looked up the log and it shows 

The network path was not found. (Error: 80070035; Source: Windows)

ipconfig now shows 169.252.x.x ip address .. i have refreshed the DP for boot images and have verified ports and permission seems to be in place.

any ideas?

September 30th, 2012 8:37am

Found the solution. We had implemented NAP in our environment and the Excluded MAC was not placed in proper VLAN that's why system not picking the production IP.

Therefore; system cant access on network path for OS image.

Free Windows Admin Tool Kit Click here and download it now
October 1st, 2012 6:07am

I was experiencing the same error with SCCM 2012 R2 when trying to build and capture a Win 8.1 x64 image.  The solution was that I was trying to save the image to a NetBIOS name of the server (i.e. \\sccm\capture).  Once I changed this to the IP address (I believe that the FQDN of \\sccm.contoso.com would have worked as well) like \\192.168.1.5\capture then the capture process worked.
May 29th, 2015 3:44pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics