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.

187 Replies
Ashley Terwilliger

Hi Jean-Guy,

Thanks for updating us. If it's an overall memory issue, I'd look into seeing if you can allocate more memory or working on Storyline with other programs such as Photoshop closed when you go to save or publish. You can see the minimum system requirements for Storyline here (Storyline 1 here)

Ashley Terwilliger

Hi Jean-Guy,

We have heard this from a subset of users as you'll see within this thread. If you're running into it consistently as you mentioned, I'd also want to have you follow the other steps outlined in this thread such as ensuring that you're working locally, conducting the repair of Storyline, and if it continues please connect with our Support team so that we can gather more information about your particular set up. 

Ashley Terwilliger

Hi Max,

Thanks for confirming you already did the repair. What browser are you using to try to upload to the support site? I haven't heard of any issues today - so I'd recommend trying from a different browser and ensuring that there aren't any security settings that would prevent you from uploading information. Also, you can proceed with the case without sharing the screenshot right away and once the case is opened our team will be able to connect with you and share a link where you could upload the files directly. 

Max Laboy

Here is the latest.
I realized that I was working on a template converted from SL1, so I decided to start over from scratch and start with a fresh SL2 project.
Everything was going great for about 20 slides, and then it started throwing the cannot save errors again.
I've lost 3 days just trying to get around this issue - not to mention the destroyed project, which took a week to build!
Any other ideas on getting around this? I've only had SL2 for a month!

Ashley Terwilliger

Hi Max,

Do you  have one of the case numbers handy so that I can take a look? If you submitted two, they likely were combined on our end so either number should work. I know our Storyline team has been playing some catch up following the holiday last week, so I just want to check in on the status. 

You mentioned that on or around slide 20 is when the issue started to occur in a new project, were you able to remove whatever element you had added to that slide and see if the you could continue to work normally? I'm wondering if it's a specific item you're including that could be contributing to the error. Also, I know you've done the repair, and I believe you said you did the full repair detailed here but I also wanted to confirm that you're working locally as mentioned here. 

Max Laboy

Case #00443012

I did the full repair. Completely uninstalled and re-installed twice and then again with the latest update.
Saving and working locally.
Not working in a project upgraded from SL1.
I have an Intel chip (some thought it might have a bearing on it) running Win 7 pro 64bit, 8 GB Ram
The last element added before the issue activated again in the virgin SL2 project was simply a new page with only text on it. I re-added that page again this morning and was able to get it saved, so I will continue to limp along saving after each edit and fingers crossed I can get something accomplished today!

Thanks,
Max

Ashley Terwilliger

Hi Adam,

I'm sorry to hear that you've run into the issue as well, and our team is actively looking into this and working on a fix. The best course of action right now is to connect with our Support team here so that we can see your file, the exact error message you're receiving (there are a few different ones in this thread now) and pull some system information to help our QA team as they continue to try to reproduce the issue and track the error. 

Max Laboy

Here is another bit of info - today I made sure to save after every edit. Each time I have gotten the save error, I closed out of the program, let it sit for a few minutes and then reopened and continued. It allows me to save a few times again before throwing the error. Makes it VERY slow going, but at least I am making progress..

Thanks,
Max

Michael Grady

Hello Ashley,

Not to seem presumptuous or to state the obvious, but have all these particular case #'s been identified/grouped together for analysis? I have not heard anything about my case (00438551) since the 20th, nor has my co-worker heard anything about a 'mirror' case # (004437091) since the 14th. This seems to be a significant issue but besides you Ashley (and a few other Articulate staffers on this thread), I'm not seeing or hearing any updates much less progress towards resolution.

Ashley Terwilliger

Hi Michael,

Yes, we've shared all the case numbers and project files with our QA team. As I mentioned earlier, there are a few different error messages and set ups that we're seeing - so it's difficult right now to say that they're all the same - but they are being investigated together. I do see that your case was shared with our QA team, and until we have additional information to share our support engineers would not reach out again on your case unless you emailed them with updates. As for the other case number you shared, I don't see a case associated with that one and it looks to be at least one number too long. Can you check that again or if you can share the co-workers name I can try to track it down that way? 

There are a few of us who moderator the forums (myself included) to reply, assist with troubleshooting and provide updates. Our QA and Engineering teams don't often have time to get into the forums to reply, so there may only be a handful of us that you hear from here. Please know that we're in communication with them regularly and sharing updates as they occur in this thread or from our support engineers who are testing files in the case.