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

Sep 07, 2017

Hi all,

I wanted to export a file for proofreading purposes from Articulate Storyline 360, but encountered an error when exporting the word file. I had done this before with Articulate 1 for my previous employer, so theoretically I know what I am doing. However, I keep receiving the error.

I have checked for weird letters or a too long path, but cannot find anything out of the ordinary

I have recorded what happened with Peek:

https://360.articulate.com/review/content/83fb8bb7-53dd-4031-a660-f6383be9b3a4/review

43 Replies
Alyssa Gomez

Thanks for including the Peek, Antje! That was really helpful. I have a few suggestions for you to try:

  1. Open a new Storyline file, and Export to Word for translation. Do you see the same error message in the new file? If so...
  2. Go through these steps to repair Storyline 360.

Let me know how it goes! If you're still getting stuck, we'll keep digging. ☺️

Antje T.

Hi Alyssa,
thanks a lot for the support. Unfortunately,even  after uninstalling and rebooting, I am still getting the same error message.

The file is stored locally on my computer and I am exporting locally as well to avoid any server related issues. It does not seem to matter how many slides the course contains, since I tested with a one- and two-slide test course as well as with the relatively short 21 slide course.

At this point it is not vital to have the export function since I can of course also have my colleague proofread the course online. However, in the near future we need to translate the content, then I really need this function to work.

Any other solutions are highly appreciated!

Alyssa Gomez

Sorry you're running into this, M. Are you on the latest update of Storyline 360? To check, click the Help tab, then click About Storyline. You should see 3.11.14249.0 in the bottom-right corner. 

If you're already on the latest update, I'd like to connect you with our Support Engineers here. They'll gather more information about your system and hopefully nail down the culprit! 

Jessica Lucas

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.

Søren Kastholm

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.

Ashley Terwilliger-Pollard

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? 

Søren Kastholm

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

Leslie McKerchie

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?

Tina Marie Lalonde

Good news, I finally got it to work.  What I've done different is I made sure that Office wasn't working in the background. I remembered way back having problems with SL2 because Office was open while I was trying to export my translation to Word.  I also split the file in 2 with only half the slides.  It still is a pretty big file of 65 slides and 32 Mb.  

Ashley Terwilliger-Pollard

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? 
Ashley Terwilliger-Pollard

Hi Dave,

Thanks for checking into all of those areas! Is this happening on all Storyline 360 files or only those that have been upgraded from Storyline 2?  You mentioned that you and a friend are both having trouble, but it would help if we're able to take a look at your original Storyline 2 file and test upgrading and exporting it too. I'll start a Support case for you so that you can share at least one of those files! 

Keep an eye out for an email from Support@articulate.com

Just kidding! Looks like you've already got a Support case, so I'll share the additional details here with Rona.