Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
MDT2012 Offline Capture CNAME Loop Detected

Unanswered MDT2012 Offline Capture CNAME Loop Detected

  • Monday, October 01, 2012 10:49 PM
     
     
    Sign In to Vote
    0

    Failed to run the action: Offline User State Capture.
    CNAME loop detected. (Error: 000025EB; Source: Windows)    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Sending status message . . .    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Set a global environment variable _SMSTSLastActionRetCode=9707    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Set a global environment variable _SMSTSLastActionSucceeded=false    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Clear local default environment    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Let the parent group (Offline User State Capture) decides whether to continue execution    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Let the parent group (Preinstall) decide whether to continue execution    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    The execution of the group (Preinstall) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Failed to run the last action: Offline User State Capture. Execution of task sequence failed.
    CNAME loop detected. (Error: 000025EB; Source: Windows)    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Sending status message . . .    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767)    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Task Sequence Engine failed! Code: enExecutionFail    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    ****************************************************************************    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0)
    Task sequence execution failed with error code 80004005    TSManager    10/01/2012 3:22:59 PM    1200 (0x04B0

    This error occurs during a lite touch deployment in WinPE.

     

All Replies

  • Tuesday, October 02, 2012 2:21 AM
     
     
    Sign In to Vote
    0

    Try posting some info rather than just a log file.

    Blog: http://scriptimus.wordpress.com

     
  • Tuesday, October 02, 2012 4:42 AM
     
     
    Sign In to Vote
    0
    CNAME error may point to a bad XML file. Can validate you USMT XML files?
     
  • Tuesday, October 02, 2012 2:56 PM
     
     
    Sign In to Vote
    0
    XML is good, I have used the same XML in USMT outside a lite touch scenario, but it fails in WinPE.
     
  • Wednesday, October 03, 2012 3:29 PM
     
     
    Sign In to Vote
    0

    I've been getting an error message along the same lines. I have MDT 2012 Update 1 (with Windows ADK; USMT5, etc) installed on a Server 2008 R2 system. I've created a standard task sequence, and when I perform a lite touch deployment and choose the option to capture the user settings I get this error:

    ZTI ERROR - Non-zero return code from Scanstate, RC=11

    FAILURE (9707): Non-zero return code from USMT capture, rc=11

    Litetouch deployment failed, Return Code = -2147467259 0x80004005

    Failed to run action: Offline User State Capture

    CNAME loop detected. (Error: 000025EB; Source: Windows)

    The execution of the group (Preinstall) has failed and the execution has been aborted. An action failed.

    Operation aborted (Error: 80004004; Source: Windows)

    Failed to run the last action: Offline User State Capture. Execution of task sequence failed.

    CNAME loop detected. (Error: 000025EB; Source: Windows)

    Task Sequence Engine failed! Code: enExecutionFail

    Task sequence execution failed with error code 80004005

    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

    If I choose to not capture any user settings, the task sequence (loading a base copy of Windows 7 x64) completes fine. This is mostly for testing purposes as I am attempting to capture user data and settings from a base windows 7 x64 image. I also created a new default standard task sequence and got the same error when I attempted to capture the user data and settings. I looked all over the web for info on this error, but was unable to find any solutions.

    Any help or pointers would be greatly appreciated. Thanks!



    • Edited by T Dawson Wednesday, October 03, 2012 3:29 PM
    • Edited by T Dawson Wednesday, October 03, 2012 3:30 PM spacing issue
    •  
     
  • Wednesday, October 03, 2012 3:37 PM
     
     
    Sign In to Vote
    0
    do you have any third party encryption installed? I had to uninstall and decrypt my VM to work, but it is failing on a physical box.
     
  • Wednesday, October 03, 2012 3:54 PM
     
     
    Sign In to Vote
    0
    I'm doing all my testing on a physical box, bit locker is disabled (no other encryption software installed), and the current image on the system is just a base install on Windows 7 x64, so I'm not sure what would cause the user state capture to fail.
    • Edited by T Dawson Wednesday, October 03, 2012 3:55 PM edit
    •  
     
  • Wednesday, October 03, 2012 6:48 PM
     
     
    Sign In to Vote
    0

    Bad XML, bad combo fo XMLs.

    Start with MigUser only, than add miggapp and try, etc.

     
  • Wednesday, October 03, 2012 8:20 PM
     
     
    Sign In to Vote
    0

    All of the XML's I'm using are the default ones that are setup with MDT 2012, in the task sequence it calls the ZTIUserState.wsf script that comes default with everything. Is there something I need to change in the script to make it work? I haven't changed any of the default settings so I'm not sure where I need to go to fix this error.

    I apologize for sounding crude, I'm trying to read as much as I can about MDT as I'm very new to it. Would removing USMT 5 and using USMT 4 work better?

     
  • Wednesday, October 03, 2012 10:18 PM
     
     
    Sign In to Vote
    0
    I managed to fix the error by removing USMT 5 from the tools section of the deployment share and replacing them with the USMT 4 tools. I'm not sure why the USMT 5 tool would fail, but the USMT 4 tool works fine.

    • Edited by T Dawson Wednesday, October 03, 2012 10:18 PM
    •  
     
  • Wednesday, October 03, 2012 10:24 PM
     
     
    Sign In to Vote
    0

    too bad you failed to mention USMT 5 on your first post.

    And that proves it was an XML error,...

     
  • Thursday, October 04, 2012 3:12 PM
     
     
    Sign In to Vote
    0

    But I did mention USMT 5 (Windows ADK; USMT5) on my first post, and with using MDT 2012 why would USMT 5 fail with default settings? I thought that MDT 2012 Update 1 and USMT 5 worked well together...

    The only thing I did was replace the tool with the older one. I didn't edit or change any xml files.

    • Edited by T Dawson Thursday, October 04, 2012 3:13 PM
    •  
     
  • Friday, March 08, 2013 7:55 PM
     
     
    Sign In to Vote
    0

    This could be a possible fix, pasted from another site

    Hey guys,

    I just got this weird issue -- seems a bunch of others got it too (look here:  http://social.technet.microsoft.com/Forums/en-US/mdt/thread/78ba73ee-9775-4a2d-a4f5-3b95e7bb1976 - and here: http://social.technet.microsoft.com/Forums/en-US/mdt/thread/048f0c99-393c-40b5-b140-3095f65ca438)

    I'm using USMT 5 with MDT 2012.  In the UserCapture.log, it seems that the issue is that it's looking for a version of Windows, but doesn't find it.  Makes sense, since I'm running in Windows PE.  But this error doesn't occur with USMT 4. Digging in the ZTIUserState.wsf file, I found an if cmd that does this:

    If sUSMTVersion = "USMT5" then
    If Left(oEnvironment.Item("ImageBuild"),3) = "6.1" then
    oLogging.CreateEntry "Special Case for USMT 5.0 scanstate for Windows 7 Target. /targetWindows7", LogTypeInfo
    sBaseArgs = sBaseArgs & " /targetWindows7"
    End if
    End if

    By editing out the sBaseArgs = sBaseArgs & " /targetWindows7" section, the deployment works no problem.  This section doesn't get called for USMT 3 or 4.  So I was wondering, what does this part do??  Is it some type of necessary command,  and if so, how does one get it to work in Windows PE, since it errors out because it's not running in the full-blown OS??

    Thanks