Jump to content


c4pp3r

OSD fails to half of computers error 0x80072ee2 and others

Recommended Posts

Hi guys

 

I'm pulling my hair out here. Every time I do a Windows 7 OSD to a lab of computers (NOTE: systems are already running with Windows, so OSD deployed via System Centre client as a forced sequence), about half will fail.

 

Things to mention:

Now, I have never been at a computer as the sequence as failed, so whenever I check a failed system it's always requires me to boot it up with a windows USB boot disk (ie: UBCD). When I do this, the failed PC's C drive only has the "SMSTSLog" folder on it, nothing else.

 

I use a domain account for the Network Access account. I've even tried with the Domain Admin account and the same issue occurs.

 

This occurs on both of my OSD sequences which use a different wim file (different PC systems)

 

If I reboot the system with a SCCM boot disk, or via PXE, and let the task sequence start again (I have "rerun if failed" enabled) the OSD works perfectly, well, the PC loses its AD name and I have to rename it, but that's no biggie.

 

Running the "History of a task sequence" report, I get the following

 

PersistContents ), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1368)
resolvePkgSource(), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1411)
Apply(), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1614)
installer.install(), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1689)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\BUN0001A
The user tries to release a source directory C:\_SMSTaskSequence\Packages\BUN0001A that is either already released or we have not connected to it
InstallImage( g_InstallPackageID, g_ImageIndex,targetVolume, ImageType_OS, g_ConfigPackageID,g_ConfigFileName, bOEMMedia ), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,470)
Installation of image 1 in package BUN0001A failed to complete..
The system cannot find the file specified. (Error:80070002; Source: Windows)

 

 

SMSTS log attached

smsts.log

Share this post


Link to post
Share on other sites


Seems to me you need to check that all clients can access the file "Failed to run the last action: Install Dell 780 Image. Execution of task sequence failed.

The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="08:01:22.593-660" date="10-07-2012" component="TSManager" context="" type="3" thread="1936" file="engine.cxx:214"

Share this post


Link to post
Share on other sites

They should have full access to the file. If all systems failed then I'd understand, but the fact that only half of them fail, and then the second time round they find the file, leads me to believe it is another issue,

Share this post


Link to post
Share on other sites

have you double checked your Network Access Account that's it's set and set correctly ?

 

<![LOG[GetDirectoryListing() successfully completed]LOG]!><time="07:56:28.595-660" date="10-07-2012" component="ApplyOperatingSystem" context="" type="1" thread="1192" file="downloadcontent.cpp:579">

<![LOG[succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="07:56:28.595-660" date="10-07-2012" component="ApplyOperatingSystem" context="" type="1" thread="1192" file="util.cpp:910">

<![LOG[401 - Authentication failure on request with anonymous access, retrying with context credentials.]LOG]!><time="07:56:28.610-660" date="10-07-2012" component="ApplyOperatingSystem" context="" type="0" thread="1192" file="downloadcontent.cpp:1484">

<![LOG[401 - Authentication failure on request with context credentials, retrying with supplied credentials.]LOG]!><time="07:56:28.642-660" date="10-07-2012" component="ApplyOperatingSystem" context="" type="0" thread="1192" file="downloadcontent.cpp:1489">

<![LOG[WinHttpReadData(hRequest, (LPVOID)pszOutBuffer, dwSize, &dwRead), HRESULT=80072ee2 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,1006)]LOG]!><time="07:59:25.858-660" date="10-07-2012" component="ApplyOperatingSystem" context="" type="0" thread="1192" file="downloadcontent.cpp:1006">

<![LOG[ReadDataAndWriteToFile() failed with 0x80072ee2 when downloading 0% of file C:\_SMSTaskSequence\Packages\BUN0001A\780finalcomp.wim]LOG]!><time="07:59:25.858-660" date="10-07-2012" component="ApplyOperatingSystem" context="" type="3" thread="1192" file="downloadcontent.cpp:1037">

<![LOG[ReadDataAndWriteToFile(hRequest, ullFileSize, hFile, sDestination, ulTotalSizeRequired, ulDownLoaded), HRESULT=80072ee2 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,1537)]LOG]!><time="07:59:25.858-660" date="10-07-2012" component="ApplyOperatingSystem" context="" type="0" thread="1192" file="downloadcontent.cpp:1537">

<![LOG[Download() failed with 0x80072ee2]LOG]!><time="07:59:25.858-660" date="10-07-2012" component="ApplyOperatingSystem" context="" type="3" thread="1192" file="downloadcontent.cpp:1543">

<![LOG[DownloadFile(sSourceFile, sDestinationFile, ulTotalSizeRequired, ulDownLoaded, bUseSSL), HRESULT=80072ee2 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,1596)]LOG]!><time="07:59:25.858-660" date="10-07-2012" component="ApplyOperatingSystem" context="" type="0" thread="1192" file="downloadcontent.cpp:1596">

