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

FYI, I had the same issue.  It seems to have solved itself after I first closed MS Word (and Storyline 360), then opened the Storyline file and started the TX export.

And I also made sure it was exporting to a completely local file. (However, I had been successfully exporting to Dropbox with 2 other files previously.)

Hi all!

I'm so excited to share that we've released Storyline 360 (Build 3.49.24347.0) which includes Enhanced Word Translation!

This feature fixes the issue where the error, 'Exception has been thrown by the target of an invocation' appeared when exporting a text-heavy Storyline 360 file to Word. 

To take advantage of this new feature and other fixes, make sure to update Storyline 360 in the Articulate 360 Desktop App. Here are the steps!

We have done testing on a number of different files and so far it appears the issue may actually lie with the number of slides being translated. Our testing found that if the number of slides exceeds ~70, the exception error is more likely to be thrown. This has not yet been 100% confirmed, but it is our current working theory. It's possible there is a combination between the number of slides and the amount of text in the course. We have also tested the above process and can confirm it works.

This is our current/new translation process:

1. Attempt to export from the file as is. If an error occurs, note the number of slides and proceed to step 2.
2. Using Save As, create duplicate .story files for each section in the course.
3. Export a translation document from each new .story file. [if you get another error, note the number of slides and use Save As to split that section up further]
4. Once you have all of the translation documents, the duplicate .story files are no longer necessary and can be deleted.
5. Send documents for translation.
6. Import all translated documents into the original .story file.

Hopefully this helps everyone out there experiencing this issue, and maybe those tasked with solving the problem.

Not sure if people are still having this problem, but I am. I found that if I export to XLIFF first, then try again to Word, it seems to work. Not sure why, but so far so good. Hope this can help others. (FYI, I kept my microsoft programs open, even word)

You nailed it, Nathan. That's the current workaround and this conversation is linked to our report as we continue investigating and we will share any updates we have with you here. 

You all need to work a little harder at this function.  What a nightmare.  I have a course with 13 lessons and an assessment scene, totaling 219 slides.  I have a powerhouse of a PC - latest AMD Ryzen CPU, 64GB RAM, MVME drives (plural), 8GB GPU, it's a beast.  And even it couldn't get Storyline to export unless I made multiple copies of my .story file and created 2-3 lesson chunks of the content to get it to export.  I tried exporting to different drives, restarting Windows with only Storyline 360 running, followed all the advice above, and still it would bomb with that message about "exception has been thrown by the target of an invocation".

Admittedly, I'm using this "feature" because it's the only way of getting actual text to export out of Storyline.  It would be so awesome if the publish to Word function did more than just export a screenshot and whatever notes might be there (I don't use notes).

I like to report that I was having the same issue. I closed all the Microsoft Office applications with the exception of Outlook and I was still having the issue. As soon as I closed Outlook, the problem disappeared. Suggestion for Articulate. Place a reminder on the pop-up for the export in Storyline, to alert users to close all Microsoft Office applications before initiating the export.

Thank you.

Good morning, everyone!

Thanks for taking the time to raise this issue. We can recreate the error, 'Exception has been thrown by the target of an invocation' when exporting a text-heavy Storyline 360 file to Word. 

Current workarounds:

1. Split the project into multiple parts by doing a Save As on the original .story file to reduce the number of slides
2. Export and translate the translation documents and then import them into the original .story file
3. Or, closing all Office applications can help

So sorry for the trouble, and I'll keep this discussion updated on any more changes!

Any more advice on this? I gather the problem hasn't been solved?