The file "..." is read only, being used by another process error

I am receiving this error when publishing to a word document. I have been able to publish to articulate review without issue. , my articulate storyline 360 updated on 9/6. I have uninstalled the program and reinstalled. I have restarted and shut my system completely down and I am working on a local drive. None of the tips that I have read in older discussions seem to be working. Any assistance is greatly appreciated. 

18 Replies
Crystal Horn

Hi there, Russell and Tabatha.  We identified an issue with our latest release of Storyline 360 where publishing to Word is failing with that error message.

This is a high priority issue for us, and our team is working on a fix.  I'll make sure this discussion gets updated with any new information as soon as we can!

Ashley Terwilliger

Quick update: 

The publish-to-Word feature in Storyline 360 and Studio 360 that temporarily stopped working has been fixed. Just install the latest software update. Here's how.

If Articulate 360 doesn't notify you right away about the new update, open your Articulate 360 desktop app, click the drop-down arrow next to your profile picture in the upper right corner, then choose "Check for Updates."

Thanks again for reporting it! 

Stephen Moreland

After several months of successful publishing to Word in Storyline 3, I had this same issue occur today. I test published 2 other courses to Word and they worked fine. What happened in my case on this particular course is I simply had too many characters in the title field of the player. Since Storyline creates a new folder for you, based on what you have in the title field, my exceptionally long title itself plus the new Storyline folder exceeded the Windows character maximum. I shortened the title and re-published successfully.

Might be worth a shot for you.

Crystal Horn

Hi there, Anne. Saving locally is a good first step, so thanks for confirming! Is it possible that you have automatic back-up software running at all?

If this is happening on just one file, I would recommend doing a Save As and using a slightly different file name, e.g. ProjectName_v2. Let me know if that helps!