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.

Try ctrl+alt+del and kill the process and see if auto recovery saves you. Otherwise it is already lost, sorry

Darryl, we've had a small group of users report this behavior in Storyline 2. We're trying to get to the bottom of the problem, and there are a few common themes that we've noticed thus far: The problem seems to happen more often with project files that have been upgraded from SL1 to SL2 than with files that have been created from scratch in SL2. Can you confirm this? The problem seems to happen more often with project files that contain videos (even unused Screen Recordings) than with project files that contain no videos. Can you confirm this? When the problem occurs within a given project on a given machine, it seems that the specific machine is forever unable to perform a Save, Save As, or Import against the project in question. However, when moved to another machine, the file may perform normally. Can you confirm this? This Knowledge Base Article doesn't seem to help. Can you confirm this? If the above is confirmed (or even if it's not, for that matter), we'd love it if you could send us 3 things: The SL2 .story project file that is giving you problems. The backed-up SL1 .story project file before it was upgraded to SL2. A set of Storyline 2 Error Logs. We look forward to hearing from you. Thanks!

Hi Simon! I was attempting to follow up on your case, but I am still not seeing one for you. Michael - this is something that our support team, engineers and QA teams are working to understand. It has not been something that there is a 'generic' fix for and you are welcome to work with support on this as well.

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.

Well, I've had some success in the last two weeks. I did a little research on how I could get applications to perform better and found something created by AMD that seems to really improve Storylines' performance and I never had a save issue since I started using it. It's called Ramdisk and it''s free. It's not the ideal way we want to run Storyline, but it seems to work. First I installed and reviewed the instructions from AMD on how to set it up.Bassically it takes your Ram and allocates a portion of it for specific use and calls it a ramdisk. I have 8GBs of ram, the program is limited to 4GB allocation in freeware mode. I didn’t want to allocate that much anyway so I set 2.5 GB’s up for the Ramdisk. Next I uninstalled Storyline 2 and did a forced Location install of the program to the ramdisk using the instructions provided by articulate:http://www.articulate.com/support/storyline-2/how-to-change-the-installation-location-for-articulate-storyline-2 After the install I copied over my project 600MB project to the ramdisk and I still had 1.25Gbs left on the ramdisk. Plenty of room for the project to grow. During my edits I noticed the projects published 3x faster, saved about 2x faster and I never had a lockup or save error. Only draw backs I could see is that my system slowed down for any other tasks which is likely due to the reduced available ram for the system. If you use it, I would suggest that when you’re done using storyline that you copy your project to your normal save location. The ramdisk will save the stoyline app and files in a ramdisk.img that can be unloaded/loaded at anytime, but will start with your windows if you don't unload it before shutting down.

Project won't save - Storyline 2 | Articulate

Jonathan-Olsson
Community Member
11 years ago
+1 for this problem. Suddenly started for me yesterday.

Project include video.
AshleyT-Pollard
Staff
11 years ago
Hi Anthony and Jonathan,

Thanks for sharing that here - and our team is still investigating this issue. I know Anthony that you're working in a support case, and that's the best way to continue with these issues so that our support engineers can continue to look at your system set up in more detail than we can in the forums.

Jonathan, if you'd like to have us take a look at the behavior as well, please connect with our support engineers here after going through the repair steps mentioned earlier in this thread and linked here.
DavidMcGhee
Community Member
11 years ago
I'm hearing a lot of appologies, but no resolution. Why are we doing your beta testing. Storyline 2 Update 1 is a mess. Unable to save files; text boxes disappear; content disappears,... And please don't ask me to submit files or get in touch with your engineers. From what I can see they have enough samples.
EmilyBurnett
Community Member
11 years ago
Hello David!

You should be receiving an email regarding the initial release of Storyline shortly. We do want to let you know that we only support the latest updates of the products, and that there are some bug fixes in this update that we would not want you to miss out on by reverting back to the initial release.

We are still actively investigating this issue, and hopefully with all the samples that we have already received, we can get a resolution soon.
MichaelGrady
Community Member
11 years ago
OK, we need this issue resolved NOW. Our combined amount of time LOST because of this issue is 5 business days! I just submitted my error log. Please provide a detailed update to Articulate's progress on this matter.
EmilyBurnett
Community Member
11 years ago
Hello Michael!

I checked and can see that your support case did just come in. Keep an eye out for a reply from support@articulate.com. I have also noted the case number so I can check in on progress.
MichaelGrady
Community Member
11 years ago
Hello Emily.

SL2 crashed on me (us) again. I have uploaded the .story file and log per Regil Galve. HOWEVER, when you try to run SLLogZip.bat it does not create a file on your desktop; when you run SLCrash it does, which is what I uploaded.

Please follow up on this issue with me. We are losing both valuable time, and trust in SL2. The cool new features don't outweigh this issue.
EmilyBurnett
Community Member
11 years ago
Hello Michael!

I do see that your email was received. I am sure Regil will reply shortly. I will also continue to keep an eye on the support case for you.
AnthonyProtasiu
Community Member
11 years ago
Is it possible to CHARGE you guys for our time lost?

I think some sort of refund should be in order.
Jean-Guy-Boulay
Community Member
11 years ago
I may have a temporary solution for those suffering. I am also experiencing the issue, but I have come up with a way to get around it.

As soon as I get the save error I try to save the project out as a different filename. It comes up with an error still, but if I look in the folder there will be a new file created. Don't get excited, it's just a duplicate of the file your working on before the save. I then open that project in a separate instance of Storyline. I do this because I want to preserve all my vars and triggers on the master. I then delete all the slides in the duplicate project, then copy the slides from the project that can't save out. It takes a bit of time, but the slides do transfer. Then I save out the new project without issue.

Hope This saves some people time and money. GL