Storyline 2 freezing when I try to Publish

Ashley,

"1. When you publish, are you including HTML5 and/or AMP output?" Usually yes. Most of our modules are published with HTML5 enabled.

"2. Does this occur regardless of the publishing target? i.e. web vs. LMS?" We don't know. We have not published any content to Web; everything under ASLv2 has been published to LMS.

"3. Are you working within a VM environment, such as Parallels or VMWare? If so, are you on a Mac or Windows system?" No. we am working on a PC (Windows 7 w/ IE 11).

The "freezing while publishing" issue happens all the time, but never more than once in a row. It is frustrating.

Thanks Patrick for sharing that information here - when you say never more than once in a row do you mean after your first attempt at publishing a file, if you try to publish that file again you're able to do so? 

Ashley, yes, that is what I mean. Other times, it will publish on first attempt, but crash on a follow-up attempt after edits are made. But, again, never more than once in a row.

Thanks Patrick - I wanted to clarify before sending that additional piece along to our QA team. 

I've been experiencing this issue for sometime now as well.  Hope a fix get's found. 

Hi Tracy, going back a few replies Ashley was asking for answers to a few questions to pass on to the QA team.

1. When you publish, are you including HTML5 and/or AMP output? 

2. Does this occur regardless of the publishing target? i.e. web vs. LMS? 

3. Are you working within a VM environment, such as Parallels or VMWare? If so, are you on a Mac or Windows system?

Can you provide Ashley with your answers? If there is anyone else that has previously reported this issue and still has the problem could you also reply with your answers as well.

Thanks Trevor - you beat me to it! 

Tracy, you're also welcome to connect with our support team if you'd prefer. But, you can share the info here as well and I'll pass along. 

1. When you publish, are you including HTML5 and/or AMP output?  - No, unless I have forgotten to uncheck it.

2. Does this occur regardless of the publishing target? i.e. web vs. LMS? - will continue to monitor for, but 95% of the time I am publising to LMS. Last occurance that happened today I was publishing to LMS.

I'll watch and try to track what other specifics occur (I click/set/etc) prior to me clicking that publish button.

3. Are you working within a VM environment, such as Parallels or VMWare? If so, are you on a Mac or Windows system? - Nope. Windows 7 Enterprise, 64 bit, desktop, publishing to C: drive

Thanks

Thanks Tracy for sharing that here - and I've included this info for our QA team. 

I can't find any consistencies, it doesn't matter what I select, it can freeze.

I hope this helps, Kim.

Kim Gillham MEd, Dip eLearning, Dip Bus (Project Management), Adv Dip Bus, Cert IV TAE
Learning Experience Designer / Information Architecture Consultant
Office: (07) 5467 9652
Mobile: (0433) 431 281
Email: kgillham@visumation.com.au
Web: www.visumation.com.au

Hi Kim,

First off, when you reply via email your signature is included here in the forums so you're welcome to edit your post to remove that information if you'd like. 

We're trying to gather more information about when or how this happens, so if you haven't been able to determine any of the elements in the questions that Trevor shared again or that Tracy answered - can you confirm that you're already gone through the normal repair steps as documented here? 

Hi Kim, As a matter of interest what operating system are you using e.g. Windows 7 etc. 
Trevor

Sent from Samsung Mobile

I am having the same issue - my co-worker and I just started using SL2 in the past month and we are both experiencing the freezing while publishing issue. I am also having issues with saving...it takes an incredibly long time to save my files. AW

Hi Annie,

Are you  using the latest update of Storyline, update 4? That helped with a lot of the saving issues other users were mentioning here in the forums. In regards to the freeze while publishing (and your saving issues) have you gone through the repair steps detailed here and confirmed you're working with all local project files. 

If you've gone through those, can you provide more information about what you encounter while publishing? And answer these questions:

1. When you publish, are you including HTML5 and/or AMP output?
2. Does this occur regardless of the publishing target? i.e. web vs. LMS?
3. Are you working within a VM environment, such as Parallels or VMWare? If so, are you on a Mac or Windows system? 

I have the same issue (I believe only since update 4, but I didn't publish much under update 3).

I'm in Windows 7 and was publishing to web without HTML5 or AMP.  No to VM or anything, and I always work with local files.  I do the whole task manager kill and restart as Richard explained which alows me to publish as expected, but publishing again after making some changes usually results in a repeat of the same issue.

Thanks Josh for sharing that here - it seems that Windows 7 is a common denominator here, so we've shared that element with our team. 

Ashley,

another common denominator is that we all experience the same when we got the freezing (which is actually not a freezing):

1. Quit via task manager
2. Start Storyline and open file
3. Publish again does always work

4. When chaning something again, sometimes it works, sometimes not. Unpredictable.

I just experienced these steps. Published to a new location. Worked. Next changed something, like deleting a slide and save. Republish -> Problem again. Steps Above. Worked. Changed something and savend. Republish -> no problem.

Does the problem ever occur when you do a fresh first time publication? I can't remember that.

Hi Sjoerd,

Thanks for continuing to update us. I think a few users here mentioned running into the issue when doing a first time publication - but this thread has definitely gotten long and hard to remember all the specifics! :-)

I keep sharing the information with our team though as they continue to investigate. 

Hi Ashley,

Yes I know it might be posted before. I just try to find some logical behind it.

This issue sure give you a lot of work as well.

For those interested, I've found a workaround (for me) for the publishing issue:

1. Open storyline and edit
2. Save file and close
3. Reopen file and publish

This works for me every-time, I don't edit then publish- ever now it wastes too much time. So if I edit, I close the file and reopen before I publish.

Hope it works for you too.

Enjoy your day, Kim. :-)

Thanks Kim for sharing your workaround here. Our team is still investigating this issue, and if you're able to consistently reproduce the issue we'd like to have you talk with them directly and show the steps your going through on your system. If you're able to connect with our Support team, please do so here and let them know about this thread. 

I see this thread is extremely long but I wanted to see if there was a solution yet.

We are having the same issue, so far with only one developer. She has the problem with a new S2, an updated S1 to S2, and an existing S2 when publishing. Some Storylines she created and some were created by other developers.

We only publish to HTML5 (never AMP). Our developers only work locally and all use Windows 7 (a few 64-bit and a few 32-bit) in a non-virtual environment. We do not publish for LMS.

We have tried uninstalling and repairing Storyline but it still does not work. Also, she is running the latest update, downloaded yesterday (03/05/2015).

Hi Kim,

We don't have a solution yet, as our team is continuing to investigate this and look for users who are able to consistently reproduce it as I previously mentioned. Since it sounds like one of your developers can see the behavior regularly, we'd like to have her work directly with our support engineers so that we could gather more information about what's occurring and how she's able to reproduce it so that our team can track this down further.

Please have her reach out to our team here and reference this thread. 

I'm happy to report that this hasn't happened to me for a while now, approximately 2 weeks.  I admit this is just a guess, but the only thing that I can think that has changed recently on my computer that might explain this is that I recently updated my version of the Flash Player. I'm currently on the newest version: 16.0.0.305. I know that Articulate relies on having the Flash Player installed, but have no idea if this could possibly be something involved in the publishing process.

You can see what  version of Flash you are on here: https://www.adobe.com/software/flash/about/