Task Sequence has failed with error code: 0x80070570

I've created task sequence for Windows XP OS Deployment. WinPE boot image loads successfully, Partitions are formatted successfully too. But during "Applying image 1 from volume C:\" I receive following error:
Task Sequence: My_task_sequence_name has failed with error code: 0x80070570.
What I need to do? Any ideas? (My computer has following details: ASUS P5KSE motherboard, Core 2 Duo, SATA HDD, Atheros L1 adapter)

No, a build and capture task sequence automates the build of the image removing any and all human intervention so that rebuilding or refreshing an image becomes a simple matter. Building images by actually manually installing Windows is anti-IT.
File corruption can be caused by many, many things; e.g., anti-virus, physical disk errors, network transmit errors, etc.
Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Similar Messages

  • ReleaseRequest failed with error code 0x80004005 \ Task Sequence Manager could not release active TS request. code 80004005

    Hi All,
    I am trying to deploy an OS but the deployment is failing part way through. I have searched the logs and identified the error: Task Sequence Manager could not release active TS request. code 80004005
    If anyone could assist with this is would be much appreciated.
    Many thanks
    Logs below:
    <![LOG[Unlocked ActualConfig successfully]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="0" thread="1752" file="policyutil.cpp:7898">
    <![LOG[Unlocked policy transaction lock successfully]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="0" thread="1752" file="policyutil.cpp:7904">
    <![LOG[Raising event:
    instance of CCM_PolicyAgent_SettingsEvaluationComplete
    ClientID = "GUID:8388E2E2-7642-4436-88D0-FC9335F6D56E";
    DateTime = "20141218122103.273000+000";
    PolicyNamespace = "\\\\wst0339\\root\\ccm\\policy\\machine\\actualconfig";
    ProcessID = 1748;
    ThreadID = 1752;
    ]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="event.cpp:729">
    <![LOG[Successfully submitted event to the Status Agent.]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="0" thread="1752" file="event.cpp:747">
    <![LOG[End TS policy evaluation]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="policyutil.cpp:10580">
    <![LOG[Policy evaluation initiated]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="utils.cpp:3387">
    <![LOG[Sending success status message]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="tsmanager.cpp:659">
    <![LOG[MP server http://LONSVR0150.uk.ham.local. Ports 80,443. CRL=false.]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="utils.cpp:4855">
    <![LOG[Setting authenticator]LOG]!><time="12:21:03.288+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="utils.cpp:4877">
    <![LOG[Set authenticator in transport]LOG]!><time="12:21:03.288+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="libsmsmessaging.cpp:7592">
    <![LOG[Sending StatusMessage]LOG]!><time="12:21:03.304+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="libsmsmessaging.cpp:4020">
    <![LOG[Setting message signatures.]LOG]!><time="12:21:03.320+00" date="12-18-2014" component="TSManager" context="" type="0" thread="1752" file="libsmsmessaging.cpp:1292">
    <![LOG[Setting the authenticator.]LOG]!><time="12:21:03.320+00" date="12-18-2014" component="TSManager" context="" type="0" thread="1752" file="libsmsmessaging.cpp:1322">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: LONSVR0150.uk.ham.local:80  CCM_POST /ccm_system/request]LOG]!><time="12:21:03.320+00" date="12-18-2014" component="TSManager" context="" type="1"
    thread="1752" file="libsmsmessaging.cpp:8422">
    <![LOG[Request was succesful.]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="0" thread="1752" file="libsmsmessaging.cpp:8758">
    <![LOG[Finalize logging request ignored from process 1748]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="tslogging.cpp:1737">
    <![LOG[Waiting for CcmExec service to be fully operational]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="utils.cpp:4019">
    <![LOG[CcmExec service is up and fully operational]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="utils.cpp:4024">
    <![LOG[Access handle will be read from _SMSTSActiveRequestHandle]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="tsmanagerutils.cpp:99">
    <![LOG[Access handle: {9F9B91DA-055D-4B32-9817-52C369835080}]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="tsmanagerutils.cpp:111">
    <![LOG[Attempting to release request using {9F9B91DA-055D-4B32-9817-52C369835080}]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752"
    file="tsmanagerutils.cpp:118">
    <![LOG[CoCreateInstance succeeded]LOG]!><time="12:21:03.382+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="tsmanagerutils.cpp:133">
    <![LOG[pISoftwareExecutionRequestMgr->ReleaseRequest(ActiveRequestGUID), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanagerutils.cpp,136)]LOG]!><time="12:21:03.382+00" date="12-18-2014" component="TSManager"
    context="" type="0" thread="1752" file="tsmanagerutils.cpp:136">
    <![LOG[ReleaseRequest failed with error code 0x80004005]LOG]!><time="12:21:03.382+00" date="12-18-2014" component="TSManager" context="" type="3" thread="1752" file="tsmanagerutils.cpp:136">
    <![LOG[Task Sequence Manager could not release active TS request. code 80004005]LOG]!><time="12:21:03.382+00" date="12-18-2014" component="TSManager" context="" type="2" thread="1752"
    file="tsmanagerutils.cpp:165">
    <![LOG[Process completed with exit code 0]LOG]!><time="12:21:03.413+00" date="12-18-2014" component="TSMBootstrap" context="" type="1" thread="1728" file="commandline.cpp:1098">
    <![LOG[Exiting with return code 0x00000000]LOG]!><time="12:21:03.413+00" date="12-18-2014" component="TSMBootstrap" context="" type="1" thread="1728" file="tsmbootstrap.cpp:1032">
    <![LOG[Process completed with exit code 0]LOG]!><time="12:21:03.413+00" date="12-18-2014" component="OSDSetupHook" context="" type="1" thread="788" file="commandline.cpp:1098">
    <![LOG[Task sequence completed 0x00000000]LOG]!><time="12:21:03.413+00" date="12-18-2014" component="OSDSetupHook" context="" type="1" thread="788" file="basesetuphook.cpp:1384">
    <![LOG[Uninstalling Setup Hook]LOG]!><time="12:21:06.552+00" date="12-18-2014" component="OSDSetupHook" context="" type="1" thread="788" file="basesetuphook.cpp:1427">
    <![LOG[Removing setup hook from registry.]LOG]!><time="12:21:06.552+00" date="12-18-2014" component="OSDSetupHook" context="" type="0" thread="788" file="vistasetuphook.cpp:143">
    <![LOG[Successfully removed C:\WINDOWS\system32\OSDGINA.DLL]LOG]!><time="12:21:06.552+00" date="12-18-2014" component="OSDSetupHook" context="" type="1" thread="788" file="basesetuphook.cpp:1183">
    <![LOG[Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE]LOG]!><time="12:21:06.552+00" date="12-18-2014" component="OSDSetupHook" context="" type="1" thread="788" file="basesetuphook.cpp:1183">
    <![LOG[Successfully removed C:\WINDOWS\system32\_SMSOSDSetup]LOG]!><time="12:21:06.552+00" date="12-18-2014" component="OSDSetupHook" context="" type="1" thread="788" file="basesetuphook.cpp:1220">

    4005 can mean a few things,  Some common can be  The wrong BIOS time,  or a a bad Hard drive.   look at those two first. 

  • Task sequence failed with error code 0x80070002

    I am facing issue in OS deployment my machine PXE boot successfully but on the step of apply operating I got an error "task sequence failed with error code 0x80070002" 
    I see lot of thread describes to add Network Access Account I already added but still I receive same error please help
    Usama Arif

    i had this happen on two of my dp's the other day.  It drove me nuts,  I ended up  removing the DP Role,  removing the server from SCCM
    I then deleted all files on the  'D :'  drive
    after everything was deleted, I re-added the  Server to SCCM and gave it the DP Role back. 
    I then added the DP Back to the  DP Group to receive all packages that was on it before.    then finally once everything was re-uploaded my users were able to pxe boot again

  • SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has be

    Hello, I have a sql 2005 server, and I am a developer, with the database on my own machine.  It alwayws works for me but after some minutes the other developer cant work in the application
    He got this error
    Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.140]
    and When I see the log event after that error, it comes with another error.
    SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.1.140]
    He has IIS5 and me too.
    I created a user on the domain called ASPSYS with password, then in the IIS on anonymous authentication I put that user with that password, and it works, on both machines.
    and in the connection string I have.
    <add key="sqlconn" value="Data Source=ESTACION15;Initial Catalog=GescomDefinitiva;Integrated Security=SSPI; Trusted_Connection=true"/>
    I go to the profiler, and I see that when he browses a page, the database is accesed with user ASPSYS, but when I browse a page, the database is accesed with user SE\levalencia.
    Thats strange.
    The only way that the other developer can work again on the project is to restart the whole machine. He has windows xp profession, I have windows 2000.
    If you want me to send logs please tellme

    Well here's my problem, maybe you can help. Intermittenly I get a login failed when connecting to a db engine through Server Management Studio using Windows authentication. When this happens the following entries are generated on the server's application event log:
    Event Type:        Error
    Event Source:    MSSQLSERVER
    Event Category:                (4)
    Event ID:              17806
    Date:                     1/14/2009
    Time:                     10:41:31 AM
    User:                     N/A
    Computer:          <server name>
    Description:
    SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: <ip address>]
    Event Type:        Failure Audit
    Event Source:    MSSQLSERVER
    Event Category:                (4)
    Event ID:              18452
    Date:                     1/14/2009
    Time:                     10:41:31 AM
    User:                     N/A
    Computer:          <server name>
    Description:
    Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: <ip address>]
    I've already ensured that the server is set to mixed authentication mode. Oddly enough, the workaround that I've found is that if I remote desktop into the server, log in and then log back out, Management Studio is suddenly able to connect again. No idea why it works. 
    As I said before, it is intermitten. Some days it errors on login, other days it doesn't and there are no configuration changes between them. Also, both client and server are in the same domain and same site so there is no VPN or anything in between. I'm really quite stumped. Any help would be great, or if you can point me in the right direction of where to look. Thank you in advance!

  • Error in upgrading SharePoint Server 2013 with SP1 : "Task upgradebootstrap has failed with an unknown exception"

    I has successfully setup new Dev ENV of SarePoint server 2013 in VMware with 2 servers running om OS: win server 2008 R2 Ent SP1, AD + Central Admin Application Server.
    After that the configuration of SharePoint App and WorkFlow Manager completed as well and many projects run perfectly,
    And after installing SP1 of SharePoint server 2013, and running the SharePiont Configuration wizard to complete the configuration of the SharePoint Farm the Upgrade has fialed on Step2 with the following Error from the Log file:
    Task upgradebootstrap has failed with an unknown exception 
    01/04/2015 00:43:30  11  ERR                  Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: Exception of type 'Microsoft.SharePoint.Upgrade.SPUpgradeException' was thrown.
       at Microsoft.SharePoint.Upgrade.SPManager.BootStrap(Guid sessionId, SPUpgradeOperationFlags flags)
       at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
       at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
    Also after that I was not able to create like before a new site , and this creating end with error message as follows:
    Failed to call GetTypes on assembly Microsoft.Office.TranslationServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Method not found: 'Microsoft.Office.Web.Common.ProcessImageInfo.
    Is there any solution to my problem with SharePoint server 2013 SP1, this supposed not to cause any bug in stable environment.
    Basel Badr ,SharePoint Specialist ,MCAD ,MCTS.

    Hi Daniel,
    Thanks for replying on my post, actually I have downloaded the  kb2880552 sp1 for
    enterprise edition from the link 
    https://support.microsoft.com/kb/2880552 , and this has been experienced with me before since I had my Standalone Dev machine first installation, and the issue only occurred when the SP1 installed though.
    Anyway, I've tried to install CU Nov 2013 http://support.microsoft.com/kb/2889944
    but still facing the same issue,
    I run the Setup of SP2013 from the CD to repair the SharePoint and error message appears,
    The issue related to "Microsoft.Office.TranslationServices" is also related to running
    the repair successfully which leads to the same error message above.
    The Version of SP 2013 from the program file is : 15.0.4571.1502
    The Update snapshot is as below:
    Is there a problem with my sharepoint media file?
    Basel Badr ,SharePoint Specialist ,MCAD ,MCTS.

  • SCOM 2012 SP1 "Task invocation failed with error code -2146232576"

    Hi,
    I`m trying to discover a Linux RHEL 5.9 Server which is in another untrusted domain and from the Discovery wizard I receive the following error:
    Task invocation failed with error code -2146232576. Error message was 0x80131700.
    Any ideas ?
    Greetings.

    Hi,
    @Simon, I restart the SCOM services and I also verify the UAC and it's disabled.
    @Mai Ali, thank you for you reply. I don't have a "&" symbol in my password, but only a "$" ..I hope it's fine.
    If the SCOM discovery doesn't work, I installed the agent manually on the Linux server.
    BTW I also use a "monuser" account configured using this procedure:
    http://social.technet.microsoft.com/wiki/contents/articles/7375.configuring-sudo-elevation-for-unix-and-linux-monitoring-with-system-center-2012-operations-manager.aspx
    I also verify the ports 22 and 5723 and are opened, but I also noticed that if you restart the scxadmin, is listening on HTTPS on port 1207.
    Now..if I try to re-discover the Linux server from SCOM, I receive the following error:
    "The pool managing the instance is not available or the location monitoring object cannot be found"
    Regards.

  • SCCM 2012 CU2 OSD forest trust: ReleaseRequest failed with error code 0x87d00317

    Hello,
    Actually i have a difficult Problem with my SCCM 2012 R2 CU2 Windows 7 x64 SP1 Tasksequence:
    I get the folowing error in smsts.log:
    ::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811) TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    GetTsRegValue() is unsuccessful. 0x80070002. TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    End program:  TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Finalize logging request ignored from process 1736 TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Waiting for CcmExec service to be fully operational TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    CcmExec service is up and fully operational TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Access handle will be read from _SMSTSActiveRequestHandle TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Access handle: {B699D570-B2BF-4874-8CB7-3B208B380969} TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Attempting to release request using {B699D570-B2BF-4874-8CB7-3B208B380969} TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    CoCreateInstance succeeded TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    pISoftwareExecutionRequestMgr->ReleaseRequest(ActiveRequestGUID), HRESULT=87d00317 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanagerutils.cpp,136) TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    ReleaseRequest failed with error code 0x87d00317 TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Task Sequence Manager could not release active TS request. code 87D00317 TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Here is the complete smsts.log: http://1drv.ms/1pwTEBf
    To explain the Problem in Detail:
    The SCCM Primary Site Server and the Clients are in different trusted (bidirectional) forests!
    Everythings working fine in this Scenario, I can install SCCM Agent on the Clients with Manual ccmsetup and with Client Push Installation. Additionally i can deploy Software Updates and so on... only OSD is crashing in the releaserequest step.
    During my Tasksequence new Clients are joined to Domain A while SCCM Primary Site Server is installed in Domain B
    If I change my TS and let the Clients also join Domain B everything works without any Problems and the Tasksequence finish without any Errors.
    My Problem must be related to the different Domains and the forest trust.
    My Setup:
    MP published to DNS in both domains
    Schema Extended in both domains
    System Management Container published and verified in both domains
    ccmsetup Parameters in TS: ccmsetup SMSMP=sccm.domain.b FSP=sccm.domain.b DNSSUFFIX=Domain.b
    Network Access account configured with Domain B account
    Domain Join account has create Computer rights on the OU in Domain A (Domain join is successful)
    DNs conditional forwarders configured in both Domains and DNS resolutin is working in both directions
    Any suggestions?
    Many thanks.
    regards,
    Christian

    Hi Christian,
    So do you actual get an error message in your TS or is it just failing to join Domain B?  (Could be both if the machines fails to join the domain).
    Can you review netsetup.log on the machines after the issue and see what error message you might be getting during the domain join process?
    Also, if it a domain join issue, can you try manually joining to domain B using the same service account?

  • Request User State Store Fails with error code 0x00004005

    I am trying to get a machine refresh working in SCCM and am running into a road block with the user state migration. The Task sequence hits Request user state store and then fails. In the logs on the machine it shows it downloads the cert from the SMP but it fails to verify the cert. The thing is that this was working and then stopped for no apparent reason. I have added a second SMP and it has the same issue so its got to be something environmental causing this. I have found no references to the errors I am recieving that relate to the issue so I am stumped. We have a SCCM 2007 site in mixed mode. The error log is:
    The task sequence execution engine failed executing the action (Request User State Storage) in the group (Capture User Files and Settings) with the error code 16389 Action output: ployment\osdsmpclient\smpclient.cpp,1743) Request to SMP 'ATXFREPSMS01.NA.atxglobal.com' failed with error (Code 0x80090006). Trying next SMP. FALSE, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1698) pClientRequestToSMP->Execute(migInfoFromMP.saSMPs), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2713) ExecuteCaptureRequestToSMP(migInfoFromMP), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2755) ExecuteCaptureRequest(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\main.cpp,72) OSDSMPClient finished: 0x00004005 Failed to verify certificate signature for 'ATXFREPSMS01.NA.atxglobal.com' (0x80090006) ClientKeyRequestToSMP failed (0x80090006). ClientRequestToSMP:oRequest failed. error = (0x80090006). Failed to find an SMP that can serve request after trying 4 attempts. ExecuteCaptureRequestSMP failed (0x80004005). ExecuteCaptureRequest failed (0x80004005).. The operating system reported error 16389:

    Hi
    I am getting the same issue.
    More info:
    The same task works ok for one client - an xp machine that was upgraded to vista sp1 using sccm but without usmt.
    If I send this machine a task which includes usmt and os deploy it works.
    On 2 other machines ( so far) , the request store fails with the same error  - 0x80090006. (one of them existing vista and the other xp)
    I have tried removing and adding the client from the domain but it did not help.
    Any idea?
    David

  • The AcquireConnection method call failed with error code 0xC0202009.

    I've seen the previous threads on this (although maybe not all of them). However, i don't think I'm getting the error for the same reason. The full error I'm getting is:
    - Pre-execute (Error)
    Messages
    Error 0xc0202009: {F1B3B35C-FAE3-48F6-A169-4E4D8D99F9B6}: An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft JET Database Engine"  Hresult: 0x80004005  Description: "Unspecified error".
     (SQL Server Import and Export Wizard)
    Error 0xc020801c: Data Flow Task: The AcquireConnection method call to the connection manager "DestinationConnectionExcel" failed with error code 0xC0202009.
     (SQL Server Import and Export Wizard)
    Error 0xc004701a: Data Flow Task: component "Destination 64 - production_effectivities" (7042) failed the pre-execute phase and returned error code 0xC020801C.
     (SQL Server Import and Export Wizard)
    The entire package is running on one machine. The data source is SQL Server 2005 and the destination (this happens with both of them) is Excel or Access. Either way I cannot get the package which the wizard generated to run at all. This error occurs after the first table is exported. I'm running on WinXP SP2 with 2005 Developer and ALL components installed except analysis services.
    Anyone else have this problem or know the solution?
    Jeff

    I am getting the same error. My Destination and source both are on SQL Server 2005 on the same box.
    I am using SQL- Code for Source and and table as destination. When the package runnes under Transaction- TransactionOption-Supported then the packages excuted fine but it fails when i change the Transaction- TransactionOption to Required.
    It fails with following error code.
    [OLE DB Destination [22]] Error: The AcquireConnection method call to the connection manager "FMFCLSQADB01.DWH_Rakesh" failed with error code 0xC0202009.
    [DTS.Pipeline] Error: component "OLE DB Destination" (22) failed the pre-execute phase and returned error code 0xC020801C.
    [Connection manager "FMFCLSQADB01.DWH_Rakesh"] Error: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D00A "Unable to enlist in the transaction.".
    [Connection manager "FMFCLSQADB01.DWH_Rakesh"] Error: An OLE DB error has occurred. Error code: 0x8004D00A.
    When i change the source SQL query to Table or View then it works fine.
    Thanks for any suggestion.
    Regards
    Rakesh
    Now, my issues related to “SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D00A "Unable to enlist in the transaction."…..”. are fixed.
    This is one of the very common errors that comes up in SSIS (SQL Server Integration service) 
    I have faced this issue for at-least two occasions. Both of them have one common setting: “TransactionOption” was set to “Required”.
    In first case, I had multiple dataflow tasks but there were no sequence given. There were no error if I ran the package with TransactionOption=Supported. But when I ran the package in TransactionOption= Required, it got failed.
    To fix the issue I have changed my package and put the entire dataflow task one after another (connected thru Constraint).  
    In another case, where I was doing data transfer from one server to another, I had to configure the MSDTC.

  • SSIS 2012: SSIS Error Code "Excel Connection Manager" failed with error code 0xC0202009.

    Hi,
    This is kind of weird issue that I am experiencing with excel connection manager in SSIS 2012. This issue occurs sometimes but when I close and re-open SSDT (SQL Server Data Tools - newer BIDS) then this issues goes off temporarily.
    Just FYI, through SSDT environment I executed the package successfully with both settings Run64bit runtime setting to Yes and No when error does not occur.
    So far I have installed
    http://www.microsoft.com/en-us/download/details.aspx?id=13255 (Microsoft Access Database Engine 2010 Redistributable).
    I still remember for older versions of SQL Server (2005 & 2008) that I have executed Excel connection SSIS packages with Run64bit runtime = false i.e. in 32-bit mode. As far as I know I think Excel 64-bit issue has been resolved with SQL Server
    2012 release.
    Here is the detail of error message:
    TITLE: Package Validation Error
    Package Validation Error
    ADDITIONAL INFORMATION:
    Error at Data Flow Task [Excel Source [2]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection
    Manager" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.
    Error at Data Flow Task [SSIS.Pipeline]: Excel Source failed validation and returned error code 0xC020801C.
    Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.
    Error at Data Flow Task: There were errors during task validation.
    Error at Package [Connection manager "Excel Connection Manager"]: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft Access Database Engine"  Hresult: 0x80004005  Description: "Unspecified error".
     (Microsoft.DataTransformationServices.VsIntegration)
    Here are my environment details:
    SQL Server 2012 {Microsoft SQL Server 2012 (SP1) - 11.0.3368.0 (X64) } , Excel 2010 (32-bit). I am developing SSIS code on Virtual desktops with Windows 7 32-bit OS.
    Also it occurred to me that since Virtual Desktops are on Shared Infrastructure, the source files and SSIS packages (code) can be on Shared drives for e.g. \\<Corpnet>\userdata\<Corp_Users_Grp>\<Username>\Visual Studio 2010\Projects\Integration
    Services Project2\Integration Services Project2\Package.dtsx.
    Does this kind of Shared drives have any impact to give this issue?
    Thanks in advance!
    Ketan
    P.S.: I had look at this forum question -->
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/903bbe1d-e070-4c43-9d3b-0a5193550029/64bit-error-in-excel-connection-manager-in-ssis

    Hi Arthur,
    Thanks for your response.
    Yes, it looks like SSIS still has bunch of issues with Excel files like as follows:
    1) Some times excel source files cannot be parsed by excel source connection manager.
    2) For derive column conversion, we can't replace the existing column. rather, we have to add the derived column as " add as new column" which is tough to manage  while destination mapping.
    3) If an column in excel contains a data which is not of the data type assigned for the column in excel, the excel source reads that data as "null". For the same, we can't validate the data and redirect the erroneous data in reject file.  <-- For
    this we tried IMEX setting also
    4) In multi-tab/sheet excel file, excel source is unable to detect a tab and identify the metadata of the excel.
    I am also checking Microsoft connect for Excel issues with SSIS 2012(https://connect.microsoft.com/SQLServer/SearchResults.aspx?SearchQuery=excel#&&PageIndex=22
    As worst case scenario, I am thinking of converting Excel to CSV file or Flat text file. (http://www.mssqltips.com/sqlservertip/2772/importing-data-from-excel-using-ssis--part-2/).
    Do you think it is advisable to convert Excel into CSV or Flat file.
    Thanks,
    Ketan

  • [Load data from excel file [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messa

    Error
    [Load data from excel file [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.  There
    may be error message
    I am using BIDS Microsoft Visual Studio 2008 and running the package to load the data from excel .
    My machine has 32 bit excel hence have set property to RUN64BITRUNTIME AS FALSE.
    But the error still occurs .
    I checked on Google and  many have used Delay validation property at Data flow task level to true but even using it at both excel connection manager and DFT level it doesnt work
    Mudassar

    Thats my connection string
    Provider=Microsoft.ACE.OLEDB.12.0;Data Source=E:\SrcData\Feeds\Utilization.xlsx;Extended Properties="Excel 12.0;HDR=NO";
    Excel 2010 installed and its 32 bit edition
    Are you referring to install this component -AccessDatabaseEngine_x64.exe?
    http://www.microsoft.com/en-us/download/details.aspx?id=13255
    Mudassar
    You can try an OLEDB provider in that case
    see
    http://dataintegrity.wordpress.com/2009/10/16/xlsx/
    you might need to download and install ms access redistributable
    http://www.microsoft.com/en-in/download/details.aspx?id=13255
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • CcmSetup failed with error code 0x80004005 - windows 8.1

    using sccm 2012 r2, trying to push to a windows 8.1 client i get:
    <![LOG[==========[ ccmsetup started in process 7416 ]==========]LOG]!><time="16:05:28.041+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:9437">
    <![LOG[Running on platform X64]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="util.cpp:1837">
    <![LOG[Updated security on object C:\WINDOWS\ccmsetup\cache\.]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9272" file="ccmsetup.cpp:9281">
    <![LOG[Launch from folder C:\WINDOWS\ccmsetup\]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:721">
    <![LOG[CcmSetup version: 5.0.7958.1000]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:727">
    <![LOG[In ServiceMain]LOG]!><time="16:05:28.044+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="ccmsetup.cpp:3365">
    <![LOG[Running on 'Microsoft Windows 8.1 Pro' (6.3.9600). Service Pack (0.0). SuiteMask = 272. Product Type = 18]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context="" type="1"
    thread="9468" file="util.cpp:1919">
    <![LOG[Ccmsetup command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context="" type="1"
    thread="9468" file="ccmsetup.cpp:3590">
    <![LOG[Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context=""
    type="1" thread="9468" file="ccmsetup.cpp:3775">
    <![LOG[Command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468"
    file="ccmsetup.cpp:3776">
    <![LOG[SslState value: 224]LOG]!><time="16:05:28.085+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="ccmsetup.cpp:4425">
    <![LOG[CCMHTTPPORT:    80]LOG]!><time="16:05:28.086+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8617">
    <![LOG[CCMHTTPSPORT:    443]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8632">
    <![LOG[CCMHTTPSSTATE:    224]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8650">
    <![LOG[CCMHTTPSCERTNAME:    ]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8668">
    <![LOG[FSP:    ]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8720">
    <![LOG[CCMFIRSTCERT:    1]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8778">
    <![LOG[Config file:      C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468"
    file="ccmsetup.cpp:4539">
    <![LOG[Retry time:       10 minute(s)]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4540">
    <![LOG[MSI log file:     C:\WINDOWS\ccmsetup\Logs\client.msi.log]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468"
    file="ccmsetup.cpp:4541">
    <![LOG[MSI properties:    INSTALL="ALL" SMSSITECODE="consto" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"]LOG]!><time="16:05:28.088+00"
    date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4542">
    <![LOG[Source List:]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4550">
    <![LOG[                  \\TA-SRV-SC.constoplc.local\SMSClient]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup"
    context="" type="1" thread="9468" file="ccmsetup.cpp:4557">
    <![LOG[                  \\TA-SRV-SC.constoPLC.LOCAL\SMSClient]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup"
    context="" type="1" thread="9468" file="ccmsetup.cpp:4566">
    <![LOG[MPs:]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4569">
    <![LOG[                  TA-SRV-SC.constoplc.local]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context=""
    type="1" thread="9468" file="ccmsetup.cpp:4584">
    <![LOG[MapNLMCostDataToCCMCost() returning Cost 0x1]LOG]!><time="16:05:28.091+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmutillib.cpp:5479">
    <![LOG[No version of the client is currently detected.]LOG]!><time="16:05:28.093+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:2748">
    <![LOG[Folder 'Microsoft\Configuration Manager' not found. Task does not exist.]LOG]!><time="16:05:28.094+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="wintask.cpp:622">
    <![LOG[Updated security on object C:\WINDOWS\ccmsetup\.]LOG]!><time="16:05:28.095+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="ccmsetup.cpp:9281">
    <![LOG[A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent.]LOG]!><time="16:05:28.095+00" date="01-15-2014" component="ccmsetup" context="" type="1"
    thread="9468" file="ccmsetup.cpp:9763">
    <![LOG[Running as user "SYSTEM"]LOG]!><time="16:05:28.118+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:1995">
    <![LOG[A Fallback Status Point has not been specified.  Message with STATEID='328' will not be sent.]LOG]!><time="16:05:28.118+00" date="01-15-2014" component="ccmsetup" context="" type="1"
    thread="9468" file="ccmsetup.cpp:9763">
    <![LOG[CcmSetup failed with error code 0x80004005]LOG]!><time="16:05:28.119+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:10879">
    any ideas why its failing?

    Hi,
    I've seen the same error on a customer where we had Windows Intune Client (SCCM) installed previously. Did you try it on a newly deployed computer? If you had Intune or another CCM client on it previously make sure you clean it up. Here is a well formulated
    instruction:
    http://douwevanderuit.wordpress.com/2014/01/30/removing-windows-intune-client/
    Usually when deploying to many clients we use a startup script, there is a great one that Jason Sandys made in the link below.
    http://blog.configmgrftw.com/configmgr-client-startup-script/
    There should be no problems deploying SCCM 2012 R2 clients on Windows 8.1 unless there is something wrong with either the setup or the client computer.
    All the best, Jesper Hassing - MCTS SCCM 2012 - MCSA 2012 Server - MCP

  • Client push error CcmSetup failed with error code 0x8007064c

    Installing file 'C:\WINDOWS\ccmsetup\Silverlight.exe' with options '/q'.
    File 'C:\WINDOWS\ccmsetup\Silverlight.exe' returned failure exit code 1612. Fail the installation.
    InstallFromManifest failed 0x8007064c
    ITaskScheduler::Delete failed to delete task Configuration Manager Client Retry Task (0x80070002).
    CcmSetup failed with error code 0x8007064c
    This error i faced while Upgrading client on Windows Server 2003 ,that i upgraded my SCCM 2012 SP1 to SCCM2012 R2 
    i tried to uninstall the client and done successfully , while pushing the client again I've the same Error code.
    i searched and found SMS 2003 toolkit 2 fixed the problem for some people but i did not .

    <![LOG[==========[ ccmsetup started in process 8108 ]==========]LOG]!><time="15:37:25.641-180" date="08-05-2014" component="ccmsetup" context="" type="1" thread="5432" file="ccmsetup.cpp:9437">
    <![LOG[Running on platform X86]LOG]!><time="15:37:25.641-180" date="08-05-2014" component="ccmsetup" context="" type="1" thread="5432" file="util.cpp:1837">
    <![LOG[Updated security on object C:\WINDOWS\ccmsetup\cache\.]LOG]!><time="15:37:25.641-180" date="08-05-2014" component="ccmsetup" context="" type="0" thread="5432" file="ccmsetup.cpp:9281">
    <![LOG[Launch from folder C:\Setup\Client\]LOG]!><time="15:37:25.641-180" date="08-05-2014" component="ccmsetup" context="" type="1" thread="5432" file="ccmsetup.cpp:721">
    <![LOG[CcmSetup version: 5.0.7958.1000]LOG]!><time="15:37:25.641-180" date="08-05-2014" component="ccmsetup" context="" type="1" thread="5432" file="ccmsetup.cpp:727">
    <![LOG[Running on 'Microsoft(R) Windows(R) Server 2003, Standard Edition' (5.2.3790). Service Pack (2.0). SuiteMask = 272. Product Type = 18]LOG]!><time="15:37:25.876-180" date="08-05-2014" component="ccmsetup" context="" type="1" thread="5432" file="util.cpp:1919">
    <![LOG[Ccmsetup command line: C:\Setup\Client\ccmsetup.exe  SMSSLP=ldcsccm1v.linkdc.local  SMSSITECODE=ldc DNSSUFFIX=linkdc.local]LOG]!><time="15:37:25.876-180" date="08-05-2014" component="ccmsetup" context="" type="1" thread="5432" file="ccmsetup.cpp:3590">
    <![LOG[Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.]LOG]!><time="15:37:25.876-180" date="08-05-2014" component="ccmsetup" context="" type="1" thread="5432" file="ccmsetup.cpp:3775">
    <![LOG[Command line: C:\Setup\Client\ccmsetup.exe  SMSSLP=ldcsccm1v.linkdc.local  SMSSITECODE=ldc DNSSUFFIX=linkdc.local]LOG]!><time="15:37:25.876-180" date="08-05-2014" component="ccmsetup" context="" type="1" thread="5432" file="ccmsetup.cpp:3776">
    <![LOG[SslState value: 224]LOG]!><time="15:37:25.876-180" date="08-05-2014" component="ccmsetup" context="" type="0" thread="5432" file="ccmsetup.cpp:4425">
    <![LOG[No version of the client is currently detected.]LOG]!><time="15:37:25.907-180" date="08-05-2014" component="ccmsetup" context="" type="1" thread="5432" file="ccmsetup.cpp:2748">
    <![LOG[Updated security on object C:\WINDOWS\ccmsetup\.]LOG]!><time="15:37:25.938-180" date="08-05-2014" component="ccmsetup" context="" type="0" thread="5432" file="ccmsetup.cpp:9281">
    <![LOG[A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent.]LOG]!><time="15:37:25.938-180" date="08-05-2014" component="ccmsetup" context="" type="1" thread="5432" file="ccmsetup.cpp:9763">

  • CcmSetup failed with error code 0x80070643

    I`m running Windows 2012 r2 with SCCM 2012 R2.
    Installed SCCM without any problems, but now I try to install the client and that`s not working.
    Tried to install client from SCCM and tried to install cliënt manualy on the client device. Both fail.
    Operating systems: Windows 7 and 8
    Installing client on Windows 2008 server==>OK
    Errors in the ccmsetup.log on client:
    <![LOG[MSI: Action 15:59:04: Rollback. Rolling back action:]LOG]!><time="15:59:04.973-120" date="07-30-2014" component="ccmsetup" context="" type="0" thread="7280" file="msiutil.cpp:314">
    <![LOG[File C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi installation failed. Error text: ExitCode: 1603
    Action:
    ErrorMessages:
    ]LOG]!><time="15:59:13.291-120" date="07-30-2014" component="ccmsetup" context="" type="3" thread="7280" file="msiutil.cpp:876">
    <![LOG[InstallFromManifest failed 0x80070643]LOG]!><time="15:59:13.291-120" date="07-30-2014" component="ccmsetup" context="" type="3" thread="7280" file="ccmsetup.cpp:7202">
    <![LOG[A Fallback Status Point has not been specified.  Message with STATEID='311' will not be sent.]LOG]!><time="15:59:13.291-120" date="07-30-2014" component="ccmsetup" context="" type="1" thread="7280"
    file="ccmsetup.cpp:9763">
    <![LOG['Configuration Manager Client Retry Task' is scheduled to run at 07/30/2014 08:59:13 PM (local) 07/30/2014 06:59:13 PM (UTC) time with arguments ' "/mp:cap-sccm01" "SMSSITECODE=CAP" /RetryWinTask:1'.]LOG]!><time="15:59:13.291-120"
    date="07-30-2014" component="ccmsetup" context="" type="1" thread="7144" file="wintask.cpp:315">
    <![LOG[Creating Windows Task Scheduler folder 'Microsoft\Configuration Manager'...]LOG]!><time="15:59:13.291-120" date="07-30-2014" component="ccmsetup" context="" type="0" thread="7144" file="wintask.cpp:160">
    <![LOG[CcmSetup failed with error code 0x80070643]LOG]!><time="15:59:13.291-120" date="07-30-2014" component="ccmsetup" context="" type="1" thread="7144" file="ccmsetup.cpp:10879">
    Errors in ccm.log on server
    ---> Unable to connect to WMI (root\ccm) on remote machine "CAP-LT24", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 30-7-2014 15:47:56 6248 (0x1868)
    Execute query exec [sp_CP_SetLastErrorCode] 2097152008, 0 SMS_CLIENT_CONFIG_MANAGER 30-7-2014 15:47:57 6248 (0x1868)
    Additonal Info: On the client devices we had Windows ITunes. Uninstalled Windows ITunes, but no effect.
    Please advise

    Hi,
    How about MicrosoftPolicyPlatformSetup.msi.log ?
    There is a similar problem in the blog below. You could have a look.
    http://blogs.msdn.com/b/george_bethanis/archive/2013/02/04/cm12-upgrade-of-a-client-to-sp1-fails-with-error-microsoftpolicyplatformsetup-msi-installation-failed-exit-code-1603.aspx
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • CcmSetup failed with error code 0x8004100e - CcmGetOSVersion failed with 0x8004100e

    Hi ,
    the installation failed for clients with the following errors
    CcmSetup failed with error code 0x8004100e
    CcmGetOSVersion failed with 0x8004100e
    SCCM Verion 2012 R2  (Upgraded from 2012)
    Client O.S 2008 R2 SP1
    Ramy

    Hi Jason,
    please check this logs
    ==========[ ccmsetup started in process 9516 ]==========    ccmsetup    8/14/2014 4:29:51 PM    10476 (0x28EC)
    Running on platform X64    ccmsetup    8/14/2014 4:29:51 PM    10476 (0x28EC)
    Updated security on object C:\Windows\ccmsetup\cache\.    ccmsetup    8/14/2014 4:29:51 PM    10476 (0x28EC)
    Launch from folder C:\Windows\ccmsetup\    ccmsetup    8/14/2014 4:29:51 PM    10476 (0x28EC)
    CcmSetup version: 5.0.7958.1000    ccmsetup    8/14/2014 4:29:51 PM    10476 (0x28EC)
    In ServiceMain    ccmsetup    8/14/2014 4:29:51 PM    9472 (0x2500)
    Successfully started the ccmsetup service    ccmsetup    8/14/2014 4:29:51 PM    8180 (0x1FF4)
    Deleted file C:\Windows\ccmsetup\ccmsetup.exe.download    ccmsetup    8/14/2014 4:29:51 PM    8180 (0x1FF4)
    Folder 'Microsoft\Configuration Manager' not found. Task does not exist.    ccmsetup    8/14/2014 4:29:51 PM    8180 (0x1FF4)
    CcmSetup is exiting with return code 0    ccmsetup    8/14/2014 4:29:51 PM    8180 (0x1FF4)
    All other instances of ccmsetup have completed.    ccmsetup    8/14/2014 4:29:51 PM    5732 (0x1664)
    Attempt to delete ccmsetup.exe failed (5)    ccmsetup    8/14/2014 4:29:52 PM    5732 (0x1664)
    Attempt to delete ccmsetup.exe failed (5)    ccmsetup    8/14/2014 4:29:53 PM    5732 (0x1664)
    Attempt to delete ccmsetup.exe failed (5)    ccmsetup    8/14/2014 4:29:54 PM    5732 (0x1664)
    Attempt to delete ccmsetup.exe failed (5)    ccmsetup    8/14/2014 4:29:55 PM    5732 (0x1664)
    Attempt to delete ccmsetup.exe failed (5)    ccmsetup    8/14/2014 4:29:56 PM    5732 (0x1664)
    Attempt to delete ccmsetup.exe failed (5)    ccmsetup    8/14/2014 4:29:57 PM    5732 (0x1664)
    Attempt to delete ccmsetup.exe failed (5)    ccmsetup    8/14/2014 4:29:58 PM    5732 (0x1664)
    Attempt to delete ccmsetup.exe failed (5)    ccmsetup    8/14/2014 4:29:59 PM    5732 (0x1664)
    Attempt to delete ccmsetup.exe failed (5)    ccmsetup    8/14/2014 4:30:01 PM    5732 (0x1664)
    Attempt to delete ccmsetup.exe failed (5)    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    Failed to delete C:\Windows\ccmsetup\ccmsetup.exe (5). Renaming and queuing for deletion on reboot.    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    Successfully renamed C:\Windows\ccmsetup\ccmsetup.exe to C:\Windows\ccmsetup\DELEB07.tmp and queued for deletion on reboot.    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    Downloading file C:\Setup\Client\ccmsetup.exe    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    Downloading C:\Setup\Client\ccmsetup.exe to C:\Windows\ccmsetup\ccmsetup.exe    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    File download 16% complete (262144 of 1614520 bytes).    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    File download 32% complete (524288 of 1614520 bytes).    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    File download 48% complete (786432 of 1614520 bytes).    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    File download 64% complete (1048576 of 1614520 bytes).    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    File download 81% complete (1310720 of 1614520 bytes).    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    File download 97% complete (1572864 of 1614520 bytes).    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    File download 100% complete (1614520 of 1614520 bytes).    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    Download complete.    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    Failed to create the ccmsetup service 0x(80070431)    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    A Fallback Status Point has not been specified.  Message with STATEID='301' will not be sent.    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    CcmSetup failed with error code 0x80070431    ccmsetup    8/14/2014 4:30:02 PM    5732 (0x1664)
    CheckAndLogOSInformation failed with 0x8004100e    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /source:"C:\Setup\Client" "SMSSLP=ldcsccm1v.linkdc.local" "SMSSITECODE=ldc" "DNSSUFFIX=linkdc.local"    ccmsetup  
     8/14/2014 4:40:16 PM    9472 (0x2500)
    Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /source:"C:\Setup\Client" "SMSSLP=ldcsccm1v.linkdc.local" "SMSSITECODE=ldc" "DNSSUFFIX=linkdc.local"    ccmsetup    8/14/2014
    4:40:16 PM    9472 (0x2500)
    SslState value: 224    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    CCMHTTPPORT:    80    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    CCMHTTPSPORT:    443    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    CCMHTTPSSTATE:    224    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    CCMHTTPSCERTNAME:        ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    SMSSLP:    ldcsccm1v.linkdc.local    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    FSP:        ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    CCMFIRSTCERT:    1    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    Config file:          ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    Retry time:       10 minute(s)    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    MSI log file:     C:\Windows\ccmsetup\Logs\client.msi.log    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    MSI properties:    SMSSLP="ldcsccm1v.linkdc.local" SMSSITECODE="ldc" DNSSUFFIX="linkdc.local" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"  
     ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    Source List:    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
                      C:\Setup\Client    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    MPs:    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
                      None    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    No version of the client is currently detected.    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    Folder 'Microsoft\Configuration Manager' not found. Task does not exist.    ccmsetup    8/14/2014 4:40:16 PM    9472 (0x2500)
    Updated security on object C:\Windows\ccmsetup\.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Running as user "SYSTEM"    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Detected 28163 MB free disk space on system drive.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Checking Write Filter Status.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    This is not a supported write filter device. We are not in a write filter maintenance mode.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=ldc))'    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>480</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F3308201DBA00302010202107B6F93150C5A958F411F813122BF4CEA300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303832363136353035335A180F32313133303830333136353035335A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100A8BD6E83FE1AE591E87E59E17F6E3119068166C37F0F02911246B003878146DD4EF98F26A8E37DAB3D557545913127A780CDD9D8DB46E7A1BD52B28BB8FD42E21339065C8A24EA06EEAEFB0177DAFE0E62DB30ECCA68DB1B6EA3BC985D2D26DDBF180938BBEA36F56E5604FED265E2E01154AC495C5269D577C10B523C6B3CDCBFEE44961D08ED5E298381F927C49494E35FA5634B1C56847A55EFB52B0E32BFACE704E0A2F44A39D9D656B9097BF93AF2466242CC2CB050B02734E46A0EC3553249599BD5CC5917CC408938FAFF8FF097B434FDD9F9174AF6C533FE220E93929DF082FCE7A11143AB7B5D2537829D18B6F756B85A68B0B7C520728165BF4EAB0203010001A33B303930210603551D11041A301882164C44435343434D31562E4C696E6B44432E4C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100477430C70E8B5E48E78912C71B22C86DCE5ED91A429A786346B1EE5C076697C080056C52B1649FA4366D7AEAC08B35AC01734365D2A38B7A797DF1420027BFA103DEF91109F0025A20DA6C592807F134C7283219A88D6B5592A1993134A2649D6F6F663BCE0D872675D260D9D61C59EE1D36A602110839D5CC6F15C7FF842C92A118A0BCECD302F36235FFB79EF37054FB998D3666337B3C5DBBF6C1553600044CD4940FBDDE18EAE3A2B94E31FEC72DA32A7B8BC86A8868B92F782547B799E898A3B1460576A70773F58FE9D2D3363BF04796A91E66155E419B9E50946287A213C4E8A3BB81BA1FEEB9E9EDF86EA4627F7E421281532B0B340834F2A92C3215</SiteSigningCert></SecurityConfiguration><RootSiteCode>LDC</RootSiteCode><CCM>
    <CommandLine>SMSSITECODE=LDC</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain
    Value="LinkDC.Local" /><Forest Value="LinkDC.Local" /></ClientOperationalSettings>'    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    The MP name retrieved is 'LDCSCCM1V.LinkDC.Local' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>'    ccmsetup  
     8/14/2014 4:40:17 PM    9472 (0x2500)
    MP 'LDCSCCM1V.LinkDC.Local' is compatible    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Retrieved 1 MP records from AD for site 'ldc'    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Retrived site version '5.00.7958.1000' from AD for site 'ldc'    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    SiteCode:         ldc    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    SiteVersion:      5.00.7958.1000    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Deleted file C:\Windows\ccmsetup\client.msi    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Deleted file C:\Windows\ccmsetup\client.msi.download    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    No MPs were specified from commandline or the mobileclient.tcf.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Downloading file ccmsetup.cab    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Determining source location...    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Found accessible source: C:\Setup\Client    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Found available source C:\Setup\Client\    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Downloading C:\Setup\Client\ccmsetup.cab to C:\Windows\ccmsetup\ccmsetup.cab    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    File download 100% complete (9662 of 9662 bytes).    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Deleted file C:\Windows\ccmsetup\ccmsetup.cab    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Download complete.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    C:\Windows\ccmsetup\ccmsetup.cab is Microsoft trusted.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Successfully loaded ccmsetup manifest file.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Checking if manifest version '5.00.7958.1000' is newer than the ccmsetup version '5.0.7958.1000'    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    Running from temp downloaded folder or manifest is not newer than ccmsetup.    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    CcmGetOSVersion failed with 0x8004100e    ccmsetup    8/14/2014 4:40:17 PM    9472 (0x2500)
    A Fallback Status Point has not been specified.  Message with STATEID='301' will not be sent.    ccmsetup    8/14/2014 4:40:17 PM    10476 (0x28EC)
    'Configuration Manager Client Retry Task' is scheduled to run at 08/14/2014 09:40:17 PM (local) 08/14/2014 06:40:17 PM (UTC) time with arguments ' /source:"C:\Setup\Client" "SMSSLP=ldcsccm1v.linkdc.local" "SMSSITECODE=ldc" "DNSSUFFIX=linkdc.local"
    /RetryWinTask:1'.    ccmsetup    8/14/2014 4:40:17 PM    10476 (0x28EC)
    Creating Windows Task Scheduler folder 'Microsoft\Configuration Manager'...    ccmsetup    8/14/2014 4:40:17 PM    10476 (0x28EC)
    CcmSetup failed with error code 0x8004100e    ccmsetup    8/14/2014 4:40:17 PM    10476 (0x28EC)
    Ramy

Maybe you are looking for