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 :-)
I am working on a project and have the same error. It will not save but was working just fine earlier today. I also cannot preview the project.
Sometimes I also get an error that the process cannot access the file because it is being used by another process. When checking my task manager there is no other process using the file that I can see. Really cannot afford to lose a whole days work here!
Hi Thomas,
I'm sorry you've run into these errors! Both of those tend to indicate file corruption or impending corruption. I'd look at the best practices outlined here and you could try importing that file into a new project or searching your temp files for an earlier version.
Here's how to check:
1. Open this folder in Windows Explorer:
%Appdata%\Articulate\Storyline
2. Scan the contents of this folder for a file that starts with the name of your project. If you find one, copy it to your desktop. If you find more than one, copy the latest version to your desktop.
3. Change the file extension of the copy on your desktop from *.tmp to *.story.
4. Double-click the file to open it in Storyline.
Hi all,
In our continued efforts to help prevent and recover from file corruption, we've added a new recovery feature to Storyline 360, build 3.29.19305.0. If a project becomes corrupt, Storyline lets you know if there's a working version in your temp files and makes it easy for you to recover. Details here.
Let us know how this feature is working for you and if you have any other questions on the latest update! You can reach out in E-Learning Heroes or connect with our Support Team.
Hi Ashley :)
Thats great but are you doing the same for Storyline 3 as this is happening daily to me.
My files keep getting corrupt and can't save anything.
thanks
Connor
So sorry you're running into this, Connor.
While this feature doesn't exist in Storyline 3 right now, I'm going to share your experience with the team and advocate on your behalf. If we add this functionality in a future update, we promise to update this discussion!
And even though it's tough to nail down the cause of corruption, these tips can help reduce the risk!
Hi Con,
I wanted to let you know the feature I mentioned earlier is now available in Storyline 3, build 3. 3.7.20003.0. You can download the latest update from this page, and this article will provide more details on how this enhancement will work.
I hope that helps, and please let us know if you need anything else!
Can't save my file.
Cannot access the closed stream.
Tried to save as, says cannot access some temp file.Uninstalled and reinstalled too... Tried saving in C drive and D drive.. working locally..
Lost 4 hours work yesterday... this is frustrating.Hi Ritca!
I've opened a support case on your behalf so that we can start troubleshooting right away. So sorry for the trouble! You'll hear from our team shortly.
If any solution for this error please share me. I am also finding the solution for this error.
