Error message: "The process cannot access the file because it is used by another process"

Hello,

I’m having a persistent problem with Trados Studio, I hope someone can help me!

My PC is running Windows 10 and I am currently working with Studio 2017.

Whenever I try to save the target file I get an error message saying that “the process cannot access the file because it is used by another process”. The message is in Italian, and the name and location of the file change each time, but the file is always located in the AppData\Local\Temp\SDLTempFileManager folder. Please find attached two screenshots of the Error Messages for your reference.

 I’ve tried anything I could think of, and anything I read both in the SDL Community and in other forums, but nothing has worked so far: restart, check whether any winword process is running (but it isn’t), remove the project from Studio and open it again after restarting, saving the file in a different and empty folder, disinstall and reinstall both Trados Studio and MSOffice, temporarily disable the anti-virus …. What’s more, the file in the above-mentioned folder doesn’t exist!

 

Following the advice of the Italian Trados support team, I once managed to create a new project and use the TM to retrieve my work. Last time, however, even this trick didn’t work and I had to adjust the file manually. Luckily it was a short file, but these last resorts are too time-consuming and severely impact productivity. 

 Do you have any suggestions??

Thank you for your time and attention.

Kind regards,

 Francesca

Parents Reply
  • Hi Francesca,

    sometimes, I had to face this message (Studio 2015 and 2017) when saving the target translated document in its original format, and I solved the problem in a very simple way, and it worked.

    In my case, when I try to save from SDL Studio a target translated file with the same name and path of the original source file (e.g. E:\TRANSITO\TEST\Test-file_UK.docx), and if the original source file is open in its application (say, MS Word), I get the same error message (but not always).

    In this case, I just close the open original source file, and the generation of final target translated file works without any problem.

    Another solution would be assigning a different name to the final target translated file (e.g. Test-file_IT.docx), and this works too.

    This was my personal experience and I never had any problem, even when my antivirus (McAfee Antivirus Plus) is active.

    Claudio

Children