SL360 Publishing Error
Nov 10, 2016
I have a .story file (about 480mb) created with SL2. Whenever I publish it from Storyline 2 it gets published succesfully. I have a i7 PC with 16GB ram. When I open the file with Storyline 360 the file gets upgraded. But when I publish the course, it pops up and error while publishing 'memory is low that i need to close non-essential applications'. Even when SL360 is the only application runing on the PC. Is there a size limit to SL360?
9 Replies
Hi Kennethg,
No size limit to publishing in SL360 - so can we take a look at your .story file? You can attach it here or send it along to our Support Engineers here.
I'm having the same error, was a solution found in this case?
Hi Liz,
It looks like our team was waiting for some additional information from Kennethg, in the form of another project file so I don't have any additional information on his case to share. If you'd like us to take a look at your file we'd be happy to and you can use the same link above to upload it to our Support Engineers.
There was an update on the SL360. This cut the resources required (or what my computer was using ) is half. So i was later able to publish the course without any issues. This is common in the files that you convert from SL2 to SL360.
Thanks Kennethg for the update and I am glad to hear things are working for you again.
Hi there, just bumped into the same Low Memory problem with SL360. PC is a brand new Dell with 16 Gb ram. It happens randomly and even at starting up 360 without a story. even loaded. Seems to me like a bug we suffered in the past with SL2. Attached a screenshot.
Hey John,
When we saw that error in the past it was an issue of temp files cause the memory to bloat excessively. There was a fix for that in Storyline 1 as it seemed connected to publishing or preview. Can you connect with our Support team so that we can look at pulling the memory logs on your system to help track down where the error is happening?
Hi Ashely and thanks, I have just submitted the case to your support team. I'll await the outcome.
Thanks John and I'll follow along in your case (# 00998769 for my reference).
This discussion is closed. You can start a new discussion or contact Articulate Support.