Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs

More documents

Recommendations

Info

36 USMT_ERROR_UNSUPPORTED_PL ATFORM A store path can't be used because it contains data that could not be overwritten There was an error removing the store Compliance check failure; please check the logs for details Use of /offline is not supported during apply Use /offline to run gather on this platform 37 USMT_ERROR_NO_INVALID_KEY The store holds encrypted data but the correct encryption key was not provided 38 USMT_ERROR_CORRUPTED_NOTE An error occurred during store access NCRYPTED_STORE 39 USMT_UNABLE_TO_READ_CONFIG _FILE 40 USMT_ERROR_UNABLE_CREATE_P ROGRESS_LOG Error reading Config.xml File argument is invalid for /config Error writing to the progress log A migration store could not be deleted. If you are using a hardlink migration store you might have a locked file in it. You should manually delete the store, or use usmtutils /rd command to delete the store. Review ScanState log or LoadState log for details about command-line errors. Investigate whether there is an active temporary profile on the system. The /offline command was not used while running in the Windows Preinstallation Environment (Windows PE). The /offline command was not used while running in Windows PE. Verify that you have included the correct encryption /key or /keyfile. Review ScanState log or LoadState log for details about command-line errors. Make sure that the store path is accessible and that the proper permission levels are set. Review ScanState log or LoadState log for details about command-line errors in the Config.xml file. Check the command line you used to load the Config.xml file. You can use online Help by typing / on the command line. The Progress log could not be created. Verify that the location is Setup and Initialization Setup and Initialization Setup and Initialization Setup and Initialization Setup and Initialization Page | 47
valid and that you have write access. Progress log argument is invalid for /progress The Progress log could not be created. Verify that the location is valid and that you have write access. 41 USMT_PREFLIGHT_FILE_CREATION _FAILED Can't overwrite existing file The Progress log could not be created. Verify that the location is valid and that you have write access. Invalid space estimate path. Check the Review ScanState log or LoadState parameters and/or file system permissions log for details about command-line errors. 42 USMT_ERROR_CORRUPTED_STORE The store contains one or more corrupted files Review UsmtUtils log for details about the corrupted files. For information on how to extract the files that are not corrupted, see How to Extract Files from a Compressed USMT Migration Store. 61 USMT_MIGRATION_STOPPED_NO NFATAL 71 USMT_INIT_OPERATING_ENVIRON MENT_FAILED Processing stopped due to an I/O error A Windows Win32 API error occurred An error occurred when attempting to initialize the diagnostic mechanisms such as the log USMT exited but can continue with the /c command-line option, with the optional configurable section or by using the /vsc command-line option. Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details. Data transfer has begun, and there was an error during the creation of migration store or during the apply phase. Review the ScanState log or LoadState log for details. Setup and Initialization Non-fatal Errors Fatal Errors Page | 48
Page 1 and 2: SEPTEMBER 11, 2012 Troubleshooting
Page 3 and 4: Document History Date September 6,
Page 5 and 6: Log files Windows logs There are se
Page 7 and 8: Smsts.log Main log file written by
Page 9 and 10: TaskSequenceProvider.log Useful whe
Page 11 and 12: 5204 LiteTouch.wsf The logged-on us
Page 13 and 14: 5614 LTIApply.wsf ERROR - Unable to
Page 15 and 16: 7102 ZTIConfigureADDS.wsf ERROR - M
Page 17 and 18: variable (used to control the size
Page 19 and 20: 9701 ZTIUserState.wsf Unable to fin
Page 21 and 22: Version is not supported. You must
Page 23 and 24: deployment share, but it wasn’t t
Page 25 and 26: oot sector on the boot drive. In th
Page 27 and 28: 6191 LTISysprep.wsf FAILURE: Test f
Page 29 and 30: use.”) Then BCDBoot was used to c
Page 31 and 32: emovable disk or network path. In t
Page 33 and 34: 6740 ZTIBDE.wsf FAILURE: Check to s
Page 35 and 36: 7813 ZTIDiskpart.wsf FAILURE: Verif
Page 37 and 38: means that it wasn’t able to find
Page 39 and 40: 10311 ZTIVHDCreate.wsf FAILURE: Ver
Page 41 and 42: User State Migration Tool Return Co
Page 43 and 44: An option argument is missing An op
Page 45 and 46: 12 USMT_ERROR_OPTION_PARAM_T OO_LAR
Page 47: Another process is preventing migra

Troubleshooting Windows Deployments 2012-09-11 - TechNet Blogs

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?