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.
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.
Our team would be happy to work through this issue with you one on one as I know that there have been some inconsistent behaviors and causes for it. Can you reach out here and share a copy of your .story file with our Support Engineers?
I have encountered this as well. The only workaround (I've tried all the steps provided in this thread) successful for me is to save it under different names every time I save. Very problematic.
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.
I submitted a ticket and included screenshots of the various errors I'm receiving. It is with 2 of my projects both made using Storyline 2. I uninstalled Articulate & am going to reinstall.
Thanks Erin - I see where you reached out to the support team (01089537) and you should be hearing from someone soon. I'll be sure to follow along as well.
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 support@articulate.com. 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 discovered in SL360 that if you have more than one master slide in your project it can often lead to saving errors or publishing errors. Try using multiple layouts with just one master slide, and delete the extra master slides.
Sorry to hear that you ran into an issue with Storyline 3.
This thread is a bit dated and I know that many of the posts are for Storyline 2, so I'd like to understand what you are seeing and if you are getting an error of some sort?
This issue is almost a decade old, and for SL2, but it just happened to me today. I am using SL360, working locally, and my project indeed has a few videos.
Object reference not set to an instance of an object
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.
187 Replies
I think that's within her files, not within the software. Again, I cannot speak for her.
Are you utilizing the latest update? Are you having difficulty across files or just with a particular file?
Have you tried to import into a new file to see if that alleviates the issue?
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.
Hi Kaitlin,
Our team would be happy to work through this issue with you one on one as I know that there have been some inconsistent behaviors and causes for it. Can you reach out here and share a copy of your .story file with our Support Engineers?
I have encountered this as well. The only workaround (I've tried all the steps provided in this thread) successful for me is to save it under different names every time I save. Very problematic.
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.
Hi Leslie,
I submitted a ticket and included screenshots of the various errors I'm receiving. It is with 2 of my projects both made using Storyline 2. I uninstalled Articulate & am going to reinstall.
Thanks Erin - I see where you reached out to the support team (01089537) and you should be hearing from someone soon. I'll be sure to follow along as well.
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 support@articulate.com. 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.
I'm experiencing the same issue with SL3. Any solutions yet?
I discovered in SL360 that if you have more than one master slide in your project it can often lead to saving errors or publishing errors. Try using multiple layouts with just one master slide, and delete the extra master slides.
Hey Rocky,
Sorry to hear that you ran into an issue with Storyline 3.
This thread is a bit dated and I know that many of the posts are for Storyline 2, so I'd like to understand what you are seeing and if you are getting an error of some sort?
Object reference not set to an instance of an object
Did anyone find a solution?
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.
This post was removed by the author