Sorry for the delay here in seeing this discussion! That error is one our team was investigating and we've fixed in the latest update, Storyline 360, build 3.27.18822.0.
We installed update as soon as it came out and now opening SL3 for the first time since update and files will not save. I get error message "not enough space on the disk" but we save everything to a D drive, not to a C and in all these years this has never happened or been an issue. I am at my wits end. What is the fix?
Thanks for those details, Gillian. We recommend creating, editing and publishing your Storyline files to the local C: drive for the best experience. This article explains why.
Let us know if saving to your C: drive isn't working!
For the past 3 weeks, I have been continuously getting save errors that forces me to rename or overwrite (which creates a numbered copy) in the same folder. Or it tells me another user has it open. Which cannot be the case. Please - is there any advice on solving this issue. Several of my projects now have about 20 copies of the same course each with a different number behind the name. I've spoken with our IT group and they couldn't figure out why it is happening only with the .story files and no other documents/files/videos etc. that I work with regularly.
Sorry for the trouble you've had - we opened up a Support case for you on Friday afternoon, and it looks like Jopney has already been in touch to troubleshoot with you. Look for the email from Support@articulate.com for those next steps!
So sorry to hear these issues are popping up! As mentioned above by Crystal, this article covers the reasons why we strongly recommend working locally from your C: drive.
Try saving the file to your desktop to work on it, then load it back into Dropbox once you've reached a stopping point, or when someone else needs to take over. If you still find yourself running into these messages after working locally, connect with a support engineer, and they can help troubleshoot your file!
7 Replies
Hi Das,
Sorry for the delay here in seeing this discussion! That error is one our team was investigating and we've fixed in the latest update, Storyline 360, build 3.27.18822.0.
Follow the directions here to update it.
We installed update as soon as it came out and now opening SL3 for the first time since update and files will not save. I get error message "not enough space on the disk" but we save everything to a D drive, not to a C and in all these years this has never happened or been an issue. I am at my wits end. What is the fix?
Thanks for those details, Gillian. We recommend creating, editing and publishing your Storyline files to the local C: drive for the best experience. This article explains why.
Let us know if saving to your C: drive isn't working!
For the past 3 weeks, I have been continuously getting save errors that forces me to rename or overwrite (which creates a numbered copy) in the same folder. Or it tells me another user has it open. Which cannot be the case. Please - is there any advice on solving this issue. Several of my projects now have about 20 copies of the same course each with a different number behind the name. I've spoken with our IT group and they couldn't figure out why it is happening only with the .story files and no other documents/files/videos etc. that I work with regularly.
Hi Becky,
Sorry for the trouble you've had - we opened up a Support case for you on Friday afternoon, and it looks like Jopney has already been in touch to troubleshoot with you. Look for the email from Support@articulate.com for those next steps!
My team are having several saving issues:
1) Exactly the same issue as Becky above
2) We also are finding we can't reopen the project again until Dropbox has fully synced which is causing delays
3) We are seeing conflicted saved copies of Storylines when we only have one person in the file at a time
4) We are increasingly seeing messages 'file being used by another user' when we know we don't have more than one person with the file open.
Please advise how we can overcome these issues. Many thanks.
Hi Emma,
So sorry to hear these issues are popping up! As mentioned above by Crystal, this article covers the reasons why we strongly recommend working locally from your C: drive.
Try saving the file to your desktop to work on it, then load it back into Dropbox once you've reached a stopping point, or when someone else needs to take over. If you still find yourself running into these messages after working locally, connect with a support engineer, and they can help troubleshoot your file!
This discussion is closed. You can start a new discussion or contact Articulate Support.