none
ZTI ERROR - Non-zero return code by ZTIUserState, rc = 38 RRS feed

  • Question

  • Hi, we're using MDT 2013 (and USMT5) to capture and deploy images. Last week a colleague captured user data and tried to restore the mig-file on another newly installed pc. But he got an error :ZTI ERROR - Non-zero return code by ZTIUserState, rc = 38 (38 is a Windows System Error code and means : "reached the end of the file")

    This info comes from the smsts.log

    Start executing the command line: cscript.exe "%SCRIPTROOT%\ZTIUserState.wsf" /restore		01/01/1601 00:00:00	0 (0x0000)
    !--------------------------------------------------------------------------------------------!		01/01/1601 00:00:00	0 (0x0000)
    Expand a string: 		01/01/1601 00:00:00	0 (0x0000)
    Executing command line: cscript.exe "%SCRIPTROOT%\ZTIUserState.wsf" /restore		01/01/1601 00:00:00	0 (0x0000)
    Process completed with exit code 38		01/01/1601 00:00:00	0 (0x0000)
    !--------------------------------------------------------------------------------------------!		01/01/1601 00:00:00	0 (0x0000)
    Failed to run the action: Restore User State. 
    Reached the end of the file. (Error: 00000026; Source: Windows)		01/01/1601 00:00:00	0 (0x0000)
    Sending status message . . .		01/01/1601 00:00:00	0 (0x0000)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request		01/01/1601 00:00:00	0 (0x0000)
    Set a global environment variable _SMSTSLastActionRetCode=38		01/01/1601 00:00:00	0 (0x0000)
    Set a global environment variable _SMSTSLastActionSucceeded=false		01/01/1601 00:00:00	0 (0x0000)
    Clear local default environment		01/01/1601 00:00:00	0 (0x0000)
    Let the parent group (State Restore) decides whether to continue execution		01/01/1601 00:00:00	0 (0x0000)
    The execution of the group (State Restore) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)		01/01/1601 00:00:00	0 (0x0000)
    Failed to run the last action: Restore User State. Execution of task sequence failed.
    Reached the end of the file. (Error: 00000026; Source: Windows)		01/01/1601 00:00:00	0 (0x0000)
    Sending status message . . .		01/01/1601 00:00:00	0 (0x0000)

    Other info in the BDD-log

    ------ Performing State Restore ------	ZTIUserState	30/03/2015 13:50:57	0 (0x0000)
    ZTI Beginning user state restore.	ZTIUserState	30/03/2015 13:50:57	0 (0x0000)
    Event 41007 sent: ZTI Beginning user state restore.	ZTIUserState	30/03/2015 13:50:57	0 (0x0000)
    About to run command: cmd /c ""C:\MININT\USMT\X64\loadstate.exe" "\\our-enterprise\USMT\PORT-ALH-OLD" /i:WNB.XML /i:MigNotes.xml /i:MigDocs.xml /c /r:10 /w:5 /v:13 /uel:30 /lac /ui:Administrator  /i:"C:\MININT\USMT\X64\MigApp.xml" /i:"C:\MININT\USMT\X64\Migdocs.xml" /config:"C:\MININT\USMT\X64\ZTIUserState_Config.xml" /l:C:\MININT\SMSOSD\OSDLOGS\USMTrestore.log  /progress:C:\MININT\SMSOSD\OSDLOGS\USMTrestore.prg > nul 2>&1"	ZTIUserState	30/03/2015 13:50:57	0 (0x0000)
    Return code from command = 38	ZTIUserState	30/03/2015 13:51:51	0 (0x0000)
    ZTI ERROR - Non-zero return code from Loadstate, RC = 38	ZTIUserState	30/03/2015 13:51:51	0 (0x0000)
    Event 41007 sent: ZTI ERROR - Non-zero return code from Loadstate, RC = 38	ZTIUserState	30/03/2015 13:51:51	0 (0x0000)
    ZTI USMT LOADSTATE reported 0 errors and 0 warnings.	ZTIUserState	30/03/2015 13:51:51	0 (0x0000)
    Event 41010 sent: ZTI USMT LOADSTATE reported 0 errors and 0 warnings.	ZTIUserState	30/03/2015 13:51:52	0 (0x0000)
    ZTIUserState COMPLETED.  Return Value = 38	ZTIUserState	30/03/2015 13:51:52	0 (0x0000)
    Removing drive letter E: from the boot drive.	ZTIUserState	30/03/2015 13:51:52	0 (0x0000)
    DISKPART + list volume	ZTIUserState	30/03/2015 13:51:52	0 (0x0000)
    DISKPART + Select volume E:	ZTIUserState	30/03/2015 13:51:52	0 (0x0000)
    DISKPART + REMOVE LETTER=E: NOERR	ZTIUserState	30/03/2015 13:51:52	0 (0x0000)
    DISKPART + exit	ZTIUserState	30/03/2015 13:51:52	0 (0x0000)
    About to run command: cscript.exe //nologo "\\our-enterprise\DeploymentShare\Scripts\ztiRunCommandHidden.wsf" "DiskPart.exe /s C:\Users\ADMINI~1\AppData\Local\Temp\rad74A55.tmp"	ZTIUserState	30/03/2015 13:51:52	0 (0x0000)
    Microsoft Deployment Toolkit version: 6.2.5019.0	ztiRunCommandHidden	30/03/2015 13:51:52	0 (0x0000)
    The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.	ztiRunCommandHidden	30/03/2015 13:51:52	0 (0x0000)
    Write all logging text to \\our-enterprise\MDT Varia\Logs\Dynamic\PORT-ALH	ztiRunCommandHidden	30/03/2015 13:51:52	0 (0x0000)
    Validating connection to \\our-enterprise\MDT Varia\Logs\Dynamic\PORT-ALH	ztiRunCommandHidden	30/03/2015 13:51:52	0 (0x0000)
    Mapping server share: \\our-enterprise	ztiRunCommandHidden	30/03/2015 13:51:52	0 (0x0000)
    Already connected to server our-enterprise.be as that is where this script is running from.	ztiRunCommandHidden	30/03/2015 13:51:52	0 (0x0000)
    About to run command: DiskPart.exe /s C:\Users\ADMINI~1\AppData\Local\Temp\rad74A55.tmp	ztiRunCommandHidden	30/03/2015 13:51:52	0 (0x0000)
    Command has been started (process ID 4596)	ztiRunCommandHidden	30/03/2015 13:51:52	0 (0x0000)
    ZTI Heartbeat: command has been running for 0 minutes (process ID 4596)	ztiRunCommandHidden	30/03/2015 13:51:53	0 (0x0000)
    Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 4596)	ztiRunCommandHidden	30/03/2015 13:51:53	0 (0x0000)
      Console > Microsoft DiskPart version 6.1.7601	ztiRunCommandHidden	30/03/2015 13:51:53	0 (0x0000)
      Console > Copyright (C) 1999-2008 Microsoft Corporation.	ztiRunCommandHidden	30/03/2015 13:51:53	0 (0x0000)
      Console > On computer: PORT-ALH	ztiRunCommandHidden	30/03/2015 13:51:53	0 (0x0000)
      Console >   Volume ###  Ltr  Label        Fs     Type        Size     Status     Info	ztiRunCommandHidden	30/03/2015 13:51:54	0 (0x0000)
      Console >   ----------  ---  -----------  -----  ----------  -------  ---------  --------	ztiRunCommandHidden	30/03/2015 13:51:54	0 (0x0000)
      Console >   Volume 0     D                       DVD-ROM         0 B  No Media           	ztiRunCommandHidden	30/03/2015 13:51:54	0 (0x0000)
      Console >   Volume 1     E   System       NTFS   Partition    499 MB  Healthy    System  	ztiRunCommandHidden	30/03/2015 13:51:54	0 (0x0000)
      Console >   Volume 2     C   OSDisk       NTFS   Partition    232 GB  Healthy    Boot    	ztiRunCommandHidden	30/03/2015 13:51:54	0 (0x0000)
      Console > Volume 1 is the selected volume.	ztiRunCommandHidden	30/03/2015 13:51:54	0 (0x0000)
      Console > DiskPart successfully removed the drive letter or mount point.	ztiRunCommandHidden	30/03/2015 13:51:54	0 (0x0000)
      Console > Leaving DiskPart...	ztiRunCommandHidden	30/03/2015 13:51:54	0 (0x0000)
    Return code from command = 0	ztiRunCommandHidden	30/03/2015 13:51:54	0 (0x0000)
    Command has returned: 0	ZTIUserState	30/03/2015 13:51:54	0 (0x0000)
    ZTI ERROR - Non-zero return code by ZTIUserState, rc = 38	ZTIUserState	30/03/2015 13:51:54	0 (0x0000)
    Event 41002 sent: ZTI ERROR - Non-zero return code by ZTIUserState, rc = 38	ZTIUserState	30/03/2015 13:51:54	0 (0x0000)
    Command completed, return code = -2147467259	LiteTouch	30/03/2015 13:51:55	0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259  0x80004005	LiteTouch	30/03/2015 13:51:55	0 (0x0000)
    Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005	LiteTouch	30/03/2015 13:51:55	0 (0x0000)

    So the mig-file is found, the restore action starts, but it failed to run the last action. What buggers me is the "reached the end of the file". I can't find any info on the internet.

    Any idea what could be going on?

    Paul




    • Edited by KZen Muug Tuesday, March 31, 2015 7:46 AM
    Tuesday, March 31, 2015 7:23 AM

