Forum Discussion
Storyline 360 Crashes when Publishing to SCORM and Review
I have two project files that crash when I attempt to publish. Storyline (v3.108.36078.0) crashes (closes) without warning or error message. The failure happens during the 'Preparing to create slides' phase of the process. I can publish other projects with no issue. Preview works fine, so it's tough to figure out which element(s) is the cause.
Here's what I've done (twice) with no change:
- Uninstalled all Articulate apps.
- Rebooted
- Ran 360Cleanup batch file as Admin
- Rebooted
- Installed Articulate client app
- Installed Storyline 360 x64 (only)
- Rebooted
- Imported slides from problem project into new project
- Saved new project with new name
- Attempted to publish
- Storyline crashes without warning or message
Hey Mike,
It sounds like you have done quite a bit of troubleshooting. I am sorry you have not reached a solution. One thing I did not see in your list was "Submit a Case" - I think that should be your next step.
https://articulate.com/support/contact/case
Also, can you confirm that you are installing and working from your local C Drive?
4 Replies
Hey Mike,
It sounds like you have done quite a bit of troubleshooting. I am sorry you have not reached a solution. One thing I did not see in your list was "Submit a Case" - I think that should be your next step.
https://articulate.com/support/contact/case
Also, can you confirm that you are installing and working from your local C Drive?
..and I've submitted a case to Articulate :)
Hello MikeAnderson-27,
I'm glad RonPrice recommended reaching out to us in a case! I see that you're currently working with my colleague Phil. You're in excellent hands!
We'll continue the conversation over in your case, so everything is in one spot!
Outcome... I was finally able to publish both of the corrupted modules using a previous version of Storyline and the projects files. It appears that there was some corruption in several (10+) of the AI TTS elements. Still no cause, but if you run into something like this, look at the timeline for irregularities (see image). Replacing the audio solved the problem.