<![LOG[Error downloading file from http://myserver.myserver.com.au:80/SMS_DP_SMSPKG$/BUN0001A/sccm?/780finalcomp.wim to C:\_SMSTaskSequence\Packages\BUN0001A\780finalcomp.wim ]LOG]!><time="07:59:25.858-660" date="10-07-2012" component="ApplyOperatingSystem" context="" type="3" thread="1192" file="downloadcontent.cpp:1596">

Share this post


Link to post
Share on other sites

Is it the same PCs that are failing or different PCs all the time from that collection?

 

I'm pulling my hair out here. Every time I do a Windows 7 OSD to a lab of computers (NOTE: systems are already running with Windows, so OSD deployed via System Centre client as a forced sequence), about half will fail.

 

From your symptoms (half will fail) then I gather the others are successful....then it may be some underlying problem with your internal network/PCs hardware??

 

Have you tried to isolate these problematic PCs into a seperate test collection and try the same TS out to them?? (See if any of them are successful)??

Share this post


Link to post
Share on other sites

OneOne: Boundaries are fine from what I can see Also, my collections a split into rooms, so the PCs I image are always on the same subnet. if it were boundaries the whole room would fail I presume?

 

Anyweb: Network Access account is fine (currently set to Domain Admin, but I have tried others too).

 

Rocket: That's right. Half fail, half succeed. I doubt it's H/W related because if I run the task again on the the failed systems, the OSD completes successfully with the exact same settings, Network account and boundaries as when they failed. the ONLY difference is that on the second turn I initiate the OSD via PXE or a USB boot disk, whereas the initial OSD is initiated from within Windows and the SCCM client.

Share this post


Link to post
Share on other sites

Is it the same machines that are failing all the time or is it different??

 

Have you isolated these problematic PCs and tried the forced client OSD install to see if they still fail?

Share this post


Link to post
Share on other sites

Do you mean a 3rd time via OSD? I've been pressed for time so I haven't had a chance to image them a 3rd time to check that, but will do this week and post back.

Share this post


Link to post
Share on other sites

If possible....... but isolate the problematic PCs(if you can remember which ones failed) into a seperate collection and push it out to the live OS.......just to rule out that there is nothing weird happening on your network(connectivity issues.etc) at time of OSD to full collection.

 

I doubt it is Boundary related nor NetAccess account related if some pass and some fail and all machines are on the same subnet/physical LAN/switch....if it was either BG or Net Account then it can only be assumed that all would fail.....right?

 

Just out of curiosity....Are all machines same model that are in this collection??

Share this post


Link to post
Share on other sites

have you verified they have the required network drivers added via an apply driver package step (you can bring up a command prompt around the time of failure and type ipconfig, any valid ip address ? can you ping the fqdn of the managment point ?)

Share this post


Link to post
Share on other sites
the OSD works perfectly, well, the PC loses its AD name and I have to rename it, but that's no biggie.

 

Ok so you rename them also because of the above after they have failed and you then PXE boot them to get them imaged.......are there any entries like MININT-XXXXXX in all systems/AD.....it could also be that there is a duplicate entry for these PCs MAC addresses...

 

Does the new naming of the computers update in AD or is the old names present there also?

Share this post


Link to post
Share on other sites

Sorry for the lack of reply.

 

anyweb: Yep, the drivers are all right.

 

Rocket: Most of these MININT named PCs will rename and join the Domain just fine and take over their original AD account. Only a tiny number will give me a duplicate name error so I then have to delete the computer from AD and then rename the MINIT one and re-join.

 

NOTE: I haven't had a chance to do my test yet, planninto at the start of Nov (got a few straight days with no users!)

Share this post


Link to post
Share on other sites

Hi ,

 

Would be interested if you came up with a cause /solution for your problems as we are experiencing the same problem.

 

for example: Building 10 Machines and 6 or 7 randomly fail in different places .. and 3 or 4 will build successfully.

Build the same 10 machines again and have the same ratio of failure but not on the same machines.

 

Using Dell , different makes and models. (780's 790's E6320's E6400's E4310's)

Share this post


Link to post
Share on other sites

I am also interested if any has come up with a solution for this as I'm having a similar problem but I've narrowed it down a bit more.

 

It seems that my clients start the download fine and either finish the download without problems or some just fail after a random percentage has been downloaded. Here are some error log entries from an OSD client that failed:

 

ReadDataAndWriteToFile() failed with 0x80072efe when downloading 27% of file C:\_SMSTaskSequence\Packages\ISD0002A\Windows.7.x64.Thick.Basic.wim ApplyOperatingSystem 2/12/2013 1:36:00 PM 1472 (0x05C0)

DownloadFile failed. 80072efe. ApplyOperatingSystem 2/12/2013 1:36:00 PM 1472 (0x05C0)

Error downloading file from http://XXXXX.XXXXXXX.local:80/SMS_DP_SMSPKG$/ISD0002A/sccm?/Windows.7.x64.Thick.Basic.wim to C:\_SMSTaskSequence\Packages\ISD0002A\Windows.7.x64.Thick.Basic.wim ApplyOperatingSystem 2/12/2013 1:36:00 PM 1472 (0x05C0)

 

Notice it failed at 27%, some fail at 25%, others at 89%, and some don't fail at it. It's important to remember these computers are the same model, in the same room, same switch. I downloaded the file directly from a browser, using http://XXXXX.XXXXXXX.local:80/SMS_DP_SMSPKG$/ISD0002A/sccm?/Windows.7.x64.Thick.Basic.wim, and the first time I did it it downloaded the file. On the second try it failed after only getting ~20% of the file.

 

Does anyone have any ideas, or suggestions. What other log files can I look in? Could it be an issue with IIS?

Share this post


Link to post
Share on other sites

Hi there, I just wanted to bump this to say I just starting experiencing this as well. My system has been running fine for approx. 3 weeks and then all of a sudden this starts happening.

 

SCCM 2012 SP1 running on Windows Server 2012 + all Windows updates

 

Primary Site Server - Windows Server 2012

SQL Server - SQL Server 2012

34 Distribution Points - Windows Server 2012

 

The whole system has been working amazing, then I start getting calls about OSD not working. It seems to have broken on multiple DPs with the error code 0x80072EE2. This is across multiple locations on multiple networks. I don't know if it's broken on all DPs but there have been reports from multiple locations. Imaging will fail at a random % with error code 0x80072EE2 which seems to reference a "network connection failed" type message.

 

I haven't been able to track down the culprit yet so if anyone has a suggestion, it would be most welcome.

 

Thank you.

Share this post


Link to post
Share on other sites

Had problems myself since my previous posts......have a single PS at a single site which will eventually branch off to multiple remote DPs.....Have not got a successful lab imaged as of yet, some bomb out and others image fine, but hit a major blackspot in a couple of labs, couldnt get really anything to work. It is a quite an intricate network with mutiple VLANs, and what I found just today is that spanning tree was enabled on switches that caused quite a few problems including getting clients to PXE. Got onto the network guys and got it disabled and since that all clients that could not PXe starting to PXE again.

 

Have not got around to the other labs yet to see if it has made any difference to clients bombing out half way through imaging but hopefully it can only help. maybe spanning tree could be a possibility?

Share this post


Link to post
Share on other sites

I checked with our network guys and we do run spanning tree, but what really bothers me is that this was a working setup up until yesterday. It's been running really well for at least 3 weeks and out of the blue it craps out like this. I've been working on this all day today with no joy at all. The only thing that is consistant is that the image download will fail at a random % every time with the 0x80072EE2 error. Bummer...

 

I'll update if I discover anything new. Thanks for the suggestion.

Share this post


Link to post
Share on other sites

OK so I just wanted to post an update. I changed one setting on all of my distribution points; I unchecked "Allow fallback source location for content". This setting has been enabled and working fine for 3 weeks so I don't know what happened, but now my imaging works again. I have successfully deployed 5 workstations since unchecking that option. It may be a coincidence but since making that change everything is back to working.

 

Anyway, I'm keeping that setting disabled and I'll post back with an update if anything changes.

  • Like 1

Share this post


Link to post
Share on other sites

Well it looks like I spoke too soon. Imaging is back to not working again. Same timeout error message as before.

 

It was nice while it lasted...

Share this post


Link to post
Share on other sites

BUMP!

 

I am having the same issue as listed above. SCCM 2012, SVR2012.

 

All machines work fine except for one model (which was working last week). They are all the same brand laptop but the model with the issue does happen to use UEFI(I don't think that should matter but...)

 

Now, for some reason, this one model will get to anywhere from 5% to 85% downloaded and then fail.

 

Any suggestions?

 

Thanks.

Share this post


Link to post
Share on other sites

This may help some people. In my case, it was an issue with a USB to Ethernet dongle. We purchased Lenovo Carbon X1's for our employees and it is a very thin laptop with no built in ethernet port. The supplied Lenovo USB 2.0 to 10/100 Ethernet adapter would download the image from the SCCM server at about 1G every 90-100 seconds. This was apparently too slow. Even though we brought up a command prompt and did a constant ping and it never dropped a packet, at some random percentage it would just stop downloading and say it lost connection. Even though it never actually did. We tried the new drivers another website recommends for the dongle straight from the dongle manufacturer but to no avail.

We then bought a USB 3.0 to Gigabit Ethernet adapter(not available from Lenovo), loaded the files into the base image, had SCCM build a bootable USB media.

Plug in the USB, plug in the (non working yet) USB 3.0 adapter, boot from the USB, let it load the drivers and you could see the link light come on and then WinPE took over from there and ran successfully every time.

It now downloads the image at 1G every 17-18 seconds.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...