I haven't seen the part of the error regarding the "found invalid data while decoding" piece - and you mentioned having the latest update install, but you may also want to look into the troubleshooting steps here in regards to purging the temp files.
If you continue to have difficulty, please let us know!
I'm really sorry to hear that you've run into the same issue. This forum discussion is a bit older, but the same steps apply in terms of ensuring you're working on project files according to the guidelines here and using the latest update of Storyline (currently Storyline 2 Update 10).
If it's just one project file you could also look at the options for importing it into a new project file to see if that resolves any of the behavior.
I experienced the same issue today when trying to update an old Storyline file from SL2 to SL360. The update wouldn't allow me to save the file, which was saved locally. It would only state the error message experienced by Robyn and Cindy.
Luckily, I had a backup file that upgraded fine, but there was an issue with the first file attempted. I transferred it to my desktop and converted it just fine.
What was the previous file path for your file before you put it on your desktop? Even if it was local, the file path could have been well over 260 characters (or getting close) and that may have caused issues when it tried to go through the update as well.
Glad to hear the back up copy and the desktop got you back in working order though!
9 Replies
Hi Robyn,
I haven't seen the part of the error regarding the "found invalid data while decoding" piece - and you mentioned having the latest update install, but you may also want to look into the troubleshooting steps here in regards to purging the temp files.
If you continue to have difficulty, please let us know!
I am still experiencing the same problem, even after purging the temp files
and restarting my computer.
I will just have to copy everything over into a new document.
Hi Robyn,
I'm sorry to hear it, and if it occurs again, you may also want to look at conducting the repair as detailed here.
I like to know whether this issue has any updates or not. I am having the same issue now :-(
Hi Cindy,
I'm really sorry to hear that you've run into the same issue. This forum discussion is a bit older, but the same steps apply in terms of ensuring you're working on project files according to the guidelines here and using the latest update of Storyline (currently Storyline 2 Update 10).
If it's just one project file you could also look at the options for importing it into a new project file to see if that resolves any of the behavior.
I experienced the same issue today when trying to update an old Storyline file from SL2 to SL360. The update wouldn't allow me to save the file, which was saved locally. It would only state the error message experienced by Robyn and Cindy.
Luckily, I had a backup file that upgraded fine, but there was an issue with the first file attempted. I transferred it to my desktop and converted it just fine.
I think crossing my fingers helped. : )
Hey Daniel,
What was the previous file path for your file before you put it on your desktop? Even if it was local, the file path could have been well over 260 characters (or getting close) and that may have caused issues when it tried to go through the update as well.
Glad to hear the back up copy and the desktop got you back in working order though!
The file path was under 260 characters. It was around 40-50. The SL2 file was on an external hard drive before I moved it to the desktop.
Ah, that could have done it Daniel - thanks for popping back in with an update.
This discussion is closed. You can start a new discussion or contact Articulate Support.