Forum Discussion
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
- AshFarazmandCommunity Member
Thanks, my main problem is that I have only one file. Even when I reopen the file it says you can't save:
"The project file could not be saved
Object reference not set to an instance of object"
How can I start working on the file? The whole work is gone?!
- MaxLaboyCommunity Member
Your project is a single slide?
If so, maybe try going straight to a save as instead of just save? Most are finding that even if the error appears during save as, that the new file is saved anyway.
I do not envy tracking this bug down since it seems to have no consistency other than the projects contain video files - is that also the case for you Ash?- AshFarazmandCommunity Member
Max,
Save as does not work neither.It is not a one slide file but it contains a
video.
- JannickeWilhelmCommunity Member
I have also noticed that it is saving very slowly. My support case number is # 00443771.
Thanks Jannicke for sharing your case number here.
- RachelAndersonCommunity Member
Oh no I've looked through all these pages hoping that by the 10th page someone would announce a solution. I have sent in my support case. The number is #00445523. My project has videos as well. It did start my project in Storyline 2. In fact I made sure that I had the latest update installed before I started working with putting the videos in today. My computer has 12GB of RAM memory, and I didn't have anything heavy running in the background while I was working. Copying and pasting my slides into another Storyline 2 project window didn't work for me unfortunately as someone suggested earlier.
I'm really hoping you all can fix this issue. I dread the thought of having to start over especially since there's a chance that I'll just run into the same issue again considering that my project must have videos in it.
Hope to hear some good news from you all soon! Storyline has always been a very reliable program that my team and I would praise over Adobe Captivate. Since this is the first real serious issue I've ran into I haven't changed my opinion but I do hope to hear about a fix soon.
- MaxLaboyCommunity Member
The one thing I have found that seems to keep the error away for a while is to delete ALL app data/temp files from both the temp articulate and root temp. It triples the amount of good saves I get before the error strikes.
I also save after every edit - doing all this is a HUGE time suck as each save takes almost 5 minutes to perform and the program is outputting a ridiculous amount of temp files. In less than a week my entire HD was filled with temp files from articulate!Good luck!
- Jean-Guy-BoulayCommunity Member
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-2After 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.
Thanks Max and Jean-Guy! I shared that information with our QA team as they continue to investigate this issue. Please know that our team is continuing to look into what may be causing this issue and we'll post updates here once we have information to share.
- DanVeltriCommunity Member
Sadly I need to report I'm experiencing this issue as well. I just submitted it, case number 00448583. Using the latest update to SL2, saving to C drive, Windows 7, same problem on two different PCs. Using lots of mp4 video in these projects. My goal is to open existing SL1 projects in SL2 and swap out the video with higher quality mp4 files (saved with "high profile") and use the "none" compression setting.
My experience: Importing from SL1, project will not save in SL2. I get the same error messages that others are reporting. I have uninstalled and reinstalled, all to no avail. I then tried just importing one scene at a time from the SL1 file. That worked one time but when I try to replace the videos with higher quality versions, SL2 won't even let me insert the video. The name of the video is on the timeline but the screen is blank.
I'll be checking this thread often so please do keep us posted on your progress in resolving this issue. I know it's the holidays but I hope someone is there working this week...I'm already behind in my work. Thank you!
Hi Dan,
Thanks for sharing your case number here. Our team is catching up after being off for the Christmas holiday last week, but I expect you'll hear from someone shortly.
- Brooke-LCommunity Member
This happened to me this morning with the trial version of Storyline 2 that I just downloaded. My manager tasked me with looking into Storyline 2 to see if the new features were worth the upgrade cost to purchase for all of our developers.
I opened from SL1 file and I have a bunch of video in the project. I was playing around with the new features (which are very cool) and when I went to save I received the errors, "Cannot access a closed Stream" and "Store must be open for this operation." I tried the "task manager" shutdown solution that I saw in this thread but when I opened up the file it DID NOT ask if I wanted to recover and none of my changes were saved.
I'm so glad I found this thread before purchasing!!! I will keep an eye on this thread and when this issue is fixed I will reevaluate. We use video in every one of our courses so this will definitely need to be fixed before we buy.
- EmilyBurnettCommunity Member
Hello Brooke,
Thanks for sharing. You can submit as much information as you have with the file with our support team. And we will update this thread when we have information to share.
Related Content
- 10 years ago