Forum Discussion
Word Blocking Articulate Macro
I can no longer publish to Word from Articulate Storyline. I am getting a "potential security concern." Word has blocked macros from running because the "source of this file is untrusted." I have the articulate storyline file saved to my desktop. Is there a fix I can do in Articulate?
Hi Susan,
Thanks for reaching out and I'm sorry to hear that you're experiencing this issue! I'm happy to help troubleshoot and have a few clarifying questions to start.
- Are you saving your file to your local drive? Working from a network drive can cause erratic behavior.
- What version of Storyline 360 are you using? You can check by selecting Help, then About Storyline.
- Are you able to publish to Word in a newly created file? Does it make a difference if you change the target folder to your desktop?
If you're comfortable sharing your file with us, I'd be happy to do further testing on my end. You can upload it here or share it privately in a support case.
I have tried it from C drive, Internal server and desktop - none of them allow me to publish to Word. I used to be able to publish to Word my capabilities stopped about 1 month ago.
It's not just 1 file it's all of them.
I'm using the newest Version v377.30587.0
Hi Susan!
Thanks for the feedback! I'm sorry to hear that you've hit this snag with Storyline 360 courses refusing to publish to Word.
I've opened a support case on your behalf so our support engineers can take a closer look into this issue. They should be getting in touch with you shortly!
I have the same issue and have had it multiple times before. I have to ask my IT team to make the site that the file comes from a 'trusted site.' - but I don't know what that server is to tell them. Can anyone assist?
Hi Trace!
Sorry to hear you've also hit this snag when publishing from Storyline 360 to Word. I'd be happy to assist!
A helpful first step would be to confirm that the network endpoints are enabled. Please have your IT team check if port 443 is open. If not, ask them to open port 443 and add the domains in this article to your organization's 'allowlist'.
If the issue persists, and you're receiving an error message, seeing a screenshot of the message would be useful! You can share that here or privately in a support case.
