Export to Word
Dec 21, 2023
I'm getting an error when trying to publish my course to Word (happens with normal and x64 version of Articulate 360):
"Storyline 360 can't reach Microsoft Word and failed to publish the project. Make sure you're using a supported version of Microsoft Word."
I did try resetting the Trust Center defaults in Word, but the error is the same. Also, I tried moving the file from a network drive to my desktop to see if that makes a difference, but no improvement.
9 Replies
Hello Daniel,
I see that you have opened a support case and that you are working with my colleague Chester. You are in good hands!
We'll continue the conversation over in your support case.
Have a great day, and happy developing! ✨
Same thing happening here.
Hi Kassidy!
Sorry to hear you're also having trouble publishing from Storyline to Word. I'd be happy to help!
If you've confirmed that you are working locally, and a repair of your Storyline installation doesn't do the trick, would you be comfortable sharing a copy of your .story file for testing?
Feel free to upload it here in the discussion, or privately through a support case. We'll delete it from our system once troubleshooting is complete!
Having the same issues. Will try "repair of your Storyline installation." However, I don't have much hope. I'm running Storyline from within Parallels. Any ideas on that?
Do you have MS Office Windows installed?
https://access.articulate.com/support/article/using-articulate-software-on-a-mac-with-parallels-desktop#local
I do, but it sits upon/within Parallels. I'm actually running iOS on my laptop.
Hi Jennifer,
I'm happy to jump in here!
If you're still experiencing this issue, I'd be happy to test your course on my end. You can upload it here or privately in a support case if you prefer. We'll delete it from our systems once troubleshooting is complete.
Hi all,
I found that making sure Word was closed before trying to publish resolved the error for me.
When I tried publishing with another Word document already open, I received the error message.
Thanks, William, sometimes the simplest answer is the best!