Export translation file to Word gives error 'Exception has been thrown by the target of an invocation'

Oh no, Linda. Glad you were able to get that taken care of, but be sure to reach out if you continue to run into difficulty so that we can take a look.

Hi, I'm having the same issue and error message. My story file is saved to desktop to avoid any server issues too and my Articulate 360 is up-to-date. In case it was an issue of memory or something interfering nothing else is running on the computer whilst exporting.  Any advice or solution found since Linda posted 4 months ago?
Files for translation need to be sent to client ASAP.

Hi Jessica!

Sorry you're hung up. What version of Microsoft Office is installed on your computer? Do you run into this error when trying to export any Storyline file for translation, or just this file in particular?

My colleague also gets the Exception error. She can export small files to Word, but receive the exception error when exporting a large file. We have only tried with the two.

However. I can export the large file without problems. We are using same Word version: Office 365, version 1803 (build 9126.2282).

Hope this can help locating the problem.

Hi Søren, 

It's definitely odd if one of you can export it and the other can't. Are you both on the same update of Storyline? You can check by going to the "Help" Tab -> "About Articulate Storyline".

If you're both accessing the .story file, where is it stored? Do you download and attempt to export locally versus sharing it on a web server/network drive? 

No, we copy the file from the Network to our local computer and export the translation to our local drive. We never work on network drives.

We have the same version of Storyline 360.

My computer (i7-7700HQ) is faster than my colleagues (i5-4210M). So, could it be a time-out issue?

Earlier I have reported an error in exporting content of a variable (Case #01213077), which still is unsolved. We implement subtitles using a variable shown on the slide master.

We cannot trust all instances of the subtitle variable are exported. The more instances on a slide, the more likely it is that some are skipped.

I don't know if these problems are related. But I thínk it is worth to mention.

BR

Søren

I appreciate you sharing the additional information Søren. From the looks of the conversation and support cases referenced above, we did not reach a solid conclusion for me to share.

Would your colleague be able to work directly with our support team here so that we could better understand what may be going on?

Hi,

Were you able to solve this issue ?  I've just ran into it.  I've got 360 v3.21.17083.0 all running locally and Microsoft Office 365 Business version 1803 (build 9126.2295).

Thank you.

Glad to hear you're up and running, Tina Marie! You're right on target with closing down Word while you conduct the export/import so that everything can run seamlessly. 

If you need any other help, let us know! 

Hi Dave, 

We haven't narrowed down one particular cause for Storyline not allowing the export to Word, but a few things to check on:

• Is Word open while you're trying to export?
• Are Word and Storyline installed in the same environment with the same permissions? i.e., both installed on Windows 10 in Parallels for Mac using admin permissions
• Are you on the latest update of your version of Storyline, and using a supported Word version? 
• Are you saving the .story file and the .doc file to a local destination, following along with the other guidelines here?