In addition to confirming that you are working locally, you will also want to ensure that you are using the latest update of Storyline 2. Are you opening the file directly in SL2 (file, browse, find the file) or are you clicking on the icon from a folder to allow the update to happen?
And the following things are good practices to follow to prevent some unusual 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.
If you continue to be unable to save it, the file may have become corrupt and one solution for a corrupt file could be to import your Storyline file into a new project: Importing From Another Storyline Project.
1 Reply
Hi, Dan -
In addition to confirming that you are working locally, you will also want to ensure that you are using the latest update of Storyline 2. Are you opening the file directly in SL2 (file, browse, find the file) or are you clicking on the icon from a folder to allow the update to happen?
Please also check this out in the event that the temp directory is full.
And the following things are good practices to follow to prevent some unusual behavior:
If you continue to be unable to save it, the file may have become corrupt and one solution for a corrupt file could be to import your Storyline file into a new project: Importing From Another Storyline Project.
If this behavior continues on multiple files, you may also want to conduct a repair of your Storyline software.
This discussion is closed. You can start a new discussion or contact Articulate Support.