Possibly the same issue, though happening on different files. On Windows 7 x64 I was getting:
File library/metadata/ad/adc37ed6aacf32a4d9aca7dadadae0a8 couldn’t be written. Because moving D:/Projects/Games/HeroMaker/Temp/tempFile to D:/Projects/Games/HeroMaker/library/metadata/ad/adc37ed6aacf32a4d9aca7dadadae0a8 failed.
I recall from somewhere, perhaps unity, perhaps some other app which has having similar problems, that often Window’s indexing service will cause this issue. From memory it has something to do with the file changing, Windows goes to index it, then locks the file because it’s trying to read it at the same time the program is attempting to move it.
Quick fix in this case, right click on the project folder, select properties → general → advanced. Then click off “Allow files in this folder to have contents indexed in addition to file properties”. Click ok to let it recurse into subfolders, then delete any failed import files from your project, reimport, and it should be fine. You may need to restart at some point. Worked for me!
I can't say much about it except that I've seen somewhat similar errors on Mac OS X, and usually the best thing you can do is close Unity and reopen it (from your description it seems you already have tried it). Also, you might want to try setting the permissions a little looser for your complete projects folder (actually, I've seen a similar issue with Visual Studio which requires you to start it as admin for IIS-debugging to work ... which causes all kinds of nasty side-effects). And also for the Library folder (might be in the Unity folder - if you have trouble finding it, simply do a full disc search for FailedAssetImport.txt).
If it persists, make sure to file a bug report with your complete project attached and a good description of your environment and how this might have started (like, what were the last actions you performed).
Finally, with a copy of your project, if nothing else helps, you might try to simply remove the offending text-file (Library/FailedAssetImport.txt). Be super-careful when messing with the library folder, it might trash your project if you touch the wrong files (that's why I said "with a copy of your project" ;-) ). Not sure if there really is some "generic library folder" (I'm guessing there should be when this happens to you when creating new projects). If there is, I'd make sure to make a copy before messing with it, too (same as with the project folders).
Hope this helps ...
When I had similar issues, a restart usually did the job.
I am having the same problem with temp files, not the exact same file name.(One of them mentions scripts) I need to get this fixed ASAP! I downloaded Unity 3 because of this problem but same thing happens in 3 aswell... Please if you get help and figure out how to fix it please email me. jason2169@gmail.com
I was able to fix this frustrating problem after a little trial and error. I started by both uninstalling and re-installing Unity as administrator - no luck. I then found the “TEMP” directory and tried to cut & paste the culprit files. Sure enough, I got an error with more detail explaining that I was unable to move the files because MaxCommandPipe was open in 3ds Max (which I haven’t used since starting my computer).
So I went into task manager (processes), killed 3ds Max and clicked “Try again”. I then continued to kill 3ds Max via the task manager until the importing assets task was completed. This is most likely because Unity is trying to use 3ds to convert the file types…
Another option would be to remove the entire custom project out of your Unity Projects folder.
There’s another fix to this problem, because sometimes you might ‘overtweak’ some windows settings. In my case, Win7 was giving an error whenever I created / renamed a new directory.
And I figured that’s was the only reason why Unity was throwing error’ Moving file failed’ during build phase. Check this guide techjawa.com . It’s really easy – download the rar file file and apply registry fix per your Windows bit version.
I had the same problem since I installed unity 4, running on Windows 732,it’s happened 5 times in one day!1st 2 times was when I saved a scene, the 1st time I saved it said that and then after it saved okay,and the other issue was trying to get an asset from the asset store, completely refuses to move it and importance to the project, I pressed try again many times, and when I pressed cancel it said-importing everything so it seems that it may have copied the file okay despite the message
“Moving Temp/StagingArea/Package.apk to /Users/sjunnesson/Documents/Tellart Projects/Maritime museum /Code/NMM_GreatMap failed because the file or directory does not exist”
It also deletes all my files and I have to restore to a backup which is a nastier problem… Not sure on what to do to fix it so just sharing the problem.
Hi guys…this problem is solved to me…i follow these steps…
1.restart unity.
2.choose another empty folder to save your new project.for examble "E:\New folder "
then it will start normally…
I was having this same problem after installing 4.3 on a window 7 64 bit machine, and starting a new project from scratch. The first comment seemed so far to fix things for me. The general users permission did not include “modify”, only read, so I added modify and the error disapeared, so far…
I had a similar issue, and it turns out that it was caused by the file path exceeding windows limit. Try moving your project to C:\Temp and try again and see if it resolves it.
I had the same problem but it by uninstalling the Anti-Virus type software which is installed in my PC. because software put some limitation on write permission. You can try this to solve this problem.
Still having this problem with just one of 8 servers I’m building and nothing but nothing is fixing it - not going to turn off my malware and risk my box because of this so short of that …
Is there a way to change Staging so it’s not Read Only - that might help but I have no idea why it blows up just on this one file. Rebooted system, turned off indexing, etc.
Damn … After hours of tests, that was for me my Antivirus (Avira), that was scanning generated executable file, causing the impossibility to move files … !!