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

PhilMayor
Super Hero
11 years ago

Try ctrl+alt+del and kill the process and see if auto recovery saves you. Otherwise it is already lost, sorry
DarrylBenson
Community Member
11 years ago
Yay.. what a lovely program we paid 700 bucks for...
DarrylBenson
Community Member
11 years ago

Ended the program. It recovered, but won't let us save.

This is a SERIOUS bug, Articulate. The whole file is a lost cause, and half a day of work isn't able to be saved.
AshleyT-Pollard
Staff
11 years ago

Hi Darryl,

I don't know if you have already - but can you connect with our Support engineers so that they can help you pull more system information and event logs to help narrow down the problem you experienced?
DarrylBenson
Community Member
11 years ago
I'll do that now, thanks.
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.
Justin
Staff
11 years ago

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!
- MichaelGrady
  Community Member
  11 years ago
  Justin, We are experiencing the same issue as you have described. To further describe our situation, our client provided us their SL1 files to work with/clean-up/finish developing; there are video files included. We upgraded to SL2 and also have another developer working on the project. We had originally been working on a server, but have gone back to working on local/hard drive; We have imported the project into a new project and still are running into problems. Suggestions?
- JulieRodgers
  Community Member
  11 years ago
  I am experiencing this as well. Yes, it's with a file that was SL1 then SL2. Yes, it includes video and/or screen recordings. I seem to have some luck with saving it under a different name each time, but mine also freezes up on me when I try to publish.
  
  I'm sure you all are working on it. We are desperate for a resolution!
- AnjaEl-Kabbout
  Community Member
  11 years ago
  Hey Justin,
  
  I just experienced the same error. It's a new SL2 project, DOES contain video, and other instances of SL2 that were open simultaneously saved without issues. So, only 1 out of your 3 commonalities in my case. Thought you might like to know.
  - MaxLaboy
    Community Member
    11 years ago
    It seems video is the one factor that we all have in common when getting this error.
    
    Below are the variety of error messages I got today.
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.