Share via

USMT Error Codes

  • Article

I was recently configuring the User State Migration Tool for a customer’s MDT server when, during the testing phase, the USMT began failing with an error code (‘return code’ or ‘rc’ when you read the MDT log files).  I searched the USMT documentation on TechNet looking for the explanation of what the error code meant, only to discover that I could not find any information at all.

So, after a bit of asking around internally at Microsoft, I have managed to obtain the below list of error codes.  I should point out though that this list of error codes is only for version 3.01 of the USMT, I don’t know if there are differences for any past or future versions of the tool.

 

Error code

Error text
0 USMT_SUCCESS
1 USMT_DISPLAY_HELP
2 USMT_MEMORY_FAIL
3 USMT_INVALID_PARAMETERS  (Bad command line)
4 USMT_INVALID_STORE_LOCATION
5 USMT_NO_MORE_TOKEN
6 USMT_UNABLE_SET_SCRIPTFILES
7 USMT_UNABLE_GET_SCRIPTFILES  (Can’t find XML file(s) specified in the command-line)
8 USMT_UNABLE_SET_STOREPATH
9 USMT_UNABLE_SET_USERS
10 USMT_UNABLE_FINDMIGUNITS
11 USMT_UNABLE_DOMIGRATION  (A file is in use)
12 USMT_FAILED_MIGSTARTUP  (Error in XML file ‘Bad XML’)
13 USMT_FAILED_SETMIGRATIONTYPE
14 USMT_FAILED_LOCALONLY
15 USMT_UNABLE_GET_WORKINGDIR
16 USMT_UNABLE_SETKEY
17 USMT_UNABLE_READKEY
18 USMT_TOO_LONG_KEYSTRING
19 USMT_UNABLE_SETCOMPRESSION
20 USMT_ERROR_INSUFFICIENT_RIGHTS
21 USMT_UNABLE_DELETE_STORE
22 USMT_UNABLE_SET_BENONADMIN
23 USMT_ERROR_INSUFFICIENT_STRINGBUFFER
24 USMT_ERROR_UNSUPPORTED_PLATFORM
25 USMT_ERROR_UNABLE_TOVERIFY_PLATFORM
26 USMT_UNABLE_SET_EFSMODE
27 USMT_INIT_ERROR
28 USMT_UNABLE_SET_LAC_LAE
29 USMT_ERROR_CORRUPTED_ENCRYPTED_STORE  (Store is encrypted and no or invalid key has been specified)
30 USMT_ERROR_NO_INVALID_KEY  (Store is only compressed but a key has been specified)
31 USMT_ERROR_CORRUPTED_NOTENCRYPTED_STORE
32 USMT_ERROR_LOGFILES_INSIDESTORE
33 USMT_INVALID_PLATFORM_FOR_TARGETXP
34 USMT_STORE_VALID_ONLY_FOR_XP
35 USMT_UNABLE_TO_READ_CONFIG_FILE
36 USMT_INVALID_CONFIG_FILE_FORMAT
37 USMT_ERROR_UNABLE_CREATE_LOGS
38 USMT_ERROR_USE_LAC
39 USMT_FAILED_TO_EXCLUDE_FOLDERS
40 USMT_ERROR_UNABLE_CREATE_PROGRESS_LOG
41 USMT_STATUS_CANCELLED

 

Most of the codes are pretty self-explanatory, but I have included some extra information for some of the more cryptic error messages.

This post was contributed by Daniel Oxley a consultant with Microsoft Services Spain

Comments

  • Anonymous
    January 01, 2003
    jabdip, I understand your frustration, I was the same which was why I went and found out all the codes myself (a nice benefit from working at Microsoft!).  Anyway, I have it on good authority that the next version of USMT will come with much more detailed documentation. Daniel

  • Anonymous
    January 01, 2003
    Did anyone notice that you can not "imagex /apply" the Windows 7 install.wim from the Windows 7 Beta DVD? I didn't have problem applying the wim image from build 6956. Build 7000 fails to apply the bootstrap. No "Boot" folder in C: drive, so it doesn't boot. I've notice that Windows 7 Beta installs Ultimate edition by default. That's "image" nr4 from "install.wim" my command was: "imagex /apply d:install.wim 4 c: /verify"

  • Anonymous
    January 01, 2003
    i have error. ZTI ERROR - Non-zero return code from scanstate, RC = 35 litetouch deployment failed, return code = -2147467259 0x80004005 failed to run te action: capture user state help.

  • Anonymous
    March 25, 2009
    THANK YOU!!! Why is this information so hard to obtain? Sheesh!

  • Anonymous
    May 15, 2009
    I don't get some domain accounts getting picked up, and USMT completed with success code but in the log for the problem accounts I get: LookupAccountSidW failed. Error: 0x00000534 However this error is not listed, any ideas what this is?

  • Anonymous
    May 31, 2009
    This is a Windows error.  No mapping between account names and security IDs was done.  The account most likely doesn't exist in the AD and cannot be resolved or the host has been removed from the domain or is off the domain so the account SID was not resolved.  

  • Anonymous
    August 28, 2009
    These are the posted return codes for USMT 4. There are a few differences.

  • Anonymous
    August 28, 2009
    My mistake, here is the url: http://technet.microsoft.com/en-us/library/dd823291(WS.10).aspx#BKMK_ReturnCodes

  • Anonymous
    February 27, 2015
    Capture User State failed for me as well. I had problems with our WDS imaging with deploying our upgrades of Windows XP to Windows 7 with the USMT migration phase reporting "incorrect function" and with the error 2147467259 0x80004005. In the logs for the USMT I didn't see any specific error identified but some thing changed because it worked previously. After comparing my old Deployment Share and my New Deployment Share (I kept the old one around just for reference) I noticed that in the scripts folder on the distribution share X:Distributionscripts the file ZITUserState.wsf was missing. I sure didn't delete myself and no one else had been on the server or share with delete permissions either. After copying the file from the old share to the new one I restarted the deployment process and voila! The USMT tool migrated all the users from the XP install to the Windows 7 image without any problems. I hope that this helps anyone else with this troublesome error