I'm using Articulate 360 and find that very often the project cannot save; and I get a fatal error that means the file can never be saved again. Im saving multiple vesrsions of files so I dont lose my progress, but its taking 10x longer than it should to do this. One of the errors I keep getting is This project file could not be saved. (see attachment)
Is this happening with only one project file, or with other files as well? If you see this behavior on multiple files, we might recommend to conduct a simple repair of Storyline 360.
Would you be able to send me one of your .story files for testing? You can add it as a comment clicking on Add Attachment below, or you can share it privately here.
SInce I've starting using SL360/SL3, I get this error every time. The only workaround I've been able to find, even after doing all of the steps in the "working locally" link above, is to save my projects directly to my desktop, then copy/paste the closed project to wherever it needs to live.
What this means is that my project should live at: C:\Egnyte\Shared\Training. However, since this isn't my desktop, I get that "project cannot be saved...." error message.
What I do is save projects to: C:\Users\transom\Desktop\TrainingStoryline. Then at the end of each day, I copy/paste that folder into the Training folder on Egnyte. Make sense?
And by the way, I get the error message even if I try to save the project to C:\Users\transom\Documents\My Articulate Projects
Hi, I get this message every day, 15-20 times, and I am at the end of my tether. I follow all of the correct protocols, and have assigned 8gb of RAM to Parallels. It is almost unusable, and because you are forced to click "don't save" the recovery files seem to be deleted.
Hi there, Amanda! I'm really sorry you're getting worn down. I located your case and am sharing this latest information with Cleo. We'll try to identify what's going on, and you should hear back with some next steps as soon as possible. Thanks for continuing to reach out – I'll follow along in your case as well.
With all due respect I have already contacted your technical department with this specific error message and was sent back a copy and paste of the usual protocols (not running off a drive etc). I have to ask what is the purpose of the error codes if your own developers are not able to translate them? It is a very specific error with enormous consequences for anyone using this software. I update and reinstall almost constantly, saving updated projects every hour or so, regularly copying and pasting slides into new, fresh projects (and having to change all the project settings every time) in case the original is somehow corrupted. I spend at least 40% of my time working around these bugs. It cannot be borne for much longer.
Thanks for reaching out, Amanda. I echo Cleo in that we're more than happy to review your log files and let you know what we find – I do recommend to reply back in the case with that information so we can continue to sort this out for you.
7 Replies
Hi there, Rory!
I'm really sorry that you're running into that error, and I'm happy to help you get past this. A few questions to start:
I'll be standing by!
Hi Katie
I was working from Dropbox so i think that could be the issue. Thanks for the reminder!
Regards
Rory Flynn | Digital Specialist
Hi Rory,
SInce I've starting using SL360/SL3, I get this error every time. The only workaround I've been able to find, even after doing all of the steps in the "working locally" link above, is to save my projects directly to my desktop, then copy/paste the closed project to wherever it needs to live.
What this means is that my project should live at: C:\Egnyte\Shared\Training. However, since this isn't my desktop, I get that "project cannot be saved...." error message.
What I do is save projects to: C:\Users\transom\Desktop\TrainingStoryline. Then at the end of each day, I copy/paste that folder into the Training folder on Egnyte. Make sense?
And by the way, I get the error message even if I try to save the project to C:\Users\transom\Documents\My Articulate Projects
Hi, I get this message every day, 15-20 times, and I am at the end of my tether. I follow all of the correct protocols, and have assigned 8gb of RAM to Parallels. It is almost unusable, and because you are forced to click "don't save" the recovery files seem to be deleted.
Hi there, Amanda! I'm really sorry you're getting worn down. I located your case and am sharing this latest information with Cleo. We'll try to identify what's going on, and you should hear back with some next steps as soon as possible. Thanks for continuing to reach out – I'll follow along in your case as well.
With all due respect I have already contacted your technical department with this specific error message and was sent back a copy and paste of the usual protocols (not running off a drive etc). I have to ask what is the purpose of the error codes if your own developers are not able to translate them? It is a very specific error with enormous consequences for anyone using this software. I update and reinstall almost constantly, saving updated projects every hour or so, regularly copying and pasting slides into new, fresh projects (and having to change all the project settings every time) in case the original is somehow corrupted. I spend at least 40% of my time working around these bugs. It cannot be borne for much longer.
Thanks for reaching out, Amanda. I echo Cleo in that we're more than happy to review your log files and let you know what we find – I do recommend to reply back in the case with that information so we can continue to sort this out for you.
This discussion is closed. You can start a new discussion or contact Articulate Support.