"Can not access closed stream" Error When Saving File

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?

Hi, I am getting the same error message. Yes, it is keeping the file from saving. I am saving it to my hard drive.

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!

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.

Sounds like a plan, Jennifer. We'll be here if you need us! Fingers crossed it doesn't happen again. 😊

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?

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. 

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! 🌟

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!

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.