deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

CI Update

Browse Source
This commit is contained in:
VSC-Service-Account
2019-06-04 22:13:57 +00:00
parent 13bd3bfe64
commit 858476cf2f
1820 changed files with 28427 additions and 28190 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
windows/deployment/usmt/usmt-return-codes.md
View File

@ -46,7 +46,7 @@ Non-fatal Errors
Fatal Errors
As a best practice, we recommend that you set verbosity level to 5, **/v***:5*, on the **ScanState**, **LoadState**, and **USMTUtils** command lines so that the most detailed reporting is available in the respective USMT logs. You can use a higher verbosity level if you want the log files output to go to a debugger.
As a best practice, we recommend that you set verbosity level to 5, **/v**<em>:5</em>, on the **ScanState**, **LoadState**, and **USMTUtils** command lines so that the most detailed reporting is available in the respective USMT logs. You can use a higher verbosity level if you want the log files output to go to a debugger.
## <a href="" id="bkmk-errormessages"></a>USMT Error Messages
@ -130,7 +130,7 @@ The following table lists each return code by numeric value, along with the asso
<tr class="even">
<td align="left"><p></p></td>
<td align="left"><p></p></td>
<td align="left"><p>/encrypt can't be used with /nocompress</p></td>
<td align="left"><p>/encrypt can&#39;t be used with /nocompress</p></td>
<td align="left"><p>Review ScanState log or LoadState log for details about command-line errors.</p></td>
<td align="left"><p></p></td>
</tr>
@ -144,14 +144,14 @@ The following table lists each return code by numeric value, along with the asso
<tr class="even">
<td align="left"><p></p></td>
<td align="left"><p></p></td>
<td align="left"><p>/genconfig can't be used with most other options</p></td>
<td align="left"><p>/genconfig can&#39;t be used with most other options</p></td>
<td align="left"><p>Review ScanState log or LoadState log for details about command-line errors.</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
<td align="left"><p></p></td>
<td align="left"><p></p></td>
<td align="left"><p>/genmigxml can't be used with most other options</p></td>
<td align="left"><p>/genmigxml can&#39;t be used with most other options</p></td>
<td align="left"><p>Review ScanState log or LoadState log for details about command-line errors.</p></td>
<td align="left"><p></p></td>
</tr>
@ -438,7 +438,7 @@ The following table lists each return code by numeric value, along with the asso
<tr class="even">
<td align="left"><p>27</p></td>
<td align="left"><p>USMT_INVALID_STORE_LOCATION</p></td>
<td align="left"><p>A store path can't be used because an existing store exists; specify /o to overwrite</p></td>
<td align="left"><p>A store path can&#39;t be used because an existing store exists; specify /o to overwrite</p></td>
<td align="left"><p>Specify /o to overwrite an existing intermediate or migration store.</p></td>
<td align="left"><p>Setup and Initialization</p></td>
</tr>
@ -599,7 +599,7 @@ The following table lists each return code by numeric value, along with the asso
<tr class="odd">
<td align="left"><p></p></td>
<td align="left"><p></p></td>
<td align="left"><p>A store path can't be used because it contains data that could not be overwritten</p></td>
<td align="left"><p>A store path can&#39;t be used because it contains data that could not be overwritten</p></td>
<td align="left"><p>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 <strong>USMTUtils /rd</strong> command to delete the store.</p></td>
<td align="left"><p></p></td>
</tr>
@ -676,7 +676,7 @@ The following table lists each return code by numeric value, along with the asso
<tr class="even">
<td align="left"><p>41</p></td>
<td align="left"><p>USMT_PREFLIGHT_FILE_CREATION_FAILED</p></td>
<td align="left"><p>Can't overwrite existing file</p></td>
<td align="left"><p>Can&#39;t overwrite existing file</p></td>
<td align="left"><p>The Progress log could not be created. Verify that the location is valid and that you have write access.</p></td>
<td align="left"><p>Setup and Initialization</p></td>
</tr>
@ -691,7 +691,7 @@ The following table lists each return code by numeric value, along with the asso
<td align="left"><p>42</p></td>
<td align="left"><p>USMT_ERROR_CORRUPTED_STORE</p></td>
<td align="left"><p>The store contains one or more corrupted files</p></td>
<td align="left"><p>Review UsmtUtils log for details about the corrupted files. For information on how to extract the files that are not corrupted, see [Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md).</p></td>
<td align="left"><p>Review UsmtUtils log for details about the corrupted files. For information on how to extract the files that are not corrupted, see <a href="usmt-extract-files-from-a-compressed-migration-store.md" data-raw-source="[Extract Files from a Compressed USMT Migration Store](usmt-extract-files-from-a-compressed-migration-store.md)">Extract Files from a Compressed USMT Migration Store</a>.</p></td>
<td align="left"><p></p></td>
</tr>
<tr class="odd">
@ -767,7 +767,7 @@ The following table lists each return code by numeric value, along with the asso
</tbody>
</table>
 
## Related topics
@ -776,9 +776,9 @@ The following table lists each return code by numeric value, along with the asso
[Log Files](usmt-log-files.md)