external component exception won't allow me to save file

Oct 20, 2015

I am almost done with a large storyline 1 project and the message came up "cannot be saved, external component has thrown an exception"

I would appriciate insight and a way to fix this.

5 Replies
Ashley Terwilliger-Pollard

Hi Scott,

I haven't seen that error message before so I'd want to gather a bit more information. 

Are you on the latest update of Storyline 1 Update 10? Are you trying to save, publish or both? Have you confirmed to be following the guidelines here in regards to working on .story files? Is this file already saved as an earlier copy, have you tried doing a save as?  

Scott Ellis

I believe I am on the latest version, as I updated 2 weeks ago. Trying to save as it stopped responding when I added a video. Cant delete the video or the slide. Tried Save as too. Multiple days work in the file, previous days are saved.
Scott

[cid:457A62A2-4108-4BCE-94BD-B56D3C996722]
Scott Ellis Ed.D
Certified Professional Coach
Leadership & Process Improvement
scottellis@psquaredusa.com
425 985 8508

Ashley Terwilliger-Pollard

Hi Scott,

First, responding via email includes your signature here - so you're welcome to edit the post to remove that information.

You mentioned it's not saving after adding this video - did you try adding the video into a new blank Storyline file to see if it's something in the video that's causing the issues? Can you not delete the video physically - as in when you try Storyline freezes or crashes? If so, I'd say there is likely an element of corruption on that slide. File corruption is unpredictable, and there's no straightforward way to determine what causes it. Common causes are environmental (disk errors, power outages, improper shutdowns), viruses, failed Windows updates, and even file size (i.e., very large files have a higher risk of corrupting).

Consider these preventative measures to protect your project files:
 
1) Save and publish projects on your local hard drive. Working on a network drive or external USB drive can cause erratic behavior due to latency.
 
2) Save incrementally. If your app has an AutoRecovery feature, take advantage of it. If not, save a new version of your project every hour or so with a new file name each time. If a file becomes corrupt, you'll still have a working version available.
 
3) Install Dropbox. Snapshots of changes in your local Dropbox folder are kept for 30 days. If a file is damaged or deleted, you can restore a previous snapshot: https://www.dropbox.com/help/11/en.
 
4) Don't leave the app open and unattended for long periods of time. Some users have reported file corruption after leaving their apps open overnight. It's possible that a malware scan or disk backup could run because the machine is idle, making your app vulnerable to crashing.
 
Let us know if you're able to test that video in a new file and how it behaves after that. You could also look at importing what you have currently into a new project following these directions
Ashley Terwilliger-Pollard

Hi Scott, 

It sounds like this video file has corrupted the course - so if you're unable to save and/or open a new project, I think you'll have to close out and revert back to one of your earlier saved versions. You mentioned a few back up copies - but there may also be a copy of your project in the temporary files. Here's how to check:

1) Open this folder in Windows Explorer:
 
%appdata%\Articulate\Storyline
 
2) Scan the contents of this folder for a file that starts with the name of your project. If you find one, copy it to your desktop. If you find more than one, copy the latest version to your desktop.
 
3) Change the file extension of the copy on your desktop from *.tmp to *.story.
 
4) Double-click the file to open it in Storyline.
 
That may at least bring back some of the more recent work from your last save. Once you've closed down Storyline, then I'd look at testing that video in a brand new file to see how it behaves on it's own. 
 
Not the answer you're looking for I'm sure - but hopefully it'll help recover some of the work. 

This discussion is closed. You can start a new discussion or contact Articulate Support.