Jump to content


lightiv

Task Sequence Fails After Applying Data Image 1 - Code 0x80004005

Recommended Posts

I get Error Task Sequence Manager failed to execute task sequence. Code 0x80004005 after the Apply Data Image 1. When I restart the PC I end up with a freshly installed Windows 7 but no User State Data from the old install. Any thoughts or suggestions. Thanks.

 

 

<![LOG[==========[ TsProgressUI started in process 1680 ]==========]LOG]!><time="08:02:14.359+480" date="12-06-2012" component="TsProgressUI" context="" type="1" thread="1676" file="winmain.cpp:329">

<![LOG[Command line: "X:\sms\bin\i386\TsProgressUI.exe" /Unregister]LOG]!><time="08:02:14.359+480" date="12-06-2012" component="TsProgressUI" context="" type="0" thread="1676" file="winmain.cpp:332">

<![LOG[unregistering COM classes]LOG]!><time="08:02:14.359+480" date="12-06-2012" component="TsProgressUI" context="" type="1" thread="1676" file="winmain.cpp:204">

<![LOG[unregistering class objects]LOG]!><time="08:02:14.375+480" date="12-06-2012" component="TsProgressUI" context="" type="1" thread="1676" file="winmain.cpp:495">

<![LOG[shutdown complete.]LOG]!><time="08:02:14.375+480" date="12-06-2012" component="TsProgressUI" context="" type="1" thread="1676" file="winmain.cpp:512">

<![LOG[Process completed with exit code 0]LOG]!><time="08:02:14.375+480" date="12-06-2012" component="TSManager" context="" type="1" thread="1776" file="commandline.cpp:1098">

<![LOG[successfully unregistered TS Progress UI.]LOG]!><time="08:02:14.375+480" date="12-06-2012" component="TSManager" context="" type="1" thread="1776" file="utils.cpp:2075">

<![LOG[g_TSManager.Run(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,641)]LOG]!><time="08:02:14.375+480" date="12-06-2012" component="TSManager" context="" type="0" thread="1776" file="tsmanager.cpp:641">

<![LOG[Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]LOG]!><time="08:02:14.375+480" date="12-06-2012" component="TSManager" context="" type="3" thread="1776" file="tsmanager.cpp:671">

<![LOG[sending error status message]LOG]!><time="08:02:14.375+480" date="12-06-2012" component="TSManager" context="" type="1" thread="1776" file="tsmanager.cpp:672">

<![LOG[MP server asd.LOCAL. Ports 80,443. CRL=false.]LOG]!><time="08:02:14.390+480" date="12-06-2012" component="TSManager" context="" type="1" thread="1776" file="utils.cpp:4855">

<![LOG[setting authenticator]LOG]!><time="08:02:14.390+480" date="12-06-2012" component="TSManager" context="" type="1" thread="1776" file="utils.cpp:4877">

<![LOG[set authenticator in transport]LOG]!><time="08:02:14.390+480" date="12-06-2012" component="TSManager" context="" type="1" thread="1776" file="libsmsmessaging.cpp:7592">

<![LOG[sending StatusMessage]LOG]!><time="08:02:14.453+480" date="12-06-2012" component="TSManager" context="" type="1" thread="1776" file="libsmsmessaging.cpp:4020">

<![LOG[setting message signatures.]LOG]!><time="08:02:14.656+480" date="12-06-2012" component="TSManager" context="" type="0" thread="1776" file="libsmsmessaging.cpp:1292">

<![LOG[setting the authenticator.]LOG]!><time="08:02:14.656+480" date="12-06-2012" component="TSManager" context="" type="0" thread="1776" file="libsmsmessaging.cpp:1322">

<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: asd.LOCAL:80 CCM_POST /ccm_system/request]LOG]!><time="08:02:14.671+480" date="12-06-2012" component="TSManager" context="" type="1" thread="1776" file="libsmsmessaging.cpp:8422">

<![LOG[Request was succesful.]LOG]!><time="08:02:14.718+480" date="12-06-2012" component="TSManager" context="" type="0" thread="1776" file="libsmsmessaging.cpp:8758">

<![LOG[Finalize logging request ignored from process 1772]LOG]!><time="08:02:14.734+480" date="12-06-2012" component="TSManager" context="" type="1" thread="1776" file="tslogging.cpp:1737">

<![LOG[Process completed with exit code 2147500037]LOG]!><time="08:02:14.765+480" date="12-06-2012" component="TSMBootstrap" context="" type="1" thread="1732" file="commandline.cpp:1098">

