Storyline will not publish or preview project

Aug 09, 2013

I cannont publish to any format except for Word. When I click publish, the progress screen briefly appears (for a second or two) but then Storyline reverts back to the Publish screen, instead of giving me the View, Zip, etc. screen

When I try to preview the project, it hangs up on loading screen two.

Any help is appreciated.


14 Replies
Ashley Terwilliger-Pollard

Hi Emily,

Thanks for the clarification. Some additional thoughts for troubleshooting:

  • Have you tried to publish to anything other than your LMS, and it still won't work, such as publish to CD? If you're able to publish in other ways, just not your LMS - you may also want to try publishing in SCORMCloud to see if it's something with Storyline or with the LMS you're publishing too.  
  • Is this happening with every file, or just a specific one? You could try to import the file into a new Storyline file and then publish.
  • It definitely doesn't sound like normal Storyline behavior, so you may need to conduct a repair of your Storyline software.   
Emily Moroz


Thanks for your input. It's just a bit odd since this is the only file that won't publish, the other 9 I uploaded worked perfectly. Our files are downloaded to an external website that only excepts lms, otherwise I would try a different source. I'll try importing the file into another Storyline file and see if that helps.

Thanks for your help and quick response!

Ashley Terwilliger-Pollard

Hi Emily,

If it's one file, definitely try to import it into a new Storyline project. Sometimes file can become corrupted and cause random issues such as this. Some things to consider to prevent future corrupted files: 

  • Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior. 
  • You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
  • Avoid using special characters, accents or symbols in your file names (this includes spaces and underscores).
  • Scott Muth

    I am having a similar problem.  My module does publish to Word.  i have tried publishing to Web, Articulate Online and LMS with no success.

    I tried rebuilding the module scene by scene with no success.  Then I tried to rebuild slide by slide.  My Intro scene worked fine, but the following scenes crashed the module on preview and publishing.

    I superstitiously feared that the Korean script I am using may be a problem.  That cannot be the problem.

    My raw file is attached.  Please advise.

    Thank You

    Scott Muth

    I installed update 8 as well and still had trouble publishing. However, as
    I was playing with recreating the project with images, the problem

    I noticed that some of my slide names were using Korean script. I changed
    the slide names to English, saved the file and was able to publish.

    Thank you for the quick response.

    Scott A Muth[image: Slide Name Discrepancy.png]

    Ashley Terwilliger-Pollard

    Hm, I didn't run into any issues with the Korean Script on the slide names for my version - were you able to open it and take a look? I didn't change anything associated with your .story file, just opened and published to my local drive. Did you look to see if you had any Korean characters in the file name or path? Did you check that you were adhering to the other guidelines mentioned above in terms of publishing locally with a short file path? 

    Scott Muth

    I am working in my local drive. My course title does include Korean

    My path is quite long:

    C:\Users\Scott\Documents\My Articulate Projects\Johnson & Johnson\The
    Concourse Program\4 Korean

    I therefore do have a few items against successful publishing.

    Part of me feels that my discovery may be superstitious, but it did work
    for me. It could be all that I needed to do was save the file after the
    software update and try again.

    Thank you again for your fast response.


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