I have been trying to publish a course for web for literally the past 4-5 hours. Every time my publishing progress bar is right about to get to the end, I get a pop up that Articulate Storyline has crashed. I am saving locally to my hard drive, I have tried to repair (uninstall, reboot, install, reboot), and save to Articulate online. No luck. It will let me publish to Word, but that is all. I am on a tight deadline, and I am at a loss of what to do next. Has anyone else had these issues lately? Please help!
have you tried creating a new story file and importing your current one in. Also, check the file name to make sure it isn't longer than 256 characters and doesn't have any wildcards or symbols in the file name.
If you like, I am happy to try and publish for you and upload the zip back here
Hi, Erin -- So sorry to hear you are having such difficulties and that importing into a new file did not do the trick! Have you had an opportunity to review this information on Unexpected or Erratic Behavior in SL2? You may find it beneficial to run through the repair steps listed.
If issues persist, you are welcome to share your file and I can attempt to publish it on my machine to see if I encounter the same behavior. If that is the case, I would then recommend that you reach out to our Support Engineers for further investigation of what may be causing the issue.
Thanks, Christie. I shared the file with the Support Engineers this morning and got a response around 9:30 stating that they are currently reviewing. I think that it is something problematic within the course because I was able to replicate the issue on a colleague's computer.
I appreciate the update, Erin and I see that your case (00686125) is being handled by our Support Engineer, Abel. I intend to follow along with the progress being made and will share updates here in the thread for others who may encounter a similar issue. :)
Hi, Erin -- Thanks for touching base, and as cases are addressed in the order in which they are received, it appears that your case is still showing as being in the testing stage. Many thanks for your patience, as we work as quickly and efficiently as possible to provide all of our customers with the highest level of quality support. I reached out to Abel to let him know of your inquiry, and he will be in touch as soon as possible. :)
Hello again, Erin -- You will be hearing from Abel via email as well momentarily, but he just let me know that the "Print Results" button in slide 7.13 Results Slide is causing the crash. The customer will need to delete the button and just check the "Allow user to print results" button in Results Slide option for the button to recreate."
Please give that a shot, and reply to Abel's email if you find that you still need further assistance.
Hi, Erin -- So sorry to hear that issues persist, but I appreciate that you've shared an update, and I will continue to track the progress being made on your case. :)
Hello Patrick - Sorry to hear that you ran into difficulty with this. I second Wendy's original suggestion and advise to attempt to import into a new file first to see if this alleviates the issue.
13 Replies
Hi Erin
have you tried creating a new story file and importing your current one in. Also, check the file name to make sure it isn't longer than 256 characters and doesn't have any wildcards or symbols in the file name.
If you like, I am happy to try and publish for you and upload the zip back here
Thanks, Wendy. I'm currently in the process of importing it to a new file. Hopefully that will work!
Importing it to a new file did not work. It is still crashing.
Hi, Erin -- So sorry to hear you are having such difficulties and that importing into a new file did not do the trick! Have you had an opportunity to review this information on Unexpected or Erratic Behavior in SL2? You may find it beneficial to run through the repair steps listed.
If issues persist, you are welcome to share your file and I can attempt to publish it on my machine to see if I encounter the same behavior. If that is the case, I would then recommend that you reach out to our Support Engineers for further investigation of what may be causing the issue.
Thanks, Christie. I shared the file with the Support Engineers this morning and got a response around 9:30 stating that they are currently reviewing. I think that it is something problematic within the course because I was able to replicate the issue on a colleague's computer.
I appreciate the update, Erin and I see that your case (00686125) is being handled by our Support Engineer, Abel. I intend to follow along with the progress being made and will share updates here in the thread for others who may encounter a similar issue. :)
Thank you. Is there a progress update on the case? I really needed it published by 8 am this morning. Trying to keep my project team notified. Thanks!
Hi, Erin -- Thanks for touching base, and as cases are addressed in the order in which they are received, it appears that your case is still showing as being in the testing stage. Many thanks for your patience, as we work as quickly and efficiently as possible to provide all of our customers with the highest level of quality support. I reached out to Abel to let him know of your inquiry, and he will be in touch as soon as possible. :)
Hello again, Erin -- You will be hearing from Abel via email as well momentarily, but he just let me know that the "Print Results" button in slide 7.13 Results Slide is causing the crash. The customer will need to delete the button and just check the "Allow user to print results" button in Results Slide option for the button to recreate."
Please give that a shot, and reply to Abel's email if you find that you still need further assistance.
Thanks, Christie! I was able to publish the course now, but it is not functioning properly. I've contacted Abel for further assistance.
Thanks!
Hi, Erin -- So sorry to hear that issues persist, but I appreciate that you've shared an update, and I will continue to track the progress being made on your case. :)
I am having the same problem. Please help - due to the client this morning!
Hello Patrick - Sorry to hear that you ran into difficulty with this. I second Wendy's original suggestion and advise to attempt to import into a new file first to see if this alleviates the issue.
This discussion is closed. You can start a new discussion or contact Articulate Support.