I'm sorry to hear about the issue you're having and thanks for letting us know the troubleshooting steps you've already gone through. I'm wondering if your IT Team went through all the steps here? It's more involved than a normal repair but it solves a lot of standard issues such as this.
My IT Department tried the steps listed in that link, it works up to a certain point. If the file uses more memory than 600K under the Processes Tab in the Windows Task Manager I get the same error.
This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications with {SECURE MESSAGE} in the subject line have been sent using a secure messaging system. Communications that do not have this tag may not be secure and could be observed by a third party. Thank you for your cooperation. Northwestern Mutual is an Official Corporate Partner of the NCAA. NCAA is a trademark of the National Collegiate Athletic Association.
First, I wanted to share that responding via email includes your signature here and you're welcome to edit the post to remove that information if you wish.
In regards to the behavior, as Jim mentioned, Storyline can operate on any of the following systems: Windows Vista SP2 or later (32-bit or 64-bit), Windows 7 (32-bit or 64-bit), or Windows 8 (32-bit or 64-bit), but it's worth noting, Storyline itself is only a 32-bit program.
If you're still having difficulty, you're also welcome to connect with our Support engineers who could take a look at anything else that may be interfering with the set up of Storyline.
Yeah this really bites. First time I've experienced the low memory issues but this is probably the largest project I've worked on (.story project file is about 350MB total in size). Getting the low memory errors, closed out applications and processes that are not needed, deleted all the temp files as Ashley suggested. Still no luck. Guess I'll have to close out Storyline and lose some work. Using Windows 7 32bit so the nifty RAM patch won't help. Running the latest Storyline 2 version as well. Unhappy.
Thanks Duane for running through those steps and letting us know, and I'm sorry that it didn't help you at all. Did you already reach out to our support team so that we could take a better look at your set up and see if there is anything else we might be able to offer advice on?
Haven't reached out to support yet... was desperate to try some more immediate alternatives. My work laptop is running 32bit, 4GB RAM Windows 7. I ran home with the project file and loaded it up on my home laptop, 64bit, 8GB Windows 8. Everything runs exceptionally fine!
Wondering if perhaps it's time to update the system requirements for Storyline 2? And probably update my work laptop so I don't run into this again-
Aha, good point. This was my first foray into 300MB+ project size. Lots of screen recordings for a software application, using both video on a slide and step-by-step methods. Never once had a memory problem prior with smaller projects. So maybe a recommendation to the minimum that it is supported up to a certain size of .story project file? I'm wondering if the pattern of folks having issues boils down to that.
All I know is that I'm working with a system that exceeds the minimum requirements this afternoon, and all is well. And once again, Storyline rocks!
Glad to hear things are back to working well for you. As far as the pattern, I don't know that our team has discerned one yet and we've looked at a large grouping of files - but that's a good one to keep in mind.
Please feel free to let us know if you need anything else.
It looks like I responded to a similar message of yours about a month ago in this thread. We'd be happy to take a look at your file and how it's behaving and then our team can get a better sense of what's occurring and in what ways our team can assist.
If you have not already done so, add a feature request asking Articulate to consider creating a 64-bit version of Storyline. The more request for this, the better.
First I wanted to let you know that responding via email includes your signature here, so you're welcome to edit the post and remove that information if you wish.
In regards to the low memory error, did you already go through the troubleshooting steps in this thread such as confirming to be working locally, using the latest update of Storyline 2, and closing down other applications or programs that could be drawing on the system memory? If so, and you're still having difficulty I'd invite you to work directly with our Support engineers so that they could gather a bit more information about your system set up.
Hi Michael, I'm happy to help you straighten this out. Can I have a little more information on your set-up?
Are you on the most recent update of Storyline 2?
Are you working from your local C: drive?
Have you closed down other applications or programs that could be drawing on the system memory?
If your answer is "yes" to all of those questions, I'd want to connect you with our Support Engineers. They'll work with you one-on-one to get you up and running smoothly again!
Thanks for that update Michel, and just an FYI - Looks like your email signature came through when you replied via email! No worries, this Peek video will show you how to remove it if you'd like!
I have this same issue. I am running Storyline 3 on VMWare and all my projects are run locally. I have no other programs open in Windows when this is happening. I'm in the middle of working on a project, and I get 2 separate error messages: "The project file could not be saved. Can not access a closed Stream." and "Close non-essential applications and save your project file."
This is a large project, around 678 MB. I am unable to save my work at the point these error messages pop-up. This has happened to me several times already and keeps becoming more and more frequent. I deleted the temp files in the %temp% folder and even increased the memory in my VMware. However this only works for about 5 minutes. I have to keep deleting the temp folder every 5 minutes. I already contacted technical support, but the solution they gave me was NOT a solution. They want me to copy all my slides into a new instance, however when the error message shows up, it says I don't even have enough memory to create a new instance. It freezes and then I have to force quit and I lose my saved data; having to start over again. I am running a 64 bit version of VMware. Why hasn't Storyline been upgraded to 64 bit by now? My company has spent a lot of money on this program, and it's gotten to the point where it is becoming unusable. I can't find a solution and I am on a strict deadline. Please help!
Hey Ross, I'm really sorry this is something you're continuing to see happen-- thanks for letting us know about it.
I see that you're currently working with my colleague Eloisa, and I'll relay this information to her to keep everything connected as she continues to work with you on this. We won't leave you hanging!
I know this must be frustrating, as I can see you've put a lot of time into troubleshooting it on your own already. I really appreciate you working with us to get a resolution and I'll be keeping an eye on your case moving forward.
123 Replies
Hi Jennifer,
I'm sorry to hear about the issue you're having and thanks for letting us know the troubleshooting steps you've already gone through. I'm wondering if your IT Team went through all the steps here? It's more involved than a normal repair but it solves a lot of standard issues such as this.
My IT Department tried the steps listed in that link, it works up to a certain point. If the file uses more memory than 600K under the Processes Tab in the Windows Task Manager I get the same error.
You probably have the 32-bit version of Windows installed on your computer. Windows 32-bit can only address 640K of memory.
Windows 64-bit allows extended addressing.
Regards,
Jim Momsen, CPT
Consultant - Workforce Learning & Performance Solutions
[cid:image001.png@01CFF8D5.64B304D0]
O&T Workforce Planning & Development
(414) 661-6251
Location 1E350 /Cubie E3106
JimMomsen@NorthwesternMutual.com
This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications with {SECURE MESSAGE} in the subject line have been sent using a secure messaging system. Communications that do not have this tag may not be secure and could be observed by a third party. Thank you for your cooperation. Northwestern Mutual is an Official Corporate Partner of the NCAA. NCAA is a trademark of the National Collegiate Athletic Association.
Hi Jennifer (and Jim),
First, I wanted to share that responding via email includes your signature here and you're welcome to edit the post to remove that information if you wish.
In regards to the behavior, as Jim mentioned, Storyline can operate on any of the following systems: Windows Vista SP2 or later (32-bit or 64-bit), Windows 7 (32-bit or 64-bit), or Windows 8 (32-bit or 64-bit), but it's worth noting, Storyline itself is only a 32-bit program.
If you're still having difficulty, you're also welcome to connect with our Support engineers who could take a look at anything else that may be interfering with the set up of Storyline.
Yeah this really bites. First time I've experienced the low memory issues but this is probably the largest project I've worked on (.story project file is about 350MB total in size). Getting the low memory errors, closed out applications and processes that are not needed, deleted all the temp files as Ashley suggested. Still no luck. Guess I'll have to close out Storyline and lose some work. Using Windows 7 32bit so the nifty RAM patch won't help. Running the latest Storyline 2 version as well. Unhappy.
Thanks Duane for running through those steps and letting us know, and I'm sorry that it didn't help you at all. Did you already reach out to our support team so that we could take a better look at your set up and see if there is anything else we might be able to offer advice on?
Haven't reached out to support yet... was desperate to try some more immediate alternatives. My work laptop is running 32bit, 4GB RAM Windows 7. I ran home with the project file and loaded it up on my home laptop, 64bit, 8GB Windows 8. Everything runs exceptionally fine!
Wondering if perhaps it's time to update the system requirements for Storyline 2? And probably update my work laptop so I don't run into this again-
Well, those are the "minimum" requirements. :-)
Thanks for the update Duane, and glad you were able to get it working finally.
Aha, good point. This was my first foray into 300MB+ project size. Lots of screen recordings for a software application, using both video on a slide and step-by-step methods. Never once had a memory problem prior with smaller projects. So maybe a recommendation to the minimum that it is supported up to a certain size of .story project file? I'm wondering if the pattern of folks having issues boils down to that.
All I know is that I'm working with a system that exceeds the minimum requirements this afternoon, and all is well. And once again, Storyline rocks!
Glad to hear things are back to working well for you. As far as the pattern, I don't know that our team has discerned one yet and we've looked at a large grouping of files - but that's a good one to keep in mind.
Please feel free to let us know if you need anything else.
i am unhappy with articulate storyline 2,
there is no 64 bit version, For me, articulate totally Useless. My file not able to save and not publish, show low memory message every time.
Regard
furkan ahmad
Hi Furkan,
It looks like I responded to a similar message of yours about a month ago in this thread. We'd be happy to take a look at your file and how it's behaving and then our team can get a better sense of what's occurring and in what ways our team can assist.
Has this problem been resolved? Any update? I have the same issue. 239 GB used 237 GB free, can't save. Says low on memory.
The only resolution I had was requesting a 64 bit computer from my company. Once I started using the 64 bit, the problems disappeared!
Agree, I got a new laptop at work too, 64 bit with 12GB RAM. No problems any more!!!
This post was removed by the author
If you have not already done so, add a feature request asking Articulate to consider creating a 64-bit version of Storyline. The more request for this, the better.
Hi Kathleen,
First I wanted to let you know that responding via email includes your signature here, so you're welcome to edit the post and remove that information if you wish.
In regards to the low memory error, did you already go through the troubleshooting steps in this thread such as confirming to be working locally, using the latest update of Storyline 2, and closing down other applications or programs that could be drawing on the system memory? If so, and you're still having difficulty I'd invite you to work directly with our Support engineers so that they could gather a bit more information about your system set up.
This post was removed by the author
OK - Now I am having the same problem on a NEW system with 16G of of RAM and running Storyline 2. Has this not been fixed...?
Hi Michael, I'm happy to help you straighten this out. Can I have a little more information on your set-up?
If your answer is "yes" to all of those questions, I'd want to connect you with our Support Engineers. They'll work with you one-on-one to get you up and running smoothly again!
I appear to have resolved the issue by unloading and reloading the software.
I have not had the problem again since.
Michel
------------------------------------------------------
Michel Luca Gilbert
President, Senior Facilitator
Wellspring Learning, Inc.
802-233-1638
www.wellspringlearning.com
Thanks for that update Michel, and just an FYI - Looks like your email signature came through when you replied via email! No worries, this Peek video will show you how to remove it if you'd like!
I have this same issue. I am running Storyline 3 on VMWare and all my projects are run locally. I have no other programs open in Windows when this is happening. I'm in the middle of working on a project, and I get 2 separate error messages:
"The project file could not be saved. Can not access a closed Stream."
and
"Close non-essential applications and save your project file."
This is a large project, around 678 MB.
I am unable to save my work at the point these error messages pop-up. This has happened to me several times already and keeps becoming more and more frequent. I deleted the temp files in the %temp% folder and even increased the memory in my VMware. However this only works for about 5 minutes. I have to keep deleting the temp folder every 5 minutes. I already contacted technical support, but the solution they gave me was NOT a solution. They want me to copy all my slides into a new instance, however when the error message shows up, it says I don't even have enough memory to create a new instance. It freezes and then I have to force quit and I lose my saved data; having to start over again. I am running a 64 bit version of VMware. Why hasn't Storyline been upgraded to 64 bit by now? My company has spent a lot of money on this program, and it's gotten to the point where it is becoming unusable. I can't find a solution and I am on a strict deadline. Please help!
Hey Ross, I'm really sorry this is something you're continuing to see happen-- thanks for letting us know about it.
I see that you're currently working with my colleague Eloisa, and I'll relay this information to her to keep everything connected as she continues to work with you on this. We won't leave you hanging!
I know this must be frustrating, as I can see you've put a lot of time into troubleshooting it on your own already. I really appreciate you working with us to get a resolution and I'll be keeping an eye on your case moving forward.
Thanks again!