Error when importing translation from MS Word

Oct 26, 2022

Hello, I am attempting to import a translation from an MS Word file. the error message I am getting is: 

<?xml version="1.0" encoding="utf-16"?>
<ErrorReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<UserId>auth0|587d3ffc3bcfa12770625e17</UserId>
<HardwareId>2HDA8-RLEU3-FUKUA-UU9VT-PPRMK</HardwareId>
<Message>The requested member of the collection does not exist.</Message>
</ErrorReport>

I am using Storyline 360 (all updates installed). 

I compared the output file to the original untranslated output file and they seem the same (except for the translated content).  I have attached the translated output file. 

any ideas? 

5 Replies
Luciana Piazza

Hi Richard, 

Thanks so much for reaching out! I'm sorry to hear you're having issues with importing MS Word information for your translation project. 

I see you have opened a support case and you are working with my colleague Georvy. Great call, you are in good hands!

We'll continue the conversation over in the support case. 

Have a great day and happy developing!✨

Kelly Auner

Hi, Content Tree!

Thanks so much for reaching out and I'm sorry you're experiencing a similar issue.

I looked at Richard's case, and it appears the issue was related to a corrupted .doc file. This was resolved by re-exporting the course for Word translation, copying the translated text from the “Translation” column, and pasting it on the newly exported Word document. Then, the translation was successfully imported into Storyline.

Please let me know if these steps work for you! If you need additional assistance, it would be helpful to see your file. You can upload it here or share it privately in a support case, and we'll delete it from our systems once troubleshooting is complete!

Jose Tansengco

Hello Content Tree,

We have this documentation on common causes of file corruption, as well as how to prevent them. 

The article focuses more on Storyline 360 project files, but the same steps should also apply to other types. Alternatively, you can reach out to our support team by opening a case and sharing your project files there so we can take a look at them and fix them if possible.