I have a storyline 3 project and while trying to export translation file to word i get this error "Exception has been thrown by the target of an invocation"
and this error happens only with one specific project only.
knowing that I tried the below steps already:
1- exporting is working with other projects without errors
2- tried to split the project and reduced amount of slides and scenes with no success
3-closed all Ms. office applications while exporting
I have split my project in to 3 separate pieces and outputted 3 separate translation docs. Obviously some of the items repeat - from the master slides.
Do I need to try to combine them now into 1 word document?
How do I do this? - will it cause issues with stuff being imported back into the original file?
Or do I keep the 3 docs separate and load them back into the original file one at a time?
Obviously with removing scenes when separating the project - they all ended up being scene 1, 2, 3 in the original they are numbered differently - will this cause an issue with reimporting the translation - the work around does not explain how to get the translation back into the course.
that is interesting as so far it has been blamed on large files. I found that one day one of my files would output the translation doc, and then the next day it would not - it is about 40 slides
It worked for me eventually. Ensured that none of the MS office files word/ppt etc were open in the background. Not convenient really - but seems like it did the work. Am not sure what is the connection. Seemed to have worked so far - have done 2 more exports no glitches.
I have done larger files in the past - over 45minutes worth of content spread over more than slides - and it has worked without any concerns - so am not sure why the size file is a factor. I hope they are able to patch it though.
Thank you @Afaq for posting your recommendation. I kept getting the same error notification, multiple times, then I tried your recommendation and worked like a charm. Much appreciated!
11 Replies
Hello Mohamed,
So sorry you hit this error! We found that exporting to Word results in that exact error due to numerous slides/text-heavy Storyline content.
For now, we recommend:
If those steps don't help, are you comfortable with sharing the affected file with us for testing? You can use this secure upload link:
I have just encountered this error as well - was there any fix?
I have split my project in to 3 separate pieces and outputted 3 separate translation docs. Obviously some of the items repeat - from the master slides.
Do I need to try to combine them now into 1 word document?
How do I do this? - will it cause issues with stuff being imported back into the original file?
Or do I keep the 3 docs separate and load them back into the original file one at a time?
Obviously with removing scenes when separating the project - they all ended up being scene 1, 2, 3 in the original they are numbered differently - will this cause an issue with reimporting the translation - the work around does not explain how to get the translation back into the course.
Hi Lizzie!
We're happy to help! You'll need to import the three translation documents back into the original .story file.
If you'd like us to take a look at the project, here's a secure upload link! We'll take a look and reply with our findings.
Hi,
Just encountered this error too - its a small file of 4 slides. Not sure why am getting this error.
Will you guide me here please.
Regards,
Swapna
that is interesting as so far it has been blamed on large files. I found that one day one of my files would output the translation doc, and then the next day it would not - it is about 40 slides
It worked for me eventually. Ensured that none of the MS office files word/ppt etc were open in the background. Not convenient really - but seems like it did the work. Am not sure what is the connection. Seemed to have worked so far - have done 2 more exports no glitches.
I have done larger files in the past - over 45minutes worth of content spread over more than slides - and it has worked without any concerns - so am not sure why the size file is a factor. I hope they are able to patch it though.
-Swapna Kadam
Thank you @Afaq for posting your recommendation. I kept getting the same error notification, multiple times, then I tried your recommendation and worked like a charm. Much appreciated!
Glad to be of help.
Cheers
-Swapna Kadam
I encountered the same issue. I'm not able to export the translation to Word.
I see this thread started 3 years ago (!)
Is this workaround of splitting the file into pieces still the best solution?
Hi Dv,
Yes, at this time, the suggested workaround is best. I'd recommend following my colleague Katie's steps, which she shared earlier in this thread.
If you're having difficulty, feel free to reach out within a support case. We're happy to investigate your project further!