Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice

Moving file failed...

Discussion in '2019.3 Beta' started by Hyp-X, Oct 11, 2019.

  1. Hyp-X

    Hyp-X

    Joined:
    Jun 24, 2015
    Posts:
    438
    Hi,

    I started trying 2019.3.0b6 for development, and I'm getting a lot of "Moving file failed" issue.
    This is where Unity comes up with a dialog with [Try again] [Force quit] options.
    I haven't seen this since early 2018 builds...

    Looks like this, but it's always a different file
    Code (CSharp):
    1. Start importing Assets/Scripts/Game/MetaGame/MetaGame.cs using Guid(51f33f5d83cd72345a89b3b450e51578) Importer(-1,)
    2. Force Quit pressed for Moving file failed: Moving E:/Work/Project.2019.3/Temp/UnityTempFile-eb5aba1f7aca71c438ea018622a3d06a to E:/Work/Project.2019.3/Library/TempArtifacts/Primary/51f33f5d83cd72345a89b3b450e51578: The system cannot find the path specified.
    3.  
    Last time it was ProjectSettings/ProjectSettings.asset ...

    Does anyone see this, or is it just me or our project?
     
  2. Peter77

    Peter77

    QA Jesus

    Joined:
    Jun 12, 2013
    Posts:
    6,619
    I see this pretty much every time i trigger a build, that something can't be moved from staging to the output directory. I thought this was a local problem on my end, but perhaps it's not. Then I can just press "Retry" in the error dialog and it works.
     
    Last edited: Oct 12, 2019
  3. spacefrog

    spacefrog

    Joined:
    Jun 14, 2009
    Posts:
    734
    I usually get those prompts when some Windows Explorer window in the background points to one of the <Project>/Temp folders ( essentially where the temporary output/staging happens )
     
    cortexa and aminre like this.
  4. Hyp-X

    Hyp-X

    Joined:
    Jun 24, 2015
    Posts:
    438
    It is still happening in 2019.3.0f6
    Just occurred 4x in our team withing and our

    upload_2020-2-3_11-23-28.png

    After Force Quit, Unity crashes 100% on the next restart:

    Code (CSharp):
    1. 0x00007FF7ECD2DD21 (Unity) IsMetaInfoSame
    2. 0x00007FF7ECD32CBE (Unity) RefreshInternalV2
    3. 0x00007FF7ECD35331 (Unity) StopAssetImportingV2
    4. 0x00007FF7ECD2C816 (Unity) InitialScriptRefreshV2
    5. 0x00007FF7EC296501 (Unity) Application::InitializeProject
    6. 0x00007FF7ECBF0648 (Unity) WinMain
    7. 0x00007FF7EFB6C602 (Unity) __scrt_common_main_seh
    8. 0x00007FF8BB8C7BD4 (KERNEL32) BaseThreadInitThunk
    9. 0x00007FF8BC7ECED1 (ntdll) RtlUserThreadStart
    10.  
    After the 2nd restart Unity starts again
     
  5. Hyp-X

    Hyp-X

    Joined:
    Jun 24, 2015
    Posts:
    438
    Oops, it was an error on our side.

    Our version control tool aggressively deletes empty folders and it deleted the Library/TempArtifacts folder...
     
    kkjusdoit, BuzzKirill and LeonhardP like this.
  6. BuzzKirill

    BuzzKirill

    Joined:
    Nov 14, 2017
    Posts:
    48
    For me, it was either that, or the Remove Empty Folders option under Assets menu. I both disabled that and quit SourceTree, and then it was fine. (I was trying to use "MeshBaker" asset, just in case somebody searches it up)
     
  7. greysun

    greysun

    Joined:
    Feb 23, 2017
    Posts:
    9
    Look for multiple instances of UnityHub and or Unity Editor running in the background. That fixed it for me. For some reason there were 5 Unity Hubs running
     
    BHS, SuperVoximus, yanhongw and 3 others like this.
  8. Wiechciu

    Wiechciu

    Joined:
    Apr 24, 2023
    Posts:
    2
    I also just had that issue and it helped to just close Visual Studio and try again.
     
    JellyfischStudios and kyuskoj like this.