Answers

  • Thanks for the list of error codes ! It's a nice to have, even if we use USMT5.

    In the meantime I've used MigViewer.exe to open a good and a bad mig-file and the difference is quite evident :

    BAD

    GOOD

    GOOD

    The User Data Capture process must have been interrupted at a certain point and that explains why the mig-file hasn't been terminated in a proper way. And that's why I have this error code saying "reached the end of the file". I'll rerun the capture, it should be OK. I'll post the results.

    Paul



    • Edited by KZen Muug Wednesday, April 1, 2015 7:25 AM
    • Marked as answer by KZen Muug Wednesday, April 1, 2015 7:25 AM
    Wednesday, April 1, 2015 7:21 AM

All replies

  • http://blogs.technet.com/b/deploymentguys/archive/2009/01/14/usmt-error-codes.aspx

    38 is USMT_ERROR_USE_LAC

    (Local Account Create)

    https://technet.microsoft.com/en-us/library/cc766226%28v=ws.10%29.aspx#BKMK_User

    It is a USMT issue but, you can provide the additional parameters in customsettings.ini


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Tuesday, March 31, 2015 6:02 PM
    Moderator
  • Thanks for the list of error codes ! It's a nice to have, even if we use USMT5.

    In the meantime I've used MigViewer.exe to open a good and a bad mig-file and the difference is quite evident :

    BAD

    GOOD

    GOOD

    The User Data Capture process must have been interrupted at a certain point and that explains why the mig-file hasn't been terminated in a proper way. And that's why I have this error code saying "reached the end of the file". I'll rerun the capture, it should be OK. I'll post the results.

    Paul



    • Edited by KZen Muug Wednesday, April 1, 2015 7:25 AM
    • Marked as answer by KZen Muug Wednesday, April 1, 2015 7:25 AM
    Wednesday, April 1, 2015 7:21 AM