Forum Discussion
"Can not access closed stream" Error When Saving File
I've been running into a problem when saving a project. I've been getting the "Project file could not be saved. Your system appears to be low on memory. Please close any other programs and try again."
Well, I closed all other programs, cleared out my trash, %temp% files, my Storyline files and now when I save, I'm getting the attached file error message (Capture.png.)
I've researched this error message in the forum and it really has not been answered it seems. There is nothing wrong with the file name of my project, as it has followed the same naming convention for projects I've used in SL 3 before we upgraded.
If the naming convention of my project is suddenly an issue, then I don't understand why when I did not have an issue with SL 3 projects.
Thank you :-)
Hi Jennifer,
Sorry you're running into that error! The message 'cannot access closed stream' could indicate file corruption. Is your file saved to your local hard drive?
Is this error message preventing you from saving and closing your project file?
- bethstout-7de85Community Member
Hi, I am getting the same error message. Yes, it is keeping the file from saving. I am saving it to my hard drive.
- JenniferHollistCommunity Member
Hi Alyssa,
I'm sorry I'm just now responding, we've gone through several upgrades here and I recently ran the latest 360 update and haven't ran into the problem **yet** but when I do I'll be sure to reply to this conversation.
Hi, Beth. I'm sorry you're running into the same notice, and I'm glad you reached out to us for help! (also glad to hear you're working locally!)
I have a few more questions for you to narrow down the cause:
- What version of Storyline are you using?
- Is this happening on all of your .story projects, or just one in particular?
- Have you tried importing your slides into a new file to see if that helps?
Let me know!
Sounds like a plan, Jennifer. We'll be here if you need us! Fingers crossed it doesn't happen again. 😊
- BrianBellCommunity Member
I am having the same issue... saving locally (am using Storyline in Parallels.)
Hi there Brian,
Sorry you're hitting this, too. Can you tell me more about your set-up?
- What version of Storyline are you using?
- Is this happening on all of your .story projects, or just one in particular?
- Have you tried importing your slides into a new file to see if that helps?
- BrianBellCommunity Member
Good afternoon,
Storyline 3 (latest upgrade). I’m only working on the one project at the moment but it has happened before with other files as well… it’s interesting in that I’m actually rebuilding this course as the original file and its backup, become corrupted. To “solve” the problem, I have to save the file under a different name… I am now forced to do that at least daily.
Regards,
Brian
Wow, that's so strange! I did notice you had a case with us when you ran into the file corruption. We're happy to keep helping you through this! There may be some file within your content that is causing this problem to happen.
Reach out to us here, and we'll get you the help you need.
- VictoriaNapolitCommunity Member
I was experiencing this issue as well, and have found a workaround. I was able to import the slides from my unsaveable project into a new project and save it. This obviously won't help if you haven't already saved your work, but if you have been saving throughout development, it will at least get you everything up until the last time you saved.
And while I really do love Storyline, if there's anything I've learned using it, it's that you should save compulsively!!!
Thanks for the tip, Victoria! 🌟
- ConnorCure-6a5bCommunity Member
HI
I am having the same issue with my project it won't save and I am trying to copy and paste all the slides into another project however some slides don't seem to work?
Not sure what to do around this I am using Storyline 3
Connor
Hi, Connor. Sorry you're hitting this snag!
Is this happening on all of your .story projects or a specific one? Would you mind sharing a troublesome .story file with us so we can try to replicate the error? You can share it publicly here, or send it to us privately by using this upload link.
We'll run a few tests, and will delete it when we nail down what's happening!