• State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 435 subscribers
  • Views 8153 views
  • Users 0 members are here
Options
Related

Can't open word document

Kelsie Pettit

Dear all,

I want to open a single document for translation and I get the following error message:

'the file is locked or open in another application.' 

As far as I can tell the file is neither locked nor open.  Can anyone help?

Thanks
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    I just ran into a bug with the same error message. I'm just documenting it here for future reference, in case I run into it again.

    I'm using Studio 2015, and the file to translate is an old doc file, so the file type is Word 2000-2003. If I run the default tasks for the file, I'll get the error in the Convert to Translatable Format phase. The error can be worked around by killing the Winword.exe process and restarting the task sequence.

    What's interesting about the bug is that the Winword.exe process that's locking the file is apparently started by Studio itself, in the scanning phase (I tested this by killing all Winword processes and then checking when the process appears).

    So the cause of the bug appears to be that the file type scanning function starts a Word process (presumably to open the doc and check a few things in order to see what file type to use) and does not close it properly. I had the bug with two separate doc files, not sure how common it is (the installed Office version might affect things as well, I'm using 2007).
Reply
  • 0
    I just ran into a bug with the same error message. I'm just documenting it here for future reference, in case I run into it again.

    I'm using Studio 2015, and the file to translate is an old doc file, so the file type is Word 2000-2003. If I run the default tasks for the file, I'll get the error in the Convert to Translatable Format phase. The error can be worked around by killing the Winword.exe process and restarting the task sequence.

    What's interesting about the bug is that the Winword.exe process that's locking the file is apparently started by Studio itself, in the scanning phase (I tested this by killing all Winword processes and then checking when the process appears).

    So the cause of the bug appears to be that the file type scanning function starts a Word process (presumably to open the doc and check a few things in order to see what file type to use) and does not close it properly. I had the bug with two separate doc files, not sure how common it is (the installed Office version might affect things as well, I'm using 2007).
Children
No Data