I'm having problems with a lesson when I add a slide which draws from a question bank. The lesson previews and publishes fine without the question bank, but crashes after I've added it and then try to preview or publish. I'm using Articulate 2, has anyone else come across this?
The lesson is commercially sensitive so I cant attach on this forum, but happy to send the lesson to Articulate support.
Are you seeing the same thing across other files or is it specific to this file? I'd look first at confirming that you're working on local project files and then I'd go through the repair of Storyline. If you're still having difficulty you can send along a copy of your project to us here.
Hi Ashley,
I've tried these and I am still having problems with this lesson. It only crashes with the question bank in the lesson. If I remove the question bank it doesn't crash.
I have attached the lesson for you.
Thanks, Simon
It looks like you responded via email, and as such the attachments don't come through. You'll need to visit this forum thread and use the "Add Attachment" button to upload the .story file here for us.
Thanks for sharing here. I took a look and saw the same as you on my first attempt and importing the entire file into a new project. I instead looked at removing your question bank slide and recreating it - that allowed me to publish successfully and everything seemed to work normally. Can you take a look at the attached copy and let me know how that behaves for you?
Hi Ashley, that's working fine now thanks. I tried quite a few times to recreate the question bank, but didn't try importing into a new project. DO you know why it was happening so I can avoid it in future? Thanks again, Simon
Glad that one is working for you. I had to do the import, and then recreate the bank. I would say it's something connected to an element of corruption in the file, and 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.
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.
I'm having the same problem with various number of courses in SL 2 . This is the 5th course this month that does the same. Is there an SL2 update, same as SL 1 had update v5.
Thanks for reaching out here and sharing the image - did you review the information previously shared in terms of working on local project files, importing into a new project, etc.? That worked previously for the file Simon shared - but you can also look to confirm that you're working on the latest update of Storyline 2, Update 7.
I do understand this is a workaround, But what is causing this ? as this is
happening a lot more often then what it should. I cant keep
redesigning/reimporting projects from our developers cause of question
banks ?
Within Simon's file I wasn't able to determine a specific cause, but corruption is unpredictable and notoriously tricky to track down. If you're following the guidelines shared above, those are good steps to prevent any corruption issues and if you'd like our team is always happy to take a look at a file to see if there is something we can track down. You can connect with our Support engineers here and they're available 24/7.
I was just checking in on your case and it looks like Miker recommended that you go through the repair steps detailed here to resolve some of the odd behavior with your question banks crashing the course.
17 Replies
Hi Simon,
Are you seeing the same thing across other files or is it specific to this file? I'd look first at confirming that you're working on local project files and then I'd go through the repair of Storyline. If you're still having difficulty you can send along a copy of your project to us here.
Hi Ashley,
I've tried these and I am still having problems with this lesson. It only crashes with the question bank in the lesson. If I remove the question bank it doesn't crash.
I have attached the lesson for you.
Thanks, Simon
Hi Simon,
It looks like you responded via email, and as such the attachments don't come through. You'll need to visit this forum thread and use the "Add Attachment" button to upload the .story file here for us.
Hi Ashley, Please see attached lesson. Thanks
Hi Simon,
Thanks for sharing here. I took a look and saw the same as you on my first attempt and importing the entire file into a new project. I instead looked at removing your question bank slide and recreating it - that allowed me to publish successfully and everything seemed to work normally. Can you take a look at the attached copy and let me know how that behaves for you?
Hi Ashley, that's working fine now thanks. I tried quite a few times to recreate the question bank, but didn't try importing into a new project. DO you know why it was happening so I can avoid it in future? Thanks again, Simon
Hi Simon,
Glad that one is working for you. I had to do the import, and then recreate the bank. I would say it's something connected to an element of corruption in the file, and 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).
Hi there Ashley,
I'm having the same problem with various number of courses in SL 2 . This is the 5th course this month that does the same. Is there an SL2 update, same as SL 1 had update v5.
Ps: If I take out the Question Bank and cut the questions from the bank to the slides Works 100% as soon as I had another Bank it crashes.
Hi Chris,
Thanks for reaching out here and sharing the image - did you review the information previously shared in terms of working on local project files, importing into a new project, etc.? That worked previously for the file Simon shared - but you can also look to confirm that you're working on the latest update of Storyline 2, Update 7.
I do understand this is a workaround, But what is causing this ? as this is
happening a lot more often then what it should. I cant keep
redesigning/reimporting projects from our developers cause of question
banks ?
Hi Chris,
Within Simon's file I wasn't able to determine a specific cause, but corruption is unpredictable and notoriously tricky to track down. If you're following the guidelines shared above, those are good steps to prevent any corruption issues and if you'd like our team is always happy to take a look at a file to see if there is something we can track down. You can connect with our Support engineers here and they're available 24/7.
Thanks, I've submitted the Query. :)
Thanks Chris and if you'd like to let me know the case number I'm happy to follow along.
*Hi there, Case Number:* 00740158
Thanks Chris - and I can see that Miker has been assigned to your case, so I'll follow along as well.
Hi Chris,
I was just checking in on your case and it looks like Miker recommended that you go through the repair steps detailed here to resolve some of the odd behavior with your question banks crashing the course.
This discussion is closed. You can start a new discussion or contact Articulate Support.