<![LOG[Exiting with return code 0x80004005]LOG]!><time="08:02:14.765+480" date="12-06-2012" component="TSMBootstrap" context="" type="1" thread="1732" file="tsmbootstrap.cpp:1032">

<![LOG[Execution complete.]LOG]!><time="08:02:14.812+480" date="12-06-2012" component="TSBootShell" context="" type="1" thread="752" file="bootshell.cpp:616">

<![LOG[Finalizing logging from process 740]LOG]!><time="08:02:14.812+480" date="12-06-2012" component="TSBootShell" context="" type="1" thread="752" file="tslogging.cpp:1741">

<![LOG[Finalizing logs to root of first available drive]LOG]!><time="08:02:14.812+480" date="12-06-2012" component="TSBootShell" context="" type="1" thread="752" file="tslogging.cpp:1583">

<![LOG[successfully finalized logs to C:\SMSTSLog]LOG]!><time="08:02:14.843+480" date="12-06-2012" component="TSBootShell" context="" type="1" thread="752" file="tslogging.cpp:1640">

<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="08:02:14.843+480" date="12-06-2012" component="TSBootShell" context="" type="0" thread="752" file="tslogging.cpp:584">

Share this post


Link to post
Share on other sites

I've recreated it and I am in the process of giving it another go. If it fails again I will provide the task sequence and the log file.

 

I am using the book System Center 2012 Configuration Manager Unleashed as my guide.

 

I am using a custom Win7 image (.wim) and no PXE boot. I am selecting it from the Software Center on the client PC

Share this post


Link to post
Share on other sites

apply data image1

I take it you captured this image previously and are not using the default install .wim file from the media?

 

If this is the case then you have to move the apply data image 1 directly above the apply OS task.

Also edit the partition so that it installs on 100% of the rest of the disk otherwise it you will have a unallocated partiton after OSD!!

 

Rocket Man

Share this post


Link to post
Share on other sites

Are you distributing your TS to DPs?

 

OR

 

Have you individually distributed all packages attached to TS to your DPs?

 

If it is the 1st then after you deleted the first TS then this would have also removed all content attached to it from DP also.

You may have to distribute all attached packages again out to the DPs.

Share this post


Link to post
Share on other sites

A new week and a new look at the problem.

 

Rocket Man, thanks for your suggestion in regard to putting the Apply Data Image 1 before the OS but unfortunately it did not work.

 

Peter in follow-up to the request of more information.

 

I am trying to do a OS Refresh to bring Windows Vista SP1 and XP SP 3 to Windows 7 Enterprise Ed. SP 1 with SCCM 2012. We want to preserve the user's existing hard drive in case there is data stored there outside of the profile. I am using USMT 4.0 to copy and restore the user's profile from the old to the new PC. I am using a customized wim image of the OS that I created/captured myself using SCCM 2012. This image includes Office 2010 and the Windows 7 volume license key so we do not have to enter it after upgrade.

 

Here is my Task Sequence. It fails after applying the Operating System.

 

post-17377-0-22109900-1355150756_thumb.png

 

Here is the smsts.log:

 

smsts1.log

 

Thanks

Share this post


Link to post
Share on other sites

What's the data image good for? Seems you didn't specify a valid drive for the image to apply to.

 

There are no more volumes available for use.

The requested target could not be resolved to a valid volume on this computer. Check your task sequence to ensure this drive is correct and that it is being created

Share this post


Link to post
Share on other sites

Ok, taking a closer look at the log file I believe this is the offending lines:

 

<![LOG[The requested target could not be resolved to a valid volume on this computer. Check your task sequence to ensure this drive is correct and that it is being created

The parameter is incorrect. (Error: 80070057; Source: Windows)]LOG]!><time="12:51:33.656+480" date="12-07-2012" component="ApplyOperatingSystem" context="" type="3" thread="1584" file="installcommon.cpp:633">

<![LOG[ResolveTarget( g_Target, g_InstallType == InstallType_DataImage, targetVolume ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,453)]LOG]!><time="12:51:33.656+480" date="12-07-2012" component="ApplyOperatingSystem" context="" type="0" thread="1584" file="applyos.cpp:453">

<![LOG[Process completed with exit code 2147500037]LOG]!><time="12:51:33.718+480" date="12-07-2012" component="TSManager" context="" type="1" thread="1768" file="commandline.cpp:1098">

