none
SCCM 2012 USMT Hardlink restore is failing with error code = 27 RRS feed

  • Question

  • I am trying to restore the user data with USMT hard link. I am able to capture the user state to c:\userstate, but while restore its failing with below error. As per smsts.log its connecting to the right store (c:\userstate)

    error from loadstate.log

    2019-11-14 06:57:16, Info                  [0x000000] Command line: C:\_SMSTaskSequence\Packages\xxx003F6\amd64\loadstate.exe C:\UserState /ue:machinename\* /c /l:C:\WINDOWS\CCM\Logs\SMSTSLog\loadstate.log /progress:C:\WINDOWS\CCM\Logs\SMSTSLog\loadstateprogress.log /i:C:\_SMSTaskSequence\Packages\xxX003F6\amd64\MigApp.xml /i:C:\_SMSTaskSequence\Packages\xxX003F6\amd64\Migdocs.xml
    2019-11-14 06:57:16, Info                  [0x000000] Failed.[gle=0x00000006]
    2019-11-14 06:57:16, Info                  [0x000000]   An error occurred processing the command line.
      Invalid store path; check the store parameter and/or file system permissions[gle=0x00000006]
    2019-11-14 06:57:16, Info                  [0x000000] USMT Completed at 2019/11/14:06:57:16.422[gle=0x00000006]
    2019-11-14 06:57:16, Info                  [0x000000] ----------------------------------- USMT ERROR SUMMARY -----------------------------------[gle=0x00000006]
    2019-11-14 06:57:16, Info                  [0x000000] * USMT error code 27: [gle=0x00000006]
    2019-11-14 06:57:16, Info                  [0x000000] +-----------------------------------------------------------------------------------------[gle=0x00000006]
    2019-11-14 06:57:16, Info                  [0x000000] | An error occurred processing the command line.[gle=0x00000006]
    2019-11-14 06:57:16, Info                  [0x000000] | Invalid store path; check the store parameter and/or file system permissions[gle=0x00000006]



    Midhun.PS

    Thursday, November 14, 2019 1:16 PM

Answers

  • Thanks, 

    it was a mistake from our side as restore variable name was OSDMigrateAdditionalCaptureOptions as it was copied from capture. Post change the variable as OSDMigrateAdditionalRestoreOptions  restore worked fine. 


    Midhun.PS

    Thursday, November 28, 2019 7:00 AM

All replies

  • Hi,

    USMT error code 27 means USMT_INVALID_STORE_LOCATION, Invalid store path. Please help check the store parameter and/or file system permissions. Make sure that the store path is accessible and that the proper permission levels are set.

    Please refer to:
    Unable to migrate Profiles
    USMT Return Codes

    Thanks for your time.

    Best regards,
    Simon Ren

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 15, 2019 7:37 AM
  • Hi,

    May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

    Thanks and regards,
    Simon 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, November 18, 2019 1:59 AM
  • Thanks, 

    it was a mistake from our side as restore variable name was OSDMigrateAdditionalCaptureOptions as it was copied from capture. Post change the variable as OSDMigrateAdditionalRestoreOptions  restore worked fine. 


    Midhun.PS

    Thursday, November 28, 2019 7:00 AM
  • Hi,

    Thank you very much for posting in TechNet and your feedback. Here's a short summary for the problem.

    Problem/Symptom:
    ===================
    USMT Hardlink restore is failing with error code = 27

    Solution:
    ===================
    The restore variable name was OSDMigrateAdditionalCaptureOptions as it was copied from capture. Post change the variable as OSDMigrateAdditionalRestoreOptions  restore worked fine.

    Thanks again for your time!

    Best regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 29, 2019 2:18 AM