After my last set of changes, Publish no longer works. I get an error message and dutifully send the message to Support. I haven't yet found a work around --- it fails no matter if I'm targeting Articulate Online, the Web, whatever.
I am able to preview the project successfully.
Thoughts?
Meanwhile I am making more changes for my client, and if that accidentally fixes the problem I will have no complaints. I have saved a copy of the project as it now stands in case it is helpful for debugging.
We'd be happy to take a look at the file and test publishing it ourselves. You'll also want to make sure that you're on the latest update of Storyline, (Update 7 for Storyline 2) and publishing to a local drive as described here (when not using AO). If you'd like to share the .story file here you can attach it using the "Add Attachment" button.
I tried it, and the import seemed to going alone fine for maybe 20 seconds or so, at which point Storyline completely crashed in Windows.
Thanks anyway, I appreciate that you reached out with something to try.
I will conclude that somewhere along the line the Storyline software managed to corrupt the .story file. I will keep my fingers crossed that in my subsequent editing for the client I accidentally remove the corrupted portion.
Official Articulate Support, please advise. Is this a known defect?
I'm pretty sure the forums can handle a 122 MB project - but just in case you can always send along to us here as well.
Wendy's suggestion is another good one to test, you could look at following the steps here in terms of importing into a new project, ensure it's saved locally and then publish.
Looks like we were posting at the same time! I downloaded your file and published it for web - just to test it out and it worked on my end.
If publishing isn't working on your end and you are on the latest update, I'd also want to have you go through the repair process. Additionally you mentioned corruption, and although it can be difficult to track down you may want to 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.
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.
another way to try is to import in say 10 slides at a time and try to publish - i know its time consuming but sometimes that isolates the naughty slide if there is one. I'll download your file now and see if I can publish it
Thanks Arthur and I'm glad we were able to confirm it's not the file itself - so definitely look into those items. Do you leave Storyline open while Windows is hibernating? I typically do the full shut down.
15 Replies
Hi Arthur,
We'd be happy to take a look at the file and test publishing it ourselves. You'll also want to make sure that you're on the latest update of Storyline, (Update 7 for Storyline 2) and publishing to a local drive as described here (when not using AO). If you'd like to share the .story file here you can attach it using the "Add Attachment" button.
Yes, it's the latest version and it's not publishing to anywhere, like I
said.
I can attach a 122M file? Really?
Thanks,
-Arthur
Hi Arthur
have you tried creating a new project file and importing your current file into it and trying to pubish?
Great idea!
I tried it, and the import seemed to going alone fine for maybe 20 seconds or so, at which point Storyline completely crashed in Windows.
Thanks anyway, I appreciate that you reached out with something to try.
I will conclude that somewhere along the line the Storyline software managed to corrupt the .story file. I will keep my fingers crossed that in my subsequent editing for the client I accidentally remove the corrupted portion.
Official Articulate Support, please advise. Is this a known defect?
Hi Arthur,
I'm pretty sure the forums can handle a 122 MB project - but just in case you can always send along to us here as well.
Wendy's suggestion is another good one to test, you could look at following the steps here in terms of importing into a new project, ensure it's saved locally and then publish.
Thanks Ashley, attached the file on my previous reply.
Looks like we were posting at the same time! I downloaded your file and published it for web - just to test it out and it worked on my end.
If publishing isn't working on your end and you are on the latest update, I'd also want to have you go through the repair process. Additionally you mentioned corruption, and although it can be difficult to track down you may want to consider these preventative measures to protect your project files:
Hi Arthur
another way to try is to import in say 10 slides at a time and try to publish - i know its time consuming but sometimes that isolates the naughty slide if there is one. I'll download your file now and see if I can publish it
I do 1 and 2. I will try 3. I will do the repair thing.
I "hibernate" in Windows overnight, is that a cause for concern a la point 4?
Thanks Ashley!
-Arthur
Please don't bother --- Ashley has done that already. Thanks!!!
Hi Arthur
published successfully to web so it's not the story file - something else is amiss. I've attached the published zip file for you.
Oops...didn't refresh my screen before I posted.
Thanks Arthur and I'm glad we were able to confirm it's not the file itself - so definitely look into those items. Do you leave Storyline open while Windows is hibernating? I typically do the full shut down.
Yes I do, but not anymore! :-)
Good to hear Arthur. ;-)
Let us know if you need anything else.
This discussion is closed. You can start a new discussion or contact Articulate Support.