<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="12:51:33.734+480" date="12-07-2012" component="TSManager" context="" type="1" thread="1768" file="instruction.cxx:3011">

<![LOG[Failed to run the action: Apply Data Image 1.

 

What exactly is Data Image 1? Is it the hidden 100MB boot partition for Windows? It appears to me that it is having a problem find the correct volume to apply the image to.

 

Here is the setting for TS Apply Data Image 1

 

post-17377-0-83939500-1355158450_thumb.png

 

The Apply Operating System step before this is set to Image 2 -2

Share this post


Link to post
Share on other sites

Hi Peter, I see you responded while I was composing the above. Using the Wizard I do not recall being given choice was to what would be installed where. I expected that SCCM would put the needed partition/volumes in the right spot. I guess I need to know what the Data Image 1 is. I am thinking it may be the hidden Win 7 boot partition but I don't know. If not then maybe it can be deleted. Oh, I told the sequence to keep the user state on the hard disk so it would not be sent to the server (to save bandwidth and speed). That might be what this is.

Share this post


Link to post
Share on other sites

Forget about the data image then. If it's really the BDE partition it's not needed. Windows will apply the correct files for the BDE partiton itself. if the partition exists on your machine.

Just by the way. The correct partition would be be Disk 0 Partition 0.

Share this post


Link to post
Share on other sites

Move the apply data image1 directly above the apply OS task...in the partiotion task you will see 2 partitions the 1st one been very small approx 100mb this is the apply data image1 thus the reason as to why you have to move it above the apply OS task, also in partition task select the second partition and edit it make it install on 100% of the rest of the disk(this is your C drive) and also name the partition if you like!!

 

I have some images that have this apply data image after I have captured from a VM, and when I create an OS image and TS out of it I have the same tasks(apply data image 1 and apply OS), i do the above and it works for me, no reason as to why it should not work for you!! Remove the capture files and remove the capture windows settings of the task sequence and see how it go's..

 

This image is same as your TS except i moved the apply data image above the apply OS

 

1.PNG

 

This one shows the the 100 mb partition(this is the apply data image and by default is above the main primary partition thus the reason as to why you have to move it above the apply OS)

 

2.PNG

Share this post


Link to post
Share on other sites

He has no partitioning step in his task sequence.

If you use MDT you can easily create the BDE Partition by adding 3 new steps after the apply OS step.

 

- use toolkit package

- gather

- run command line (cscript.exe "%ScriptRoot%\ZTIBde.wsf" /debug:TRUE)

 

This will create a new BDE partition if none exists. It also applies the boot manager and makes it the boot partition.

Share this post


Link to post
Share on other sites

Hey guys, thanks for the help.

 

Peter, after I delete the Apply Data Image 1 step and redeployed the TS everything worked. :) The first test VM was Vista and I will try XP today.

 

Rocket Man, the reason I do not have any partitioning is that we want to preserve the exiting hard drive in case the user has data on it outside of their profile.

Share this post


Link to post
Share on other sites

Hi lightiv,

 

keep in mind that you will need the BDE partition if you plan to use Bitlocker on Windows 7 Enterprise Laptops. So think about the MDT step i mentioned.

As a side note. Deactivate the "client rapair on boot" on your Windows 7 machines (bcdedit /set {default} bootstatuspolicy ignoreallfailures) right in your task sequence. As soon as a client repair triggers, the client will be unable to log on to your domain.

Share this post


Link to post
Share on other sites

Hi Peter and thank. I guess I need to do some reading up on MDT. I don't know if I have access to it or not.

 

As for deactivating the "Client Repair On Boot" option I am assuming that will be a "Run Command Line" step. Where should I insert that? After the "Setup Windows and Configuration" step?

 

Thanks.

Share this post


Link to post
Share on other sites

Hi Peter,

 

I just wanted followup and say thanks again for your help. I just migrated my first XP PC to Windows 7 while successfully maintaining the User State Data.

 

I have another question with regard to Activation. I know that there is the option to "not" reset the activation. We are a Microsoft Enterprise Agreement organization. I want the newly upgraded machine to maintain its OS and Office 2010 activations so we don't have to reactivate them for each user. If I set the Task Sequence to not reset the activation will it give me the desired result and is the any drawbacks for this?

 

Thanks,

 

Paul

Share this post


Link to post
Share on other sites

Hi light,

 

 

this flag is for the build and capture of an image to prevent windows to show the activation dialog after the deployment of the final image. There should be no harm though to use it. I guess your are running a KMS server for the activation.

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...