"Errors in Task Sequence" dialog after replicating DS

I'm trying to replicate some scripts in the \Scripts folder from a Server 2008 R2 machine running MDT 2012 (update nothing) at our main office out to other servers running the same version of Windows and MDT at our remote sites.  I've found
that after doing this and opening the task sequence using this new script at the remote site I get the "This task sequence contains one or more errors..." message.  The wim file has been wiped out from the "Install Operating System"
step. The first time I saw this I fixed it thinking it was a one time glitch.  Before I replicated to the second remote site I first opened the ts to make sure the wim file was set, then I closed the MDT console, replicated, opened the ts, same
thing, the wim file was removed.  Even if I fix it the next replication once again removes the wim.  I've also tried uninstalling / reinstalling the MDT console on the source server at our main office, same thing.  Looking at the actual
ts.xml for the task sequence at the remote site I can see that the wim file is set, why is the GUI not picking it up?
Ideas?
Some back story that may be related: the local primary server that I would normally use to replicate out DS content was updated to 2012 Update 1 by a coworker a while back, but not the other local secondary server and not the remote sites. 
When I attempted to use my usual replication server yesterday to replicate content I got an error about the versions being different.  Fine, I copied the new scripts to the scripts folder, made the ts changes manually, and setup the remote sites
as linked deployment shares on my secondary server, and decided I'd just use that for replication.  Now I'm thinking maybe something got scrambled when I attemtpted to replicate a 2012 Update 1 DS to 2012 Update nothing.

My specific question is why is the DS replication removing the wim file from the Install Operating System step? 
Both the source and target DS's are the same version and I can see that the ts.xml file for the TS in question is being copied to the target DS over but the GUI is not reading the wim file from the xml.  I may be missing something simple here
but I've replicated hundreds of times in the past and never had this issue.

