Word 2016 is supported with Storyline 2 per the system requirements here. You'll want to confirm that you're following along with all the guidelines here especially in regards to working and publishing locally and ensuring that your file names and paths adhere to the character limit and not using any special characters as indicated. Have you tried to close Storyline to conduct the repair of Word? It's not an error message I've seen before, but it looks like Storyline is continuing to try and communicate with Word while you're looking at going through the repair.
I'm not sure what you mean by "clocks" but perhaps it is worth looking at conducting the repair of Storyline if this is a new issue for you. Also, I'd invite you connect with our Support team to share a copy of the .story file so that we could also take a look at how it behaves.
The story file is fine. I transfer it to my old computer that runs Windows 7/Office 2010 and it publishes fine. But I can't publish any SL2 file to Word 2016.
Thanks for sharing that information here. I know our team has been investigating some issues with publish to Word, but it seems that we're not able to consistently reproduce it - so I wonder if you could connect with our Support engineers so that we can get more information about your set up and how it's occurring.?
Do you have a case number so that I can follow up on your issue? You would have receive it in an automated email from our team and the email address would be Support@articulate.com. I tried looking by your name alone here - and "Steve Jones" isn't entirely unique :-)
Ok thanks for the update Steve - can you email your files directly to our Support team using the email address Support@articulate.com? That will start a new case as well and I'll keep an eye out for it as well.
I can send a file, but don't think that would serve any purpose. My SL2 files are fine - when send them to my old computer I can publish to Word just fine.
What I can't do is publish SL2 to Word 2016 in WIndows 10.
Sorry - I said file, but I generally just meant reaching out to them that way as opposed to our case form as it sounds like that's not working for you. I'd still like them to take a look at your overall set up, and having a file helps confirm it's not that specific file in that set up as well.
I can't find a support case for Steve for this particular issue - but you'll want to confirm that you don't have any other instances of Word open, and that you're choosing to publish to your local drive and adhering to the guidelines here.
Yes a support engineer contacted me resolved this. Don't remember exactly what we did, but he was very helpful, as usual. I suggest submitting a support case.
Thanks Alexander, and I see your case that you're working on with Wilbert. I was eventually able to find Steve's case as well and it seems that he had to conduct a repair of Storyline and Office 2016. Here are the directions to repair Storyline.
I'm sorry to hear you've run into the same issue! As you can tell from this discussion and the details of the few cases shared here, it hasn't been one solution fits all - but we'd be happy to take a look at your situation and offer more specifics. Our Support Engineers are accessible here 24/7 and we're getting ready to go into the holiday weekend - but if you can share you're information there they'll get testing it as soon as they can!
I too am still having problems publishing to Word 2016 in Office 365; however, my situation seems to be somewhat different than what is posted here. When I click on Publish to Word, Articulate starts the process of installing Word 2010 even though 2016 is my default .doc app. Word 2010 then takes over and becomes the default app and I am having to go back into settings to reset to Word 2016. Any ideas on correcting this?
Also, the Office 365 you are using, do you know if it's either of these:
Web-based versions of Office 365
Mobile versions of Office 365
Both of those aren't supported with Articulate tools, so that could be why it tries to install Word 2010. Do you have a version of Office 2010 already installed, or is it reaching out to the Microsoft site to download it?
26 Replies
Hi Steve,
Word 2016 is supported with Storyline 2 per the system requirements here. You'll want to confirm that you're following along with all the guidelines here especially in regards to working and publishing locally and ensuring that your file names and paths adhere to the character limit and not using any special characters as indicated. Have you tried to close Storyline to conduct the repair of Word? It's not an error message I've seen before, but it looks like Storyline is continuing to try and communicate with Word while you're looking at going through the repair.
When the first message comes up, Storyline is frozen so can't close it.
Restarted system; now Storyline just clocks when I try to publish to Word. Have to Ctrl-alt-del to close Storyline.
It's a brand new computer that meets requirements. Publishing locally, short file name.
Hi Steve,
I'm not sure what you mean by "clocks" but perhaps it is worth looking at conducting the repair of Storyline if this is a new issue for you. Also, I'd invite you connect with our Support team to share a copy of the .story file so that we could also take a look at how it behaves.
By "clock" I mean the spinning circle.
The story file is fine. I transfer it to my old computer that runs Windows 7/Office 2010 and it publishes fine. But I can't publish any SL2 file to Word 2016.
Hi Steve,
Thanks for sharing that information here. I know our team has been investigating some issues with publish to Word, but it seems that we're not able to consistently reproduce it - so I wonder if you could connect with our Support engineers so that we can get more information about your set up and how it's occurring.?
Any update on this? I sent the files to your support engineers, but haven't heard back.
I have to transfer the SL2 file to my old computer in order to publish to Word - it's a feature I use regularly so this is pretty annoying.
Thanks, Steve.
Hi Steve,
Do you have a case number so that I can follow up on your issue? You would have receive it in an automated email from our team and the email address would be Support@articulate.com. I tried looking by your name alone here - and "Steve Jones" isn't entirely unique :-)
Yeah, never got an email. I resubmitted my case.
Thanks Steve - did you receive an email right away? If so let me know the case number and I'll follow along.
Nope, didn't get an email.
Ok thanks for the update Steve - can you email your files directly to our Support team using the email address Support@articulate.com? That will start a new case as well and I'll keep an eye out for it as well.
I can send a file, but don't think that would serve any purpose. My SL2 files are fine - when send them to my old computer I can publish to Word just fine.
What I can't do is publish SL2 to Word 2016 in WIndows 10.
Hi Steve,
Sorry - I said file, but I generally just meant reaching out to them that way as opposed to our case form as it sounds like that's not working for you. I'd still like them to take a look at your overall set up, and having a file helps confirm it's not that specific file in that set up as well.
Was this ever resolved for you - running into similar issues.
Hi Alexander,
I can't find a support case for Steve for this particular issue - but you'll want to confirm that you don't have any other instances of Word open, and that you're choosing to publish to your local drive and adhering to the guidelines here.
Yes a support engineer contacted me resolved this. Don't remember exactly what we did, but he was very helpful, as usual. I suggest submitting a support case.
Working through that now.
Sent from my iPhone
Thanks Alexander, and I see your case that you're working on with Wilbert. I was eventually able to find Steve's case as well and it seems that he had to conduct a repair of Storyline and Office 2016. Here are the directions to repair Storyline.
Already done all of that and reinstalled office as well. No response from W yet.
Sent from my iPhone
Hi Alexander,
It looks like you and Wilbert have sent a few messages back and forth - so I'll continue to follow along to include any updates here.
This WORD issue is a pervasive one. I have been unsuccessful trying all ther referenced repairs. :-(
Hi Heather,
I'm sorry to hear you've run into the same issue! As you can tell from this discussion and the details of the few cases shared here, it hasn't been one solution fits all - but we'd be happy to take a look at your situation and offer more specifics. Our Support Engineers are accessible here 24/7 and we're getting ready to go into the holiday weekend - but if you can share you're information there they'll get testing it as soon as they can!
I too am still having problems publishing to Word 2016 in Office 365; however, my situation seems to be somewhat different than what is posted here. When I click on Publish to Word, Articulate starts the process of installing Word 2010 even though 2016 is my default .doc app. Word 2010 then takes over and becomes the default app and I am having to go back into settings to reset to Word 2016. Any ideas on correcting this?
Thanks
Hi Barry,
What version of Storyline are you using?
Also, the Office 365 you are using, do you know if it's either of these:
Both of those aren't supported with Articulate tools, so that could be why it tries to install Word 2010. Do you have a version of Office 2010 already installed, or is it reaching out to the Microsoft site to download it?
I am using Storyline 2. Yes there is a version of Word 2010 installed on the computer.
Thanks
This discussion is closed. You can start a new discussion or contact Articulate Support.