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

SimonBlackmore
Community Member
11 years ago
Hi Leslie

Yes, i'm using 1410.204. I submitted a support ticket this morning but have had no response.
LeslieMcKerchie
Staff
11 years ago
Thanks for letting me know Simon. I could not locate the case number, so if you would like me to follow along, you can share it with me here. I'm sure you will be hearing from someone soon though.
SimonBlackmore
Community Member
11 years ago
Thanks Leslie, i never actually received an email confirming the submission, i'll do it again in case something went wrong.
LeslieMcKerchie
Staff
11 years ago
Ah, yes, please do :)
SimonBlackmore
Community Member
11 years ago
Hi Leslie, i've resubmitted the case again and got the following screen, no confirmation email yet though.
MichaelGrady
Community Member
11 years ago
Has there been any progress or updates from the Articulate developers/staff, on this issue? We are also running into this issue and, like many of the comments in this post, we are have client deadlines quickly approaching. THIS IS NOT GOOD!
- SimonBlackmore
  Community Member
  11 years ago
  Hi Michael
  
  Not had a response or any assistance from Articulate so far.
  
  My project is currently behaving itself, however, my faith in Storyline 2 is waning fast.
  
  I'm saving my project every 5 or 10 minutes (or if I do something significant) and I have a couple of back ups just to be on the safe side in case it becomes corrupted.
  
  Best wishes
  
  Simon
AshleyT-Pollard
Staff
11 years ago
Hi Simon,

I see that you shared that screen, but I am not able to find a case associated with your name. Could it be under a different name or different email address? You would have received a confirmation email from Support@articulate.com and you'd want to check your junk/spam folder for it. If for some reason you didn't receive the email, it seems the case submission did not go through - and it may be easier to email the information to the aforementioned email address directly as that will generate a new case.
- SimonBlackmore
  Community Member
  11 years ago
  Hi Ashley
  
  I'll try emailing support directly tomorrow.
  
  Best wishes
  
  Simon
AnthonyProtasiu
Community Member
11 years ago
I'm crashing and burning here.....has this issue been resolved?

I'm getting work done but I'm saving at a snails pace or should I say.....trying to save.
LeslieMcKerchie
Staff
11 years ago
Hi Michael!

Based on your description, and to re-iterate what Justin shared previously, it sounds as if you have confirmed some of the common themes that we are seeing.

That being said:

Could you 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.
- AnthonyProtasiu
  Community Member
  11 years ago
  Hi Leslie,
  
  FYI: Micheal Grady and I are working on this project together. I did send the SL2.story project file and is attached to Case Number: 00437091.
  
  The only problem is that when I ran the "SLLogZip.bat file" from the "How to Upload Articulate Storyline 2 Error Logs to Articulate Support" there was no "ArticulateLogFiles.zip" file on my desktop as it stated in the dialogue box. I've checked my desktop a few times since that process thinking it may take a while....that file is a no show.
LeslieMcKerchie
Staff
11 years ago
Hi Anthony!

Thanks for submitting that to our support team (and for tying you and Michael together).

As we mentioned, we are trying to pinpoint this issue and working with support is our recommendation.

You should be hearing from someone soon.
- AnthonyProtasiu
  Community Member
  11 years ago
  Hi Leslie,
  
  I figure I give you an update.
  
  Michael gave me the go ahead and I uninstalled SL2 from my PC. Re-installed the software and on my 2nd attempt at saving.....the dialogue box popped up again and denied me saving my work.
  
  Any word on a fix?