Similar Messages

  • Task sequence fails after upgrading to 2012 R2 and MDT 2013

    After upgrading to 2012 R2, my task sequence fails after the Setup Windows and ConfigMGR & Restart Computer. Instead of continuing to run the task sequence and load up the MDT Toolkit Package, it just stops at the Windows 7 login screen.
    Do I need to create new toolkit & settings packages with MDT 2013 settings? Or do I just need to create a new task sequence?
    I can't figure out what log to look at on the VM that I am imaging. If someone can point it out maybe there's some useful information. Thanks.
    My task sequence

    It sounds a lot like that it could be failing at the client installation. Please take a look at the client installation logs.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude
    Here are the log files from c:\windows\ccmsetup\logs .. I took a glance and things run with success 0 which should mean no error right? The system also has the client installed with the CU2 patch.
    Client Logs
    Searched a bit online and people are saying it's due to the incorrect boot image. I was using a WinPE 5.0 I created on this TS but I'm going to make another and see where it goes.
    This was the solution.

  • MDT 2013 Windows 8.1 Task sequence Stops After first Reboot. login

    Hi There,
    The issue I am having is that After the OS gets laid down, and the Windows 8.1 computer reboots, The task sequence does not continue. It fails everytime. There are not any obvious errors that happen in the process that I can see in the logs. But I have
    customized this process quite a bit and I could use some help. We are deploying potentionally to over 30,000 computers.
    The test machine I have been using is the Surface pro 2.
    The interesting part is after a failure is if I start the process over again ,  boots into PE, then run diskpart manually from command prompt to Clean Disk 0, and then reboot and start the MDT task sequence, it will deploy fine.
    I also have a custom step that copies the TS media from the stick to a Recovery partition I create. The user can launch a -re-image or MDT refresh from an Icon/script, which will unhide this "recovery partition", and kick off a lite touch refresh.
    This works succesfully everytime. We have remote locations with very slow links, so MDT over the network or MDT integrated with SCCM is not an option at this time. So this is the solution.
    I am attempting to use MDT 2013 to deploy Windows 8.1 Offline, and using GPT partitions.
    I am using a custom Format and partiition Step, that call the CustomDiskpart.txt script from %deployroot%\Scripts.
    I am also using a Split image, as multi partitioned EFI/NTFS USB sticks are not a possibility for us , also, the USB sticks capable of this are seen by MDT as a "fixed drive" anyways. Which can cause issues in itself. So the LTIAPPLY.wsf has
    been edited to search and apply ther split .swm files.  This works well.
    After the Task sequence failure I have tried launching the Litetouch scripts from the C:\MINNINT folder manually to continue the sequence, but it doesnt  do anything.
    I don't want to always be running Diskpart manually before imaging a new OEM computer. I needa second pair of eyes on this.
    Thank You in advance!

    Hi,
    Thanks Again for taking a look.
    I checked the sysprep log in the image and they look fine. No errors.
    As requested here are some logs. Let me know if I can provide anything else.
    BDD.log
    litetouch.log
    SMSTS.log
    Im not actually attempting to provide a recovery image. What I am doing is leveraging MDT to refresh the computer remotely. We can update the MDT media on the hidden data partition,when required and kick it off remotely. Some of the computers are very
    remote, and without SCCM DP's, plus a combination of slow links and a lack of deskside techs made this a requirement. This works without incident.
    The only issue I have is on a new computer if I run the sequence (offline USB media) it will fail the first time, unless I run a diskpart clean in PE first.. Then it will succeed. Refreshing the computer is fine.

  • Error editing task sequence: Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" From XML into WMI

    I've started getting an intermittent error editing my Windows 7 OSD task sequence.  Sometimes I can open the TS to edit, but when I try to apply changes I get the error.  Other times I get the error when trying to open the TS.  If I try again
    right away, I still get the error, but if I wait a few minutes and try again sometimes it will open the TS. 
    The error reads:
    ConfigMgr Error Object:instance of SMS_Extended Status{Description = "Failed to load dynamic properties for class \"SMS_TaskSequence_ApplyWindowsSettingsAction\" from XML into WMI";Error Code = 2147943746;File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\ssptspackage.cpp";Line = 3454;Operation = "ExecMethod";ParameterInfo = "SMS_TaskSequencePackage";ProviderName = "WinMgmt";StatusCode = 2147749889;}
    Coinciding with this error, I show the following entries in the TaskSequenceProvider.log file: 
    [PID: 7608] Invoking method SMS_TaskSequence.LoadFromXml
    TaskSequenceProvider
    Failed to protect memory buffer, hr=0x80070542
    TaskSequenceProvider
    Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" from XML into WMI 0x80070542 (2147943746)
    TaskSequenceProvider
    Failed to load node Apply Windows Settings from XML into WMI 0x80070542 (2147943746)
    TaskSequenceProvider
    Failed to load children steps for node "PostInstall" from XML 0x80070542 (2147943746)
    TaskSequenceProvider
    Failed to load children steps for node "Execute Task Sequence" from XML 0x80070542 (2147943746)
    TaskSequenceProvider
    Failed to load children steps for node "" from XML 0x80070542 (2147943746)
    TaskSequenceProvider
    Failed to load XML for the task sequence into WMI 0x80070542 (2147943746)
    TaskSequenceProvider
    [PID: 7608] Done with method SMS_TaskSequence.LoadFromXml
    TaskSequenceProvider
    Setting status complete:  status code = 0x80070542; Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" from XML into WMI
    TaskSequenceProvider
    I exported the task sequence and checked in "object.xml" for the "ApplyWindowsSettingsAction", to see if there was something odd in the xml, but I don't find anything that jumps out as being wrong.  Here's the section of XML for
    that step.  I've removed identifying info, and replaced it with a generic term in bold.
    <step type="SMS_TaskSequence_ApplyWindowsSettingsAction" name="Apply Windows Settings" description="" runIn="WinPE" successCodeList="0" runFromNet="false"><action>osdwinsettings.exe /config</action><defaultVarList><variable name="OSDLocalAdminPassword" property="AdminPassword"></variable><variable name="OSDComputerName" property="ComputerName">%_SMSTSMachineName%</variable><variable name="OSDProductKey" property="ProductKey"></variable><variable name="OSDRandomAdminPassword" property="RandomAdminPassword">false</variable><variable name="OSDRegisteredOrgName" property="RegisteredOrgName">COMPANY NAME</variable><variable name="OSDRegisteredUserName" property="RegisteredUserName">COMPANY NAME</variable><variable name="OSDServerLicenseConnectionLimit" property="ServerLicenseConnectionLimit">5</variable><variable name="OSDTimeZone" property="TimeZone">Central Standard Time</variable></defaultVarList></step><step type="SMS_TaskSequence_ApplyNetworkSettingsAction" name="Apply Network Settings" description="" runIn="WinPEandFullOS" successCodeList="0" runFromNet="false"><action>osdnetsettings.exe configure</action><defaultVarList><variable name="OSDDomainName" property="DomainName">DOMAIN.COM</variable><variable name="OSDJoinPassword" property="DomainPassword"></variable><variable name="OSDJoinAccount" property="DomainUsername">DOMAIN ACCOUNT</variable><variable name="OSDEnableTCPIPFiltering" property="EnableTCPIPFiltering" hidden="true">false</variable><variable name="OSDNetworkJoinType" property="NetworkJoinType">0</variable><variable name="OSDAdapterCount" property="NumAdapters" hidden="true">0</variable></defaultVarList></step>
    Is there any other log I should check for a clue on this issue?  What could be causing this error?

    Thanks for sharing that!  I tend to save contacting MS support until after I've exhausted other options.  I'm always afraid that I'll spend the $500 to open a case and then it turns out to be something simple that I would have found if I had just
    kept working on it myself a little longer.
    It looks like that link is for an update released in February as KB3023562.  I downloaded and installed it. I'll try opening/editing/saving the task sequence a few times today to see if the issue is resolved.  
    After I had already installed it, I thought to look up that update in configmgr.  The update is listed as superseded by 2 other updates.  The newest of those is KB3046049, which just installed last night with the other March patches, so it's possible
    that I didn't need to install KB3023562 after all.  

  • SCCM 2012 R2 - Error with Task Sequence relating to Multicast issues

    Using a copy of a working task sequence; we have deployed a new v.6.3.9600.16384 boot image with latest Intel I217-LM driver.
    The task sequence runs perfectly fine, then stops after running "Setup Windows and Configmgr" task with an 0x80004005 error.
    Upon examination of the smsts.log file there appears to be a problem with multicast; can anyone help?
    Below is the extract of the smsts.log error:

    Found this in the smsts.log;
    <![LOG[==============================[ OSDSetupWindows.exe ]===========================]LOG]!><time="09:52:42.977+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="setupwindows.cpp:1627">
    <![LOG[Command line: "OSDSetupWindows.exe"]LOG]!><time="09:52:42.977+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="setupwindows.cpp:1628">
    <![LOG[Installing BOOTMGR bootsector]LOG]!><time="09:52:42.993+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="bootsector.cpp:73">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="09:52:43.009+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="commandline.cpp:228">
    <![LOG[Set command line: "bootsect.exe" /NT60 SYS /MBR]LOG]!><time="09:52:43.009+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="commandline.cpp:731">
    <![LOG[Executing command line: "bootsect.exe" /NT60 SYS /MBR]LOG]!><time="09:52:43.009+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="commandline.cpp:827">
    <![LOG[Process completed with exit code 0]LOG]!><time="09:52:45.510+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="commandline.cpp:1123">
    <![LOG[ResolveSource flags: 0x00000000]LOG]!><time="09:52:45.510+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="resolvesource.cpp:3201">
    <![LOG[SMSTSPersistContent: . The content for package LTC00011 will be persisted]LOG]!><time="09:52:45.510+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="resolvesource.cpp:3212">
    <![LOG[The package LTC00011 is found locally in the cache C:\_SMSTaskSequence\Packages\LTC00011]LOG]!><time="09:52:45.510+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="resolvesource.cpp:3242">
    <![LOG[!Directory::Exists(sNormalizedPath), HRESULT=800700b7 (e:\nts_sccm_release\sms\framework\core\ccmcore\path.cpp,156)]LOG]!><time="09:52:45.510+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="path.cpp:156">
    <![LOG[Setting hive location to "C:\_SMSTaskSequence\OSD\Vista\Windows\System32\SMI\Store\Machine"]LOG]!><time="09:52:45.510+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="smiinterface.cpp:812">
    <![LOG[Loading existing answer file "C:\_SMSTaskSequence\unattend.xml"]LOG]!><time="09:52:45.865+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="xmlanswerfile.cpp:578">
    <![LOG[Adding "C:\_SMSTaskSequence\drivers" to plug and play driver path.]LOG]!><time="09:52:45.943+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="xmlanswerfile.cpp:1894">
    <![LOG[Getting namespace "Microsoft-Windows-PnpCustomizationsWinPE" for architecture "amd64"]LOG]!><time="09:52:45.943+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="smiinterface.cpp:222">
    <![LOG[Writing configuration information to C:\_SMSTaskSequence\unattend.xml]LOG]!><time="09:52:45.943+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="smiinterface.cpp:860">
    <![LOG[Successfully saved configuration information to C:\_SMSTaskSequence\unattend.xml]LOG]!><time="09:52:45.959+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="smiinterface.cpp:925">
    <![LOG[Successfully initialized driver information]LOG]!><time="09:52:45.959+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="setupwindows.cpp:1205">
    <![LOG[Command line for extension .EXE is "%1" %*]LOG]!><time="09:52:45.959+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="commandline.cpp:228">
    <![LOG[Set command line: "C:\_SMSTaskSequence\Packages\LTC00011\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot]LOG]!><time="09:52:45.959+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924"
    file="commandline.cpp:731">
    <![LOG[Executing command line: "C:\_SMSTaskSequence\Packages\LTC00011\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot]LOG]!><time="09:52:45.959+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924"
    file="commandline.cpp:827">
    <![LOG[Process completed with exit code 31]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="commandline.cpp:1123">
    <![LOG[Windows Setup completed with exit code 31]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="setupwindows.cpp:1526">
    <![LOG[ReleaseSource() for C:\_SMSTaskSequence\Packages\LTC00011.]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="resolvesource.cpp:3564">
    <![LOG[reference count 1 for the source C:\_SMSTaskSequence\Packages\LTC00011 before releasing]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="resolvesource.cpp:3574">
    <![LOG[Released the resolved source C:\_SMSTaskSequence\Packages\LTC00011]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="resolvesource.cpp:3612">
    <![LOG[exitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,440)]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="setupwindows.cpp:440">
    <![LOG[Windows setup failed, code 31]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="3" thread="1924" file="setupwindows.cpp:440">
    <![LOG[setup.run(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,1650)]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="setupwindows.cpp:1650">
    <![LOG[Exiting with code 0x80004005]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="setupwindows.cpp:1696">
    <![LOG[Process completed with exit code 2147500037]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="commandline.cpp:1123">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="instruction.cxx:804">
    <![LOG[Failed to run the action: Setup Windows and ConfigMgr.
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="TSManager" context="" type="3" thread="1048" file="instruction.cxx:895">
    <![LOG[MP server http://Darwin.ltcharity.org.uk. Ports 80,443. CRL=false.]LOG]!><time="10:00:45.321+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5881">
    <![LOG[Setting authenticator]LOG]!><time="10:00:45.337+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5903">
    <![LOG[Set authenticator in transport]LOG]!><time="10:00:45.353+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:7734">
    <![LOG[Sending StatusMessage]LOG]!><time="10:00:45.434+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:4023">
    <![LOG[Setting message signatures.]LOG]!><time="10:00:45.436+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1295">
    <![LOG[Setting the authenticator.]LOG]!><time="10:00:45.444+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1325">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: Darwin.ltcharity.org.uk:80  CCM_POST /ccm_system/request]LOG]!><time="10:00:45.444+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:8604">
    <![LOG[Request was successful.]LOG]!><time="10:00:45.476+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:8939">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=-2147467259]LOG]!><time="10:00:45.476+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="10:00:45.476+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
    <![LOG[Clear local default environment]LOG]!><time="10:00:45.476+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:807">
    <![LOG[Let the parent group (Setup Operating System) decides whether to continue execution]LOG]!><time="10:00:45.491+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="instruction.cxx:1004">
    <![LOG[Let the parent group (Install Operating System) decide whether to continue execution]LOG]!><time="10:00:45.491+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="instruction.cxx:254">
    <![LOG[The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="10:00:45.491+480" date="03-25-2014" component="TSManager" context="" type="3" thread="1048" file="instruction.cxx:217">
    <![LOG[Failed to run the last action: Setup Windows and ConfigMgr. Execution of task sequence failed.
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="10:00:45.491+480" date="03-25-2014" component="TSManager" context="" type="3" thread="1048" file="engine.cxx:213">
    <![LOG[MP server http://Darwin.ltcharity.org.uk. Ports 80,443. CRL=false.]LOG]!><time="10:00:45.491+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5881">
    <![LOG[Setting authenticator]LOG]!><time="10:00:45.522+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5903">
    <![LOG[Set authenticator in transport]LOG]!><time="10:00:45.522+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:7734">
    <![LOG[Sending StatusMessage]LOG]!><time="10:00:45.539+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:4023">
    <![LOG[Setting message signatures.]LOG]!><time="10:00:45.539+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1295">
    <![LOG[Setting the authenticator.]LOG]!><time="10:00:45.539+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1325">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: Darwin.ltcharity.org.uk:80  CCM_POST /ccm_system/request]LOG]!><time="10:00:45.539+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:8604">
    <![LOG[Request was successful.]LOG]!><time="10:00:45.570+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:8939">
    <![LOG[Executing command line: X:\windows\system32\cmd.exe /k]LOG]!><time="10:03:20.975+480" date="03-25-2014" component="TSBootShell" context="" type="1" thread="776" file="bootshell.cpp:860">
    So according to this log "Windows setup failed, CODE 31", Which then produced the more generic 8004005 error.

  • Task Sequence Fails after Software Updates Install Step - Lenovo X240

    Hi All.
    I'm having a strange issue trying to run an OSD on Lenovo X240 machines. 
    After the Software Update step, it reboots as expected, then exits the task sequence and sends you to the windows logon screen.
    Review the SMSTS.log, it appears the reason is:
    Found network adapter "Intel(R) Dual Band Wireless-AC 7260" with IP Address 0.0.0.0.
    TSMBootstrap 24/07/2014 15:07:10
    1824 (0x0720)
    Found network adapter "Intel(R) Ethernet Connection I218-LM" with IP Address 0.0.0.0.
    TSMBootstrap 24/07/2014 15:07:10
    1824 (0x0720)
    Full log file:
    SMSTS.log
    If I remove the Software Updates step, the task sequence completes without any problems.
    Don't think it is a driver error, as above, every other step completes without issue. Other models use the same task sequence (including software updates step) without any problems.
    Any ideas? I'm completely stuck.
    Thanks!

    Looks like I am deploying KB2965788 which requires two restarts.
    Thanks all for your help.
    P.S. - I periodically update the base image with a build & capture to include the latest updates, so in the times between this I deploy the software updates as part of the task sequence.
    I've found the offline servicing to be very flaky, have attempted to use it many times and found it either a) doesn't apply the updates to the image b) corrupts the image.

  • Build and capture task sequence stops after apply windows updates

    Hi
    SCCM 2012 SP1 CU4. Deploying Windows 7 SP1.
    Pulling my hair out over this one. I successfully performed a build and capture installing some applications. When I choose to install Windows updates, the updates install, the system reboots then doesn't continue. Applications don't install, image isn't captured.
    I've tired using the default B&C TS and receive the same results. I've amended the TS to as follows, as suggested in a technet forum post: https://social.technet.microsoft.com/Forums/en-US/a535e509-fc6a-483c-bf24-7e2aa064e5b7/deploying-100-of-available-software-updates-during-a-task-sequence?forum=configmanagerosd
    Looking at smsts.log there's errors relating to not accepting the license agreement, but I didn't think this would stop the TS. 
    Can someone point out why the deployment stops?
    https://dl.dropboxusercontent.com/u/23479177/smsts-20141113-182413.log 
    Cheers

    This is very common scenario you´re having! :)
    For OSD and for Capture I always create myown Software Update Group, which lets me totally control, what updates goes to the image and which doesn´t. I then edit membership of update and tag or un-tag update to the group.
    I suggest you do the following:
    1. Create manual Computer record and add it to OSD Capture collection.
    2. Create SUG for OSD Capture and un-tag updates which are listed in KB2894518. But that might not be enough.
    3. Deploy TS to the OSD Capture collection.
    4. Create/modify virtual machine with MAC matching the computer record.
    5. Run PXE and hook Capture TS.

  • Rendering error using linked sequence in After Effects

    When I render out an After Effects Project with a linked sequence from Premiere, There are some frames that don't render. They are "missing media". These are only a few frames and very random. After rendering it out a second time, the missing Premiere frames were somewhere else. I use Media Encoder to render. I had to do a work around and render out the Premiere sequence first, put it into my After Effects Project and then render that again. Can someone help me with this dynamic link issue?
    For this project, i have to render in 50fps. I put both my After Effects and Premiere projects to 50fps. But the footage is not. Can that be the problem perhaps?

    Hi jstrawn,
    no, by render out i mean actually finishing off the project by exporting it to media encoder and rendering out a file. I am in After Effects and the linked sequence is refering to the sequences I made in Premiere Pro.
    As far as i know, you can only render and replace an After Effects Comp in Premiere. (vise versa would be great in my case but i couldnt find a render and replace function for premiere sequences in After Effects)
    By missing media, i mean the yellow screen you get when Premiere can not find your footage. It happens randomly and it seems as if dynamic link isn't working quite well in this case.
    in media encoder i set the rendering settings to QuickTime H.264 codec, 50fps, 1920x1080 and it renders out in .mov. All the comps in AE and Sequences in Premiere are slalso set to these settings.

  • Error in Task #10 (InitializeActivitySpaces) after fresh WCI 10gR3 install

    I've tried this several times now with the same results. I'm installing WCI 10gR3 on Windows 2003, Oracle 10gR3 XE, and WebLogic Application Server. I've run the install, setup the scripts, run through the configuration.
    But when I run the C:\bea\alui\ptportal\10.3.0\bin\diagnostic.bat, I get to Task#10 and it errors out. This is the error:
    Task 'InitializeActivitySpaces' Failed on Startup
    Task #10 (InitializeActivitySpaces) Step #2
    error: LoadActivitySpace problem: managers will not load.
    platform: Windows (Java)
    failure: FATAL: LoadActivitySpace problem: managers will not load.
    recommendation: RECOMMENDATION: Check that version.xml is located in the
    correct directory and is not corrupt.
    exception: XPException
    Fatal error loading lib file taglibJoinCommunityPageEditor:
    Unable to locate Tag Library meta data.
    message: Fatal error loading lib file taglibJoinCommunityPageEditor:
    Unable to locate Tag Library meta data.
    secondary exception: at
    com.plumtree.portaluiinfrastructure.tags.manager.TagLibManager.Intern
    alLoadLibFile(TagLibManager.java:460)
    FAILED TO INITIALIZE SYSTEM. YOU CANNOT PROGRESS BEYOND THIS POINT.
    ======= Diagnostic Run Complete =======
    Startup completion percentage: 62% (31 steps out of 50 complete)
    I have a C:\bea\alui\ptportal\10.3.0\version.xml file and it appears to be a valid XML file.
    Any ideas on what to check?
    Thanks

    The error looks like its an issue with loading one of the new tag libraries in 10gR3.
    My suggestion, if you have not done so already, open a support case and have a support engineer look at the issue.
    And the diagnostics tool should work even if you are deploying the Portal through Weblogic, provided you are not loading a custom tag library.

  • Task Sequence Failing after Stating Boot Image and Restart in WinPE - Windows XP to Windows 7

    Good Morning,
    I am trying to upgrade an XP Machine to Windows 7 (x86). I was using the boot image inbuilt with SCCM 2012 R2 but read that it wont work correcltly. I am using Windows PE 3.1 boot image to boot.
    The TS fails after trying to restart in Windows PE when staging the boot image.
    From the Logs in CCM\Logs\SMSTSLog
    I am still getting the same issue as when i am using the Boot image from ADK 8.1.
    Anybody has an idea on how to solve this issue ? I have read a workaround about replacing the bootsect from the boot image but funily i am using an older boot image.
    Kind Regards,
    Mathieu 

    http://support.microsoft.com/kb/2910552
    Torsten Meringer | http://www.mssccmfaq.de

  • Failed to run task sequence. Error occurred while starting the task sequence (0x8007000E)

    Hi there
    Patch Tuesday yesterday (10th June2014). As always we deploy new patches first to a test collection where Windows 7 updates automatically apply.
    Upon trying to rebuild any of the machines in this test collection, we were presented with the following error message:
    Failed to run task sequence.  Error occurred while starting the task sequence (0x8007000E)
    After searching about this, I found this page from Niall Brady, which explained the problem:
    http://www.niallbrady.com/2013/05/17/after-selecting-a-task-sequence-in-configuration-manager-2012-sp1-you-receive-threadtoresolveandexecutetasksequence-failed-code0x8007000e-in-smsts-log/
    So I removed some of the machines from the test Windows update collection, and as per the advice in the above link, the error was gone and those machines could be built successfully.
    So the problem is there were too many many policies downloaded (apps, packages and most of all updates) for the task sequence ram to store, hence the error.
    Now...
    ...I have a question.
    The next logical step to my mind is to patch our OS image with all missing patches, so these do not have to be downloaded at build time. Niall mentions this as one of the resolutions to this issue.
    However there seems to be some confusion over whether this would actually make a difference.
    I read through this link:
    http://social.technet.microsoft.com/Forums/en-US/7e597b44-2586-4063-b6d0-cec48a7c11c7/sccm-2012-task-sequence-failure-0x8007000e?forum=configmanagerosd
    There's seems to be no consensus on this.
    Is SCCM 2012 clever enough to - when the task sequence is first started - to download ONLY the updates (policies) it detects as NOT present in the OS image...
    or
    Will it simply try to download policies for ALL items deployed to it, whether the updates are present in the OS image or not?
    I will be disappointed if SCCM 2012 SP1 CU2 isn't clever enough to only download policies at build time for the apps, packages and updates it detects as needed.
    I'd be grateful for some clarity on this.
    Regards,
    John, Glasgow.

    Hi Jason
    Thank you for replying, I appreciate it.
    1) We currently have 15 or 16 software update groups for Office updates, dating back a month or two. The latest software update group contains all the patches in the previous software update groups plus the patches released on 10th June. Do you recommend
    deleting all but the latest software update group?
    2) I'm almost reluctant to ask this, but based on what you have advised, is it the case that when the task sequence executes, it will download policies for each update in each software update group regardless of whether it has already downloaded a policy
    for an update in a previous software update group? So in effect it's downloading policies (for updates) it has already downloaded?
    3) I'm not clear on why there would be no policy for an image; in Niall Brady's informative page on the 8007000E error, he writes the following:
    "The reason it has run of space could be due to four possibilites: too many applications, too many Windows updates, too many Task Sequence steps, too many referenced packages'.
    Can you shed some light on why there isn't a policy for an image?
    Thanks again for replying,
    John.

  • SCCM 2012 - OSD Task Sequence Error 0x80091007

    When deploying the OSD to a laptop model the TS is failing, see below from Status Message Viewer:
    The task sequence execution engine failed executing the action (Apply E6220 Driver Package) in the group (PostInstall) with the error code 2148077575
    Action output: urce, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3217)
    ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3122)
    TS::Utility::ResolveSource( pszPackageId, sSource ), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,472)
    pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,380)
    Exiting with return code 0x80091007
    Hash could not be matched for the downloded content. Original ContentHash = EB2A940227C7043DDDCE0985EB37CBB650245F47F12ACD48C936521F5CECAFED, Downloaded ContentHash = 6F4ED0BD9ECC46712E6160BF681ED3785097D95A43652424FB97E12EB1EAF8E3
    Failed to determine the driver source location. Code 0x80091007
    Failed to provision driver. Code 0x80091007. The operating system reported error 2148077575: The hash value is not correct. 
    I have redistributed the Driver packages to the DP's but still no luck - does anyone have any idea's?
    Thanks
    MCTS | MCITP | MCSA

    Below is the whole thread from Expert-sex-change.com: 
    SCCM OS deployment error (0x80091007)
    Asked by: MoritzCSA
    We are getting Error on one of your Primary Child site when deploying a XP Install Package.
    In the Advertisment Status we are getting following errors:
    The task sequence execution engine failed executing the action
    (Apply Operating System Image) in the group () with the error code
    2148077575
    Action output: zSource, sSourceDirectory, dwFlags, hUserToken,
    pszUserName, pszUserPassword), HRESULT=80091007
    (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3130)
    ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0),
    HRESULT=80091007
    (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3031)
    TS::Utility::ResolveSource( this->packageID, this->packagePath,
    TS::Utility::ResolveSourceFlags::PersistContents ),
    HRESULT=80091007
    (e:\nts_sms_fre\sms\client\osdeployment\applyos\installscripted.cpp,
    160)
    installer.install(), HRESULT=80091007
    (e:\nts_sms_fre\sms\client\osdeployment\applyos\installscripted.cpp,
    632)
    Entering ReleaseSource() for
    C:\_SMSTaskSequence\Packages\GID00004
    The user tries to
    release a source directory
    C:\_SMSTaskSequence\Packages\GID00004 that is either already
    released or we have not connected to it InstallScripted(
    g_InstallPackageID, g_ImageIndex, targetVolume,
    g_ConfigPackageID, g_ConfigFileName ), HRESULT=80091007
    (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,397).
    The operating system reported error 2148077575: The hash value is
    not correct.
    The task sequence execution engine aborted execution for a failure
    of the action (Apply Operating System Image) in the group (). The
    operating system reported error 2148077575: The hash value is not
    correct.
    The task sequence execution engine failed execution of a task
    sequence. The operating system reported error 2148077575: The
    hash value is not correct.
    The task sequence manager could not successfully complete
    execution of the task sequence. A failure exit code of 16389 was
    returned.
    appreciate any help
    IMAG0020.jpg
    747 KBscreenshot off error on Client Computer when deploying OS
    2010-02-05 at 04:39:43ID: 25117354TopicsMS System Center ,Deployment Software for DevelopmentParticipating Experts3Points0Comments9
    Request Attention
    Answers
    EXPERT COMMENT
    by: NJComputerNetworksPosted on 2010-02-05 at 05:29:05ID: 26494779
    1) enable f8 boot console on your boot image:  http://www.windows-noob.com/forums/index.php?/topic/546-how-can-i-troubleshoot-windows-pe-booting-in-sccm/  this will get you to a command prompt on the client
    2) look at the smsts.log for exactly why your client is failing osd:  http://blogs.technet.com/inside_osd/archive/2007/12/13/troubleshooting-tips.aspx
    3) also look at the reports for information as to why your OSD is failing:  http://blogs.technet.com/inside_osd/archive/2007/12/13/troubleshooting-tips.aspx
    AUTHOR COMMENT
    by: MoritzCSAPosted on 2010-02-05 at 05:39:33ID: 26494871
    Hi,
    Its not the Boot image what has problems. Its one single OS package as others workjust fine
    EXPERT COMMENT
    by: NJComputerNetworksPosted on 2010-02-05 at 06:01:11ID: 26495086
    lol... ok... but enabling F8 will allow you to get to the smsts.log which should contain some more information about why the single OS package is failing.
    EXPERT COMMENT
    by: JonLambertPosted on 2010-02-08 at 01:43:35ID: 26512090
    OK, it looks like (as descripted in the logs) that the Hash Value for the package GID00004 is not correct.
    I've seen this before with Boot WIMS, if GID00004 is a boot WIM package, then try creating a new Boot Wim, deploying it to the relevant DPs, assigning it to th TS and try again.
    If GID00004 is not a Boot WIM, then try updating the package, and keep an eye on DistMgr.log to ensure it get's distributed Ok.
    AUTHOR COMMENT
    by: MoritzCSAPosted on 2010-02-09 at 07:13:55ID: 26524885
    Hi have recreated the OS Install Packlage and have distributed it again to the Primary Child site. Still the same issue as for example the same OS in English is running fine. GID00004 was an OS Install Package.
    I have the log file from the F8 boot atached
    smsts-20100210-001651.log
    976 KBlog
    smsts.log
    391 KBlog2
    ADMINISTRATIVE COMMENT
    by: TheLearnedOnePosted on 2010-03-03 at 18:54:29ID: 27299334
    MoritzCSA,
    After 21 days without comment, it is time for you to finalize this old question -- accept an answer, split points, or get a refund.  Please be a responsible EE Member and maintain your open questions! Click here to see your options: http://www.experts-exchange.com/help.jsp#hi331
    EXPERTS,
    I need your help.  Please post your closing recommendations within a few days.  If you do not respond, I may need to assume that no correct answer was provided.
    TheLearnedOne
    Experts-Exchange Cleanup Volunteer
    EXPERT COMMENT
    by: JonLambertPosted on 2010-03-03 at 19:17:39ID: 27299526
    OK, now the package with an hash error is GID0002A .. which is the OS Install Package, Check the source directory for files with odd characters, or extremely long directory paths .. this can sometime cause a hash-check mismatch.
    Hash could not be matched for the downloded content. Original ContentHash = A9173DC49D149170C0F7F5526154AC4381ED0DC0, Downloaded ContentHash = 88601C0BA124401EA13790D2F318AF04CB283DD1      ApplyOperatingSystem     
    9/02/2010 3:29:21 PM      1680 (0x0690)
    ACCEPTED SOLUTION
    by: MoritzCSAPosted on 2010-03-04 at 00:23:07ID: 27300766
    I have change the OS installation to not download the package. After this change it works fine without issues.
    0
    excellent
    Save to Personal Knowledgebase
    EXPERT COMMENT
    by: DSS-RMPosted on 2010-10-17 at 07:14:56ID: 33923836
    Update the distribution points of the package that was failing. I have had this same problem and a distribution point update will fix it.

  • Task Sequence packages not installing after upgrade to R2

    Hi all
    As the title suggests, I've upgraded my SCCM 2012 server from SP1 to R2. The OSD Task Sequences reach the stage where the client is installed, and ends after this point. However there are several software packages after this step that it is seemingly skipping
    entirely now.
    Any idea why this might be?
    Thanks

    Ok,
    After banging my head for a few days with that issue i saw the light at the end of the tunnel ( an not the
    train) today.
    Long story short, the culprit was the boot image. I upgraded to 6.3 and everything in my TSs is working as
    it should.
    Here are the details:
    The recall my issue, after upgrading SCCM from SP1 to R2, none of the software packages were getting installed
    in a Task sequence. A TS runs up to the installation of the SCCM agent and then it quits.
    Looking at the log file in  C:\Windows\System32\ccm\logs\smstslog I found the following errors:
    Resuming Task Sequence in Full OS TSMBootstrap
    Failed to get the environment key. TSMBootstrap
    Failed to resume task sequence (0x800700EA).
    Exiting with return code 0x800700EA TSMBootstrap
    Earlier i mentioned that my boot images did not get updated as part of the site upgraded, so i went and updated
    them to version 6.3 and after making sure it got deployed in a TS to make it available through PXE, my problem was gone.
    this post helped me tremendously to realized that the boot image was the issue:
    https://social.technet.microsoft.com/Forums/en-US/a793071d-1a3b-4b68-b6de-6d8c1a1fda0f/failed-to-get-the-environment-key-smstslog?forum=configmanagerosd 
    Mario.

  • Fails to run Task Sequence (error 0x80008014)

    Hello,
    I am facing a strange problem.
    The environment is a SCCM 2007 SP2 system.
    I am using Task sequences for many years now. For OS deployment and deploying multi application updates.
    packages / programs are configured with admin rights and whether or "no user is logged on"
    I integrated these packages /programs in a os deployment task. This was successful.
    When using the same packages / programs in a task sequence for deploying these software packages the ts faisl.
    Checking exexmgr.log I can see the following message "TS Step required to run in user context, targeted to user or requiring user input. Rejecting." Which I don't understand at all.
    I stripped down the ts to only one application to install. The error is the same.
    In other logs I found these error messages:
    Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\System Health Agent. Error code 0x80070002
    failed to invoke execution manager to install software for package id
    Í checked the SCCM client on the SCCM server and the one which is installed. Both are version 4.00.6487.2000.
    Thanks for your feedback on this,
    Thanks,
    Andy

    ==========[ TsProgressUI started in process 15076 ]========== TsProgressUI 16.09.2014 11:01:37 18136 (0x46D8)
    Registering COM classes TsProgressUI 16.09.2014 11:01:37 18136 (0x46D8)
    sbModulePath = C:\WINDOWS\SysWOW64\CCM\TsProgressUI.exe TsProgressUI 16.09.2014 11:01:37 18136 (0x46D8)
    Shutdown complete. TsProgressUI 16.09.2014 11:01:37 18136 (0x46D8)
    Process completed with exit code 0 TSLauncher 16.09.2014 11:01:37 17496 (0x4458)
    Successfully registered TS Progress UI. TSLauncher 16.09.2014 11:01:37 17496 (0x4458)
    C:\_SMSTaskSequence does not exist TSLauncher 16.09.2014 11:01:37 17496 (0x4458)
    Updated security on object C:\_SMSTaskSequence. TSLauncher 16.09.2014 11:01:37 17496 (0x4458)
    Starting Task Sequence Manager Service. TSLauncher 16.09.2014 11:01:37 17496 (0x4458)
    Modifying TS Manager Service to auto start. TSLauncher 16.09.2014 11:01:37 17496 (0x4458)
    Starting the TS Manager Service. TSLauncher 16.09.2014 11:01:37 17496 (0x4458)
    Successfully intialized Logging for TS Manager. TSManager 16.09.2014 11:01:37 18688 (0x4900)
    Commandline: C:\WINDOWS\SysWOW64\CCM\TSManager.exe /service TSManager 16.09.2014 11:01:37 18688 (0x4900)
    Successfully registered Task Sequencing COM Interface. TSManager 16.09.2014 11:01:37 18688 (0x4900)
    Executing as a service TSManager 16.09.2014 11:01:37 18688 (0x4900)
    Waiting for the TS Manager Service to start. TSLauncher 16.09.2014 11:01:37 17496 (0x4458)
    Started ServiceMain TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Task Sequence Manager executing as service main thread TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Waiting for CcmExec service to be fully operational TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    CcmExec service is up and fully operational TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Pause request for Software Distribution TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Checking if CCM component SoftwareDistribution is paused TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Component is not currently paused... TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Pausing CCM component SoftwareDistribution TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Task Sequencing Manager Service successfully started. TSLauncher 16.09.2014 11:01:37 17496 (0x4458)
    Task Sequence Launcher finished execution successfully! TSLauncher 16.09.2014 11:01:37 17496 (0x4458)
    Paused notification received for Software Updates/Distribution TSManager 16.09.2014 11:01:37 14984 (0x3A88)
    Software Distribution is now paused. TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Saving SoftwareDistribution pause cookie: 22591 TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Pause request for Software Updates TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Checking if CCM component SoftwareUpdates is paused TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Component is not currently paused... TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Pausing CCM component SoftwareUpdates TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Paused notification received for Software Updates/Distribution TSManager 16.09.2014 11:01:37 14984 (0x3A88)
    Software Updates is now paused. TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Saving SoftwareUpdates pause cookie: 22591 TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Attempting to pause System Health Agent TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Checking if CCM component System Health Agent is paused TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Failed to pause component System Health Agent (80040200) TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Remediating TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Error getting system isolation info. Code 8027000C TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Remediation failed. Code 8027000C TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Remediation failed with error code 8027000C TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Parsing task sequence . . . TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Task sequence schema version is 3.00 TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Current supported schema version is 3.10 and 3.00 TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Starting Task Sequence Engine . . .  TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    **************************************************************************** TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Set a global environment variable _SMSTSNextInstructionPointer=0 TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Set a global environment variable _SMSTSInstructionTableSize=1 TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Set a global environment variable SMSTSRebootRequested= TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Set a global environment variable SMSTSRebootDelay= TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Set a global environment variable SMSTSRebootMessage= TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Set a global environment variable SMSTSRebootReason= TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Set a global environment variable SMSTSRetryRequested= TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    The task execution engine started execution TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Sending status message . . . TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Send a task execution status message SMS_TSExecution_TaskSequenceStartInfo TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Registry entry 'Certificate Store' is either missing or empty. TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    The 'Certificate Store' is empty in the registry, using default store name 'MY'. TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Registry entry 'Certificate Selection Criteria' is either missing or empty. TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Registry entry 'Select First Certificate' value is 1. TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    The 'Certificate Selection Criteria' was not specified, counting number of certificates  present in 'MY' store of 'Local Computer'. TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    1 certificate(s) found in the 'MY' certificate store. TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Only one certificate present in the certificate store. TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Client SSL is enabled. The current state is 0x95. TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    The certificate issued to 'clientname' has 'Client Authentication' capability. TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Using the certificate issued to 'clientname'. TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Formatted header: TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:eb79550c-aad9-4ed7-879e-74886b7b5aca</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2014-09-16T09:01:37Z</SentTime><Protocol>http</Protocol><Body
    Type="ByteRange" Offset="0" Length="2140"/><Hooks><Hook2 Name="clientauth"><Property Name="PublicKey">0602000000A40000525341310008000001000100AD1FCB191AF20B63A8DB91BE3968E2225100EA1EAFDD751120923C4A4332AFFE3916CDE1AE13AC891FBB7DF1BBBBCC236AD4F5689F7A03DB79379838FD043DFA8AEC3DFB5FAA24984292CDFB9A8794F4C104CF2A6B0C9DDAF86D453B25BC246E8273922C66D885F3A8BF5C08B05E90200A970A2371B77161CACBA2843BC6A973CED2ED61E84DAE2F78491D44F6B88D69C72BC815E6B31FC3C8B2D095537920F3A44893D396CAD6CBA5700416F39067A138B26155B1A3621F0619C272CEC54EDFF3EE978A3A824D8EA0053ABB1E2FC296D8FF862B47414BDCEED687B8303B0EBDD4D25A4E591AB530CBD5D5C1045A8A535F3BC467C99237B46CA2C0E2E948709A</Property><Property
    Name="ClientIDSignature">A262419FE563595B69872C1E76F91359EF41789818D1377769F25576C873871FE3E97CD4D3D2425054D969F8735CA0BBF71070F98E97E7171DA2D2B4C8352C863E368409CEF0AB6096A2E92F9E123B5866710B28572886FCC4B1F36F0D80420AAE1DE013CE62A687B2226A464889376EF9FA7B835E2003A77881F3D527669765D587B45BE9C01103C919BE355FF56787D280AE3A72F4DB976757191FAC4E391BEF1AAD9BD3FE46A83C8E6167EB1D6FAF6109682566A27D1097B27143A50522B4A9FD9514565901A2BDCE437BD097E23710904DA839456519E2A2F264072633831AB37C509CF43312A1ECEACF6C82914D7F40BC6645EEED57C3ABE41C23E03B39</Property><Property
    Name="PayloadSignature">5D6D17BC683415752B8CD07753CE0EC1D81FB69D4E78002B17D8C9B9C7A821AC255729C79F4B3E3AE1F70E7ECBDD09EC813B5A6A393FC67B742A1F4BF9EE6CB9C8A67F21B6521092F0E48E37686C5ACE66E62AB77204A9396F46E72CB03C2DB5A516BAF62AB1FA6B33D5E365DBBF23485856872BD185D62E9BF4995523BBC892B32141A0345A0A47FC2666B9129B09359854E9C5AEB617359B6C52DD7197D29FF152AD36FF05607E4008D9569AE9F51C2181C32B217C52AFFD036F855AEA43F44871B1CD919D6E04A5CD02DB1DCD4E7D422E4DE066BD1135C176031022D74F56E3AD688DDFCEEC8BF1DDCF8F10FD0BA39529539D69B61DD682817D528F25D358</Property></Hook2></Hooks><Payload
    Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
     TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Start executing an instruciton. Instruction name: Install 7-Zip 9.20 x64. Instruction pointer: 0 TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Set a global environment variable _SMSTSCurrentActionName=Install 7-Zip 9.20 x64 TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Set a global environment variable _SMSTSNextInstructionPointer=0 TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Set a local default variable _SMSSWDProgramName TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Set a global environment variable _SMSTSLogPath=C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Expand a string: smsswd.exe /pkg:D010015A /install /basevar: /continueOnError: TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Expand a string:  TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Start executing the command line: smsswd.exe /pkg:D010015A /install /basevar: /continueOnError: TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    !--------------------------------------------------------------------------------------------! TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Expand a string: FullOS TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    Executing command line: smsswd.exe /pkg:D010015A /install /basevar: /continueOnError: TSManager 16.09.2014 11:01:37 7740 (0x1E3C)
    =======================[ smsswd.exe ] ======================= InstallSoftware 16.09.2014 11:01:38 23284 (0x5AF4)
    PackageID = 'D010015A' InstallSoftware 16.09.2014 11:01:38 23284 (0x5AF4)
    BaseVar   = '', ContinueOnError='' InstallSoftware 16.09.2014 11:01:38 23284 (0x5AF4)
    SwdAction = '0002' InstallSoftware 16.09.2014 11:01:38 23284 (0x5AF4)
    SoftDist paused cookie = 22591 InstallSoftware 16.09.2014 11:01:38 23284 (0x5AF4)
    Successfully connected to "\\DistributionServer\SMSPKGD$\D010015A" InstallSoftware 16.09.2014 11:01:38 23284 (0x5AF4)
    SMS PkgID 'D010015A' resolved to location '\\DistributionServer\SMSPKGD$\D010015A\' InstallSoftware 16.09.2014 11:01:38 23284 (0x5AF4)
    Start to compile TS policy InstallSoftware 16.09.2014 11:01:38 23284 (0x5AF4)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace InstallSoftware 16.09.2014 11:01:38 23284 (0x5AF4)
    End TS policy compilation InstallSoftware 16.09.2014 11:01:38 23284 (0x5AF4)
    Start to evaluate TS policy with lock InstallSoftware 16.09.2014 11:01:38 23284 (0x5AF4)
    Updating settings in
    \\clientname\root\ccm\policy\machine\actualconfig InstallSoftware 16.09.2014 11:01:38 23284 (0x5AF4)
    Machine RequestedConfig policy instance(s) : 1978 InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Added/updated setting 'ccm_softwaredistribution:adv_advertisementid=d012054b:pkg_packageid=d010015a:prg_programid=ts_install'. InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Added/updated setting 'inventorydataitem:dataitemid={0fc01f3e-7e62-46fd-ab98-926a2c724684}:itemclass=filesystemfile:namespace=\\.\root\ccm\invagt'. InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Added/updated setting 'inventorydataitem:dataitemid={33d85ab7-9913-4ba2-b887-0c7427bc0a2d}:itemclass=filesystemfile:namespace=\\.\root\ccm\invagt'. InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Added/updated setting 'inventorydataitem:dataitemid={3a27449d-1b79-40b5-970e-54655fc8dc67}:itemclass=filesystemfile:namespace=\\.\root\ccm\invagt'. InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Added/updated setting 'inventorydataitem:dataitemid={516688f4-d6b8-488f-8461-208e0847da93}:itemclass=win32reg_addremoveprograms:namespace=\\localhost\root\cimv2'. InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Added/updated setting 'inventorydataitem:dataitemid={73719729-c4e9-4132-a3d6-b07a322c41c1}:itemclass=win32reg_addremoveprograms64:namespace=\\localhost\root\cimv2'. InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Added/updated setting 'inventorydataitem:dataitemid={94d99a25-e6aa-4cc2-9a73-dc678f47810a}:itemclass=win32reg_smsguestvirtualmachine:namespace=\\.\root\cimv2'. InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Added/updated setting 'inventorydataitem:dataitemid={ac92faf2-88c1-4cd1-b30d-9a1ccf2fe562}:itemclass=win32reg_smsguestvirtualmachine64:namespace=\\.\root\cimv2'. InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Added/updated setting 'inventorydataitem:dataitemid={d0babbf8-42d3-4a6d-a905-0679ed466add}:itemclass=filesystemfile:namespace=\\.\root\ccm\invagt'. InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Added/updated setting 'inventorydataitem:dataitemid={fe169e66-dfbd-432a-8880-8300fd5854cd}:itemclass=filesystemfile:namespace=\\.\root\ccm\invagt'. InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Raising event:
    instance of CCM_PolicyAgent_SettingsEvaluationComplete
     ClientID = "GUID:eb79550c-aad9-4ed7-879e-74886b7b5aca";
     DateTime = "20140916090139.887000+000";
     PolicyNamespace = "\\\\clientname\\root\\ccm\\policy\\machine\\actualconfig";
     ProcessID = 17988;
     ThreadID = 23284;
     InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Successfully submitted event to the Status Agent. InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    End TS policy evaluation InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Policy evaluation initiated InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Waiting for policy to be compiled in 'root\ccm\policy\machine' namespace  InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Verified policy is compiled in 'root\ccm\policy\machine' namespace InstallSoftware 16.09.2014 11:01:39 23284 (0x5AF4)
    Failed to invoke Execution Manager to Install Software for PackageID='D010015A' ProgramID='ts_install' AdvertID='D012054B' hr=0x80008014 InstallSoftware 16.09.2014 11:01:48 23284 (0x5AF4)
    InstallSoftware failed, hr=0x80008014 InstallSoftware 16.09.2014 11:01:48 23284 (0x5AF4)
    Install Software failed, hr=0x80008014 InstallSoftware 16.09.2014 11:01:48 23284 (0x5AF4)
    Process completed with exit code 2147516436 TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    !--------------------------------------------------------------------------------------------! TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Failed to run the action: Install 7-Zip 9.20 x64.
    Unknown error (Error: 80008014; Source: Unknown) TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Sending status message . . . TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Send a task execution status message SMS_TSExecution_ActionFailError TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Registry entry 'Certificate Store' is either missing or empty. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    The 'Certificate Store' is empty in the registry, using default store name 'MY'. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Registry entry 'Certificate Selection Criteria' is either missing or empty. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Registry entry 'Select First Certificate' value is 1. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    The 'Certificate Selection Criteria' was not specified, counting number of certificates  present in 'MY' store of 'Local Computer'. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    1 certificate(s) found in the 'MY' certificate store. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Only one certificate present in the certificate store. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    The certificate issued to 'clientname' has 'Client Authentication' capability. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Using the certificate issued to 'clientname'. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Formatted header: TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:eb79550c-aad9-4ed7-879e-74886b7b5aca</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2014-09-16T09:01:48Z</SentTime><Protocol>http</Protocol><Body
    Type="ByteRange" Offset="0" Length="4248"/><Hooks><Hook2 Name="clientauth"><Property Name="PublicKey">0602000000A40000525341310008000001000100AD1FCB191AF20B63A8DB91BE3968E2225100EA1EAFDD751120923C4A4332AFFE3916CDE1AE13AC891FBB7DF1BBBBCC236AD4F5689F7A03DB79379838FD043DFA8AEC3DFB5FAA24984292CDFB9A8794F4C104CF2A6B0C9DDAF86D453B25BC246E8273922C66D885F3A8BF5C08B05E90200A970A2371B77161CACBA2843BC6A973CED2ED61E84DAE2F78491D44F6B88D69C72BC815E6B31FC3C8B2D095537920F3A44893D396CAD6CBA5700416F39067A138B26155B1A3621F0619C272CEC54EDFF3EE978A3A824D8EA0053ABB1E2FC296D8FF862B47414BDCEED687B8303B0EBDD4D25A4E591AB530CBD5D5C1045A8A535F3BC467C99237B46CA2C0E2E948709A</Property><Property
    Name="ClientIDSignature">A262419FE563595B69872C1E76F91359EF41789818D1377769F25576C873871FE3E97CD4D3D2425054D969F8735CA0BBF71070F98E97E7171DA2D2B4C8352C863E368409CEF0AB6096A2E92F9E123B5866710B28572886FCC4B1F36F0D80420AAE1DE013CE62A687B2226A464889376EF9FA7B835E2003A77881F3D527669765D587B45BE9C01103C919BE355FF56787D280AE3A72F4DB976757191FAC4E391BEF1AAD9BD3FE46A83C8E6167EB1D6FAF6109682566A27D1097B27143A50522B4A9FD9514565901A2BDCE437BD097E23710904DA839456519E2A2F264072633831AB37C509CF43312A1ECEACF6C82914D7F40BC6645EEED57C3ABE41C23E03B39</Property><Property
    Name="PayloadSignature">1705FB90096C88A5F7D23FF3D8A29A1431E0E4D8F2485051440489CCC67ABF99D1F4D88E387A8142238037318798E37CE8BC77D5F15F362031823E48A4E3AF22E2475C8C1E13E72B188183265E3214954E7CF69E4D4972B308358621DEC778AA63D3C40E5A4C020F78FA89391F0E6A75D59DDF8AADD7AAA509FBAE61EEF239FEA55066E739301C7BDB80C3562239F099CFA3B74427627323132419E77170182F50DDF2021CC14D62BD05EA32D38FEEEA665088F79334A980886364ED8901A8BD703C5C9DD529723DDE8516CF14ED1785E3173F6A8D08E1CBB444191155D7115CC0CB8398A9D21CDA95513F19448F24212E179503F0F35BAB6DBE868DA7BE6132</Property></Hook2></Hooks><Payload
    Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
     TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Set a global environment variable _SMSTSLastActionRetCode=-2147450860 TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Clear local default environment TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Failed to run the action: Install 7-Zip 9.20 x64. Execution has been aborted TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Sending status message . . . TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Send a task execution status message SMS_TSExecution_ActionAbortExecutionError TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Registry entry 'Certificate Store' is either missing or empty. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    The 'Certificate Store' is empty in the registry, using default store name 'MY'. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Registry entry 'Certificate Selection Criteria' is either missing or empty. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Registry entry 'Select First Certificate' value is 1. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    The 'Certificate Selection Criteria' was not specified, counting number of certificates  present in 'MY' store of 'Local Computer'. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    1 certificate(s) found in the 'MY' certificate store. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Only one certificate present in the certificate store. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    The certificate issued to 'clientname' has 'Client Authentication' capability. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Using the certificate issued to 'clientname'. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Formatted header: TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:eb79550c-aad9-4ed7-879e-74886b7b5aca</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2014-09-16T09:01:48Z</SentTime><Protocol>http</Protocol><Body
    Type="ByteRange" Offset="0" Length="2208"/><Hooks><Hook2 Name="clientauth"><Property Name="PublicKey">0602000000A40000525341310008000001000100AD1FCB191AF20B63A8DB91BE3968E2225100EA1EAFDD751120923C4A4332AFFE3916CDE1AE13AC891FBB7DF1BBBBCC236AD4F5689F7A03DB79379838FD043DFA8AEC3DFB5FAA24984292CDFB9A8794F4C104CF2A6B0C9DDAF86D453B25BC246E8273922C66D885F3A8BF5C08B05E90200A970A2371B77161CACBA2843BC6A973CED2ED61E84DAE2F78491D44F6B88D69C72BC815E6B31FC3C8B2D095537920F3A44893D396CAD6CBA5700416F39067A138B26155B1A3621F0619C272CEC54EDFF3EE978A3A824D8EA0053ABB1E2FC296D8FF862B47414BDCEED687B8303B0EBDD4D25A4E591AB530CBD5D5C1045A8A535F3BC467C99237B46CA2C0E2E948709A</Property><Property
    Name="ClientIDSignature">A262419FE563595B69872C1E76F91359EF41789818D1377769F25576C873871FE3E97CD4D3D2425054D969F8735CA0BBF71070F98E97E7171DA2D2B4C8352C863E368409CEF0AB6096A2E92F9E123B5866710B28572886FCC4B1F36F0D80420AAE1DE013CE62A687B2226A464889376EF9FA7B835E2003A77881F3D527669765D587B45BE9C01103C919BE355FF56787D280AE3A72F4DB976757191FAC4E391BEF1AAD9BD3FE46A83C8E6167EB1D6FAF6109682566A27D1097B27143A50522B4A9FD9514565901A2BDCE437BD097E23710904DA839456519E2A2F264072633831AB37C509CF43312A1ECEACF6C82914D7F40BC6645EEED57C3ABE41C23E03B39</Property><Property
    Name="PayloadSignature">47B0130E722BA570201F17D23C59E8E8A1161BE57C5D606CDC1892392BA3A1040E851C6F82C19D39D1414A3E5D954AE8B99A171FC695D9815BA9C3B1A3BD1F3FE9F19F45C434D2BE86177548347D1647E75432FE452369E93CEF88C2F20FF7AE14F006EA24AC3BECAF5F5C81CC2F9D0BB088F3F2D50F7C6AA7ED6B131514F25A0B285D7A47C0535EF78AD85A2E054D8801B6950B6866FF63F08BD77EDF42137830EA5518B9C3865715366FD86ED5F17C27D0A2C19632E1EE1822C5C3DCF5F473D26548FD5980A79831441EF4E625DFA9FE96CBF887847346845620BBED5E5F7455ECB6738855A7AFAF40ECB1271C089EB40825FA10EE03F4F4A71F632C6BFE41</Property></Hook2></Hooks><Payload
    Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
     TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Failed to run the last action: Install 7-Zip 9.20 x64. Execution of task sequence failed.
    Unknown error (Error: 80008014; Source: Unknown) TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Sending status message . . . TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Send a task execution status message SMS_TSExecution_TaskSequenceFailError TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Registry entry 'Certificate Store' is either missing or empty. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    The 'Certificate Store' is empty in the registry, using default store name 'MY'. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Registry entry 'Certificate Selection Criteria' is either missing or empty. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Registry entry 'Select First Certificate' value is 1. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    The 'Certificate Selection Criteria' was not specified, counting number of certificates  present in 'MY' store of 'Local Computer'. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    1 certificate(s) found in the 'MY' certificate store. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Only one certificate present in the certificate store. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    The certificate issued to 'clientname' has 'Client Authentication' capability. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Using the certificate issued to 'clientname'. TSManager 16.09.2014 11:01:48 7740 (0x1E3C)
    Formatted header: TSManager 16.09.2014 11:01:49 7740 (0x1E3C)
    <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:eb79550c-aad9-4ed7-879e-74886b7b5aca</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2014-09-16T09:01:49Z</SentTime><Protocol>http</Protocol><Body
    Type="ByteRange" Offset="0" Length="2176"/><Hooks><Hook2 Name="clientauth"><Property Name="PublicKey">0602000000A40000525341310008000001000100AD1FCB191AF20B63A8DB91BE3968E2225100EA1EAFDD751120923C4A4332AFFE3916CDE1AE13AC891FBB7DF1BBBBCC236AD4F5689F7A03DB79379838FD043DFA8AEC3DFB5FAA24984292CDFB9A8794F4C104CF2A6B0C9DDAF86D453B25BC246E8273922C66D885F3A8BF5C08B05E90200A970A2371B77161CACBA2843BC6A973CED2ED61E84DAE2F78491D44F6B88D69C72BC815E6B31FC3C8B2D095537920F3A44893D396CAD6CBA5700416F39067A138B26155B1A3621F0619C272CEC54EDFF3EE978A3A824D8EA0053ABB1E2FC296D8FF862B47414BDCEED687B8303B0EBDD4D25A4E591AB530CBD5D5C1045A8A535F3BC467C99237B46CA2C0E2E948709A</Property><Property
    Name="ClientIDSignature">A262419FE563595B69872C1E76F91359EF41789818D1377769F25576C873871FE3E97CD4D3D2425054D969F8735CA0BBF71070F98E97E7171DA2D2B4C8352C863E368409CEF0AB6096A2E92F9E123B5866710B28572886FCC4B1F36F0D80420AAE1DE013CE62A687B2226A464889376EF9FA7B835E2003A77881F3D527669765D587B45BE9C01103C919BE355FF56787D280AE3A72F4DB976757191FAC4E391BEF1AAD9BD3FE46A83C8E6167EB1D6FAF6109682566A27D1097B27143A50522B4A9FD9514565901A2BDCE437BD097E23710904DA839456519E2A2F264072633831AB37C509CF43312A1ECEACF6C82914D7F40BC6645EEED57C3ABE41C23E03B39</Property><Property
    Name="PayloadSignature">607C65C61B54F43AEEF5C245F9A34E3E7E4989F4B070E37DD6A1FBF5482C940A22298E8075140D660E6F4C4387C2E04F381D2415DC9E4DA98C4C09832B54114570C68F93C88E3C52B095066F216943865A1B4F2D8A0C5AE21872E307E1C199167827A67EFE5DE5916E3AB62A1CA812906C7F408E84AE9BCEAF475408B46FB52315C7EB6C202E5B027F89746D9F306997273D5FD0311EFF82C0AC22608565555EBA20BEC0D0BFF661F14829AD9C59367AE0042DCDD1828C571BDAB5383A86AFF26C3D93481B982967DEF4B25D51E9A2F91A9E037C4D413399D26CFC5EB6B2D31CC3CF10DFF5AF82A7E2E4F52B597CBC96C2666199EE37ABD027F74D7BC26F6D36</Property></Hook2></Hooks><Payload
    Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
     TSManager 16.09.2014 11:01:49 7740 (0x1E3C)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 16.09.2014 11:01:50 7740 (0x1E3C)
    **************************************************************************** TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    Task sequence execution failed with error code 80004005 TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    Cleaning Up. Removing Authenticator TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    Cleaning up task sequence folder TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    File "C:\_SMSTaskSequence\TSEnv.dat" does not exist. (Code 0x80070002) TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    Successfully unregistered Task Sequencing Environment COM Interface. TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    Executing command line: "C:\WINDOWS\SysWOW64\CCM\TsProgressUI.exe" /Unregister TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    ==========[ TsProgressUI started in process 3064 ]========== TsProgressUI 16.09.2014 11:01:51 10880 (0x2A80)
    Unregistering COM classes TsProgressUI 16.09.2014 11:01:51 10880 (0x2A80)
    Shutdown complete. TsProgressUI 16.09.2014 11:01:51 10880 (0x2A80)
    Process completed with exit code 0 TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    Successfully unregistered TS Progress UI. TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    Start to cleanup TS policy TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    End TS policy cleanup TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    Start to evaluate TS policy with lock TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    Updating settings in
    \\clientname\root\ccm\policy\machine\actualconfig TSManager 16.09.2014 11:01:51 7740 (0x1E3C)
    Machine RequestedConfig policy instance(s) : 1978 TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Added/updated setting 'ccm_softwaredistribution:adv_advertisementid=d012054b:pkg_packageid=d010015a:prg_programid=ts_install'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Added/updated setting 'inventorydataitem:dataitemid={0fc01f3e-7e62-46fd-ab98-926a2c724684}:itemclass=filesystemfile:namespace=\\.\root\ccm\invagt'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Added/updated setting 'inventorydataitem:dataitemid={33d85ab7-9913-4ba2-b887-0c7427bc0a2d}:itemclass=filesystemfile:namespace=\\.\root\ccm\invagt'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Added/updated setting 'inventorydataitem:dataitemid={3a27449d-1b79-40b5-970e-54655fc8dc67}:itemclass=filesystemfile:namespace=\\.\root\ccm\invagt'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Added/updated setting 'inventorydataitem:dataitemid={516688f4-d6b8-488f-8461-208e0847da93}:itemclass=win32reg_addremoveprograms:namespace=\\localhost\root\cimv2'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Added/updated setting 'inventorydataitem:dataitemid={73719729-c4e9-4132-a3d6-b07a322c41c1}:itemclass=win32reg_addremoveprograms64:namespace=\\localhost\root\cimv2'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Added/updated setting 'inventorydataitem:dataitemid={94d99a25-e6aa-4cc2-9a73-dc678f47810a}:itemclass=win32reg_smsguestvirtualmachine:namespace=\\.\root\cimv2'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Added/updated setting 'inventorydataitem:dataitemid={ac92faf2-88c1-4cd1-b30d-9a1ccf2fe562}:itemclass=win32reg_smsguestvirtualmachine64:namespace=\\.\root\cimv2'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Added/updated setting 'inventorydataitem:dataitemid={d0babbf8-42d3-4a6d-a905-0679ed466add}:itemclass=filesystemfile:namespace=\\.\root\ccm\invagt'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Added/updated setting 'inventorydataitem:dataitemid={fe169e66-dfbd-432a-8880-8300fd5854cd}:itemclass=filesystemfile:namespace=\\.\root\ccm\invagt'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Raising event:
    instance of CCM_PolicyAgent_SettingsEvaluationComplete
     ClientID = "GUID:eb79550c-aad9-4ed7-879e-74886b7b5aca";
     DateTime = "20140916090152.640000+000";
     PolicyNamespace = "\\\\clientname\\root\\ccm\\policy\\machine\\actualconfig";
     ProcessID = 20444;
     ThreadID = 7740;
     TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Successfully submitted event to the Status Agent. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    End TS policy evaluation TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Policy evaluation initiated TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Error executing Task Sequence Manager service. Code 0x80004005 TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Sending error status message TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Registry entry 'Certificate Store' is either missing or empty. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    The 'Certificate Store' is empty in the registry, using default store name 'MY'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Registry entry 'Certificate Selection Criteria' is either missing or empty. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Registry entry 'Select First Certificate' value is 1. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    The 'Certificate Selection Criteria' was not specified, counting number of certificates  present in 'MY' store of 'Local Computer'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    1 certificate(s) found in the 'MY' certificate store. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Only one certificate present in the certificate store. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    The certificate issued to 'clientname' has 'Client Authentication' capability. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Using the certificate issued to 'clientname'. TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    Formatted header: TSManager 16.09.2014 11:01:52 7740 (0x1E3C)
    <Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>GUID:eb79550c-aad9-4ed7-879e-74886b7b5aca</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2014-09-16T09:01:52Z</SentTime><Protocol>http</Protocol><Body
    Type="ByteRange" Offset="0" Length="1178"/><Hooks><Hook2 Name="clientauth

  • Task Sequence Error - Failed to find CCM_SoftwareDistribution object (0x80040104)

    Hi, we recently migrated packages and a DP to SCCM2012. now, when we checked OS Deployment, the TS fails with error Code 0x80040104.   . it has errors with a driver package.
    I Already updated the DP, i also deleted it on all DPs and resend it.. no luck.
    Someone a clue. in the forum i saw an entry about a corrupt driver package.. but no further infos or a link.

    SMSTS.LOG
    Adding URL location item 2 2 00000374 00000001 http://HAMI0372.Global.BDFGroup.net/SMS_DP_SMSPKG$/BSS000B2    TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
    Prioritized locations:    TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
      http://HAMI0372.Global.BDFGroup.net/SMS_DP_SMSPKG$/BSS000B2    TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
    BSS000B2 content location:     TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
    BSS000B2 http content location: http://HAMI0372.Global.BDFGroup.net/SMS_DP_SMSPKG$/BSS000B2    TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
    Getting policy for CCM_SoftwareDistribution[AdvertID="BDF20002", PackageID="BSS000DE", ProgramID="*"]    TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
    FALSE, HRESULT=80040104 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,2506)    TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
    Failed to find CCM_SoftwareDistribution object for AdvertID="BDF20002", PackageID="BSS000DE", ProgramID="*"    TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
    (*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040104 (e:\nts_sccm_release\sms\framework\tscore\tspolicy.cpp,3341)    TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
    m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040104 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1480)  
     TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
    Failed to resolve selected task sequence dependencies. Code(0x80040104)    TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
    hrReturn, HRESULT=80040104 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediaresolveprogresspage.cpp,408)    TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
    ThreadToResolveAndExecuteTaskSequence failed. Code(0x80040104)    TSMBootstrap    20.07.2012 09:02:29    1356 (0x054C)
    ThreadToResolveAndExecuteTaskSequence returned code 0x80040104    TSMBootstrap    20.07.2012 09:02:29    1216 (0x04C0)
    Setting wizard error: This task sequence cannot be run because a package referenced by the task sequence could not be found. For more information, contact your system administrator or helpdesk operator.    TSMBootstrap    20.07.2012
    09:02:29    1216 (0x04C0)
    ResolveProgressPage::OnWizardNext()    TSMBootstrap    20.07.2012 09:02:29    1216 (0x04C0)
    Activating Finish Page.    TSMBootstrap    20.07.2012 09:02:29    1216 (0x04C0)
    Loading bitmap    TSMBootstrap    20.07.2012 09:02:29    1216 (0x04C0)
    Executing command line: X:\windows\system32\cmd.exe /k    TSBootShell    20.07.2012 09:02:30    804 (0x0324)
    The command completed successfully.    TSBootShell    20.07.2012 09:02:30    804 (0x0324)
    Successfully launched command shell.    TSBootShell    20.07.2012 09:02:30    804 (0x0324)
    Exiting task sequence wizard.    TSMBootstrap    20.07.2012 09:11:59    1216 (0x04C0)
    Exiting with return code 0x00000000    TSMBootstrap    20.07.2012 09:11:59    1216 (0x04C0)
    Execution complete.    TSBootShell    20.07.2012 09:11:59    828 (0x033C)
    Finalizing logging from process 800    TSBootShell    20.07.2012 09:11:59    828 (0x033C)
    Finalizing logs to root of first available drive    TSBootShell    20.07.2012 09:11:59    828 (0x033C)
    Successfully finalized logs to C:\SMSTSLog    TSBootShell    20.07.2012 09:11:59    828 (0x033C)
    Cleaning up task sequencing logging configuration.    TSBootShell    20.07.2012 09:11:59    828 (0x033C)

Maybe you are looking for

  • Ajax functionality works in embedded OC4J, but not on iAS 10.1.2

    Hi, For a customer, we made an ADF application using JDeveloper 10.1.2. Using instructions from http://www.oracle.com/technology/pub/articles/vohra-ajax.html we coded a servlet, to find a description from a code the user entered in the application, a

  • Ical error, as well not able to invite people to ical events

    Hi everybody I have been having issues with my Ical and I don't really know what to do anymore. I have tried the Genius, I have tried the apple care, and seems that no one can help me with this problem. I'm using Mountain Lion, and the latest updates

  • Issues with Japanese encoding using Mail

    Since recently (I would say since I updated to 10.6), I have an issue with Japanese-encoded (ISO 2022-JP) mails on my English MacOS. I have no problem to read, edit and write answers to any mails. However with some ISO JP-2022-JP encoded messages (se

  • Join Query Issue

    Hi,       I have issue in the following query when selecting SPART . If spart is selected , the results are not correct. Is there anything i am missing in the query.   SELECT  amatnr aersda alaeda aprdha aspart bmaktx cprodh cvkorg cvtweg  cmvgr1  cm

  • How do i uninstall firefox startup 2.0.0.4

    Cannot uninstall firefox setup 2.0.0.4