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

AshleyT-Pollard
Staff
11 years ago
Sounds good Darryl - and if you have a case number you'd like to share with me, I can follow along and update the forums as well.
BudKeegan1
Community Member
11 years ago
Having a similar issue-- any updates on this? I've already followed KBase advice to no avail...
AshleyT-Pollard
Staff
11 years ago

Hi Bud,

As Justin mentioned above, we've had some users who experienced this and our team is taking a deeper look into the behavior. Did you review the other questions Justin mentioned and look into gathering those three items to share with our support team? You can send them along here so that we can take a better look at what is happening.
Danielle-Watkin
Community Member
11 years ago
I am experiencing this too. Submitted a ticket even and...crickets. I submitted it on Sunday and haven't heard a word. It is truly an unacceptable bug. Not being able to save...kinda an issue. Oh, and I should add, my project isn't a converted project. I created it in SL2.
AshleyT-Pollard
Staff
11 years ago
Hi Danielle,

I'm sorry to hear that you've encountered this too, and I'd like to look in on the ticket you mentioned filing. Did you use the link here to submit a case? You would have received a confirmation email from Support@articulate.com with a case number. If you saw the message in Storyline that something went wrong, and you could send the error report - that goes to our QA team for review and tracking of issues with Storyline but doesn't have the same set up as getting back to you about what happened.

Have you already looked into conducting the repair?
LeslieMcKerchie
Staff
11 years ago
Hi Danielle!

I tried to check on your case, but I'm not seeing one.

Did you get a case number that I could check on?
georginacuttanc
Community Member
11 years ago
Also happening to me a lot!

I'm losing 10 hours a week to lost files, despite the fact that i'm saving regularly.

We have 2 users at my company experiencing this possibly more. If i send the 3 items along will you guarantee someone will look ta my files and reply? thanks.

We have another 6 or so people assessing this SW for an upgrade from articulate.; I've just told them to hold off on purchasing; suggesting SW that doesn't t save isn't going to paint me in a very good light.
LeslieMcKerchie
Staff
11 years ago
Hi Georgina!

Are you working locally? Do you have the latest update of Storyline 2, which is Update 1? Are you receiving an error when trying to save?

I'm not sure what you are referring to when you say 'SW'.
SimonBlackmore
Community Member
11 years ago
I'm having the same problem with a module that contains videos.

This is completely unacceptable. If i save the file to a network drive it seems ok, if i try and save it to my local hard drive (which is what we are told to do) it just hangs. However, i'm very reluctant to spend time updating the module only to find it corrupts the whole thing and i lose weeks of work.

My client is expecting this module completed and delivered to them by the end of next!
LeslieMcKerchie
Staff
11 years ago
Hi Simon! Sorry to hear that you are having difficulty.

Are you utilizing the latest update that was shared above?

You are welcome to work directly with our support team if you'd like.