Hi everyone,

Can someone help me with the question above, by chance?

Thanks.

Michele

Hi there Michele,

Sorry for the delay! Not quite sure how we missed your post.

First, the file size is pretty large. While there is no official maximum size, the larger the project file the more memory you're going to use. If your machine doesn't have a lot of memory that can result in some issues. That's not to say that it's only an issue with the machine - it very well could be the file.

If the file is corrupt, the best way to fix it is to import the portion of the project that has been saved into a new project file. 

Here's how:

Importing from Another Storyline Project - E-Learning Heroes

You may also want to make sure that your project file is on your primary hard drive, not on a partition and that there are only alphanumeric characters in the file names (no spaces, underscores, etc.).

• Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior. 
• You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
• Avoid using special characters, accents or symbols in your file names (this includes spaces and underscores).

Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the following Microsoft article.

If that doesn't help, try breaking the project down. Try importing a couple scenes using the import method I suggested. Remove those scenes and try to save. Keep trying this until the file size is smaller - if you reach a point where you can save the file, make sure you back it up. If you try to add on to it and you see that error again, it may simply be that your machine doesn't have the resources to work with such a large file.

Let me know how it goes.

Thanks!

Thanks Christine,

I tried to create a new file from scratch importing some scenes (4 with freeform activities).

The new file is 24 MB so small and I saved it with a small path lengh from my c.

Though the problem is still there i can't work further....

I really don't know what to do.

I'm currently downloading the new update of SL (5).

Do you think I should reinstall completly or is the update should be enough.

Thnks for your help.

Michele:

Have you checked the amount of free space on your C: drive?  I was having similar issues and I found that I only had a couple of gig of free space on the hard drive so it was running out of space for the virtual memory to work correctly. I cleaned up files I no longer needed and the issue seems to have gone away.

Brent

Hi Brent,

Thanks for sharing that tip! Hopefully that will help Michele :)

Michele,

You shouldn't need to reinstall. Just install the update and see if that helps. If it does not, however, I'd recommend following these steps, instead of the standard uninstall/reinstall method. 

Let us know how it goes! :)

Best,

Christine

Hi Brent,

I have about 59 GB of free space on my hard drive.

Do you think that's enough?

Thanks for your help!

Michèle.

Michele:

That should be more than enough.  It must be something else.

Brent

Hi Christine,

I have installed the update and ran into similar problems....

I'll try the recommandations you told me and will tell you.....

Michèle

I have run the repair programm: The problem still remains...

I worked first on the smaller file (about 33 MB) where I have created Activities slides.

I tried to import those activities slides into the mother presentation that I have reduced to 120 MB .

Impossible to insert one more slide...

I feel disappointed...that mean I can't use SL?

Help again.

Michèle

Hi Michèle,

I'm glad to hear that it's not a space issue - at least that's confirmed :)

How much memory do you have on the machine? The requirement is 512 MB minimum. However, the larger the files are, the more RAM or memory you're going to need. A 120MB file is obviously going to use a lot more than a very small file. 

My concern is that you mentioned earlier that you were having trouble with a much smaller file of 24 MB. 

I don't think it's an actual issue of the size - but maybe the memory. Especially if you've been able to save the 120 MB file in the first place.

You've made sure no other programs are running in the background, correct? If not, try closing everything you can and try again. You may want to check your task bar and see if there are any services there that you can close. 

You could also check Task Manager to see if there are any programs using up a lot of your available memory. To do this, press CTRL+ALT+DEL or CTRL+SHIFT+ESC on your keyboard. 

Let us know how it goes! :)

Christina,

1) Here are the specifications of my PC:

-Windows 7 Pro service Pack 1

-Intel(R) Core(TM)

-RAM memory: 4 GB (3,17 GB Usable)

-32 Bits

2) I have closed all the programs (except SL)

3) I have verified all the process workinq at the background: the process using the bigger space of the memory  is SL.

4) I have  closed IE

5) I tried again to import a slide: I got one slide inserted but not further....the "system out of memory" message appeared again....:-(

What else can I do?

Michèle.

Change to 64 bit windows. Since we did that we have not had a single memory error.

Hi Christopher and Michèle,

Thanks for sharing that suggestion, Christopher. I'm not sure if that's something that Michèle will be able to try - but I am curious to see if that does solve the problem for her. 

What do you think, Michèle? Is that something you'd be able to try?

Thanks!

Michele:

Have you tried to adjust your virtual memory?  Here are the instructions:

Yes, the "out of memory" warning seems to occur with users running Win x32 and 4gb of ram.  32bit windows doesn't even utilize all 4gb.  The optimal way to run Storyline is a 64bit windows w/ at least 8gb of ram.

Upping the virtual memory might work, but more like a band-aid to the bigger issue.

I routinely build 200mb+ files (video) and never get that with 8gb of ram. There have been numerous threads similar to this and one thing they seem to have in common is 32bit windows and 4gb of ram.

Thanks everyone for your help!

Christina: I tried on a PC of a colleague with 64 bit : it works !

For the moment I will work like this for a week I'm not able to upgrade my own PC .

But, thanks Brent for your advise: I will ask my IT to modify the virtual memory on my PC. I will tell you how it works.

Michele

Michèle,

That's great to hear! If you have the opportunity to try that out on your machine, I'd really like to know. 

I'm glad that you're able to access this elsewhere in the meantime. Please keep us updated.

Best,

Christine

I have tested Brent advice but the problem remains the same....changing the virtual memory size didn't help me.

It's a real problem, because I can't upgrade my PC now (I have lot of modules developped with studio 9....and it doesn't run with windows 64MB.....)

For the moment I have no time importing those studio's file into SL and really it's not my priority....

Is Articulate planning something for customers in my case....update 6 for example?

That's interesting that Storyline seems to have issues on 32 bit Windows apparently with more than 2G ram. You need a PAE type solution for the kernel to recognize more ram than that. I remember seeing issues with this about oh.... 10 years ago or so. Not sure why Update 5 would cause this issue?

Hi David,

Can you explain more about the PAE solution?  How to do that?

Thanks

This is still a problem. Any updates? It's been maybe 5, 7 years so far.

Hi there, Nicole. It sounds like you're having issues using Storyline 360. These are the minimal system requirements for Storyline 360 for reference. Let me grab some details from you so we can help better!

• What kind of error message are you seeing?
• Is this happening with a particular file, or with all files?
• What version of Windows are you using?

If you'd prefer, you can open a priority support case with my team since you have Articulate 360 for Teams. We'll be happy to help!