Project won't save - Storyline 2

Getting a different error nearly every time.

Cannot access part because parent package was closed.

Cannot access a closed stream

Store must be open for this operation.

What gives? I can't re-save it as a new file. I'm screwed. About to lose half a day of work here. Any help? We've had this for less than a week, and never had (major) issues with Storyline 1, like this. Saving on C drive. Windows 7. 

Please get back to me asap.

190 Replies
Leslie McKerchie

Hi Pierre!

Sorry to hear that you've run into this issue as well. I cannot speak for Denise, but I have seen other users mention saving the file under a different name as the solution as well. How you name them is probably personal preference. I'm not sure what you mean by 'SL did not recreate the original file'.

Pierre Jouan

Hi Leslie,

"Save as" did not work either.

I though Denise's trick was to rename the file currently opened in Storyline (you should not be able to do this normally because it's "in use").

Say you work on myProject.story and SL refuses to save it. You rename it as myProject_old.story and SL then saves your project by recreating myProject.story.

Kaitlin Nock

Has this issue still not be resolved..? The origin of this thread was two years ago and I am still getting this error message when I tried saving my file. 

I've tried the "solutions" from above and none of them worked. 

Appreciate the help from users, but this seems to be a programming issue on Articulate's end that still needs resolution. 

My advice? Save multiple versions as you go.. was able to use an older version and re-save but wasted a lot of valuable time. Frustrating. 

Leslie McKerchie

Hi Erin!

Sorry to hear that you are continuing to have a problem with this.

Is it across projects or just a single project causing the issue?

I would recommend checking out this article for additional tips on preventing file corruption. If you are having the problem across files/projects, I'd recommend a repair as well.

Leslie McKerchie

Hi Erin!

I popped in to check on your case this morning and it looks like Abel has reached out to you. Hopefully you received that e-mail, it would be from Just respond there when you can or let me know if you do not see it and we can re-send (it may be in junk/spam).

I'll continue to follow along.

Cynthia Manika
If you are on a MAC - then ignore me - PC... continue... recently, I have had multiple wacky issues coinciding with the latest windows update, so much so that I had to use another laptop just to insert or change an image. Did you try the "work's about 95% of the time" method of starting a new project, adding custom settings, and importing ONE scene at at time - saving between each import and before you link your scenes back together, save again as a new name. OH, and don't forget to sing a happy tune during this process - keeps the gremlins away. AND, do not have ANYTHNG else open - seriously - look at your services - this should be the only thing running, not an update in the background or security scan - nada - and that is after a refresh restart. I always have weeks of pain after every major windows update - which is why I keep extra computers around and do not update the spares until the non-Microsoft companies can catch. Adobe products have the problems as Articulate during this period.

Best of luck -  I also remember I did have to republish my longer videos from the highest quality to the next lower as well as my audience would be on laptops or tablets instead of the giant 4K monitor I develop on and it looked just fine on those devices. 

I'll be interested to see what solutions others have found.