Storyline 2 Crashes When Trying to Publish to LMS

Thanks Emily,

Gotcha "covered" on your first two points.

I guess the last alternative is the registry clean and SL2 reinstall...fun.

Hello Frank!

Let us know if the repair of Storyline works.

Hi, Frank!

Articulate has a clean-up tool for the registry.  See this:  http://www.articulate.com/support/storyline-2/unexpected-or-erratic-behavior-in-articulate-storyline-2

I have had two instances already where Storyline 2 crashes when trying to publish to Articulate on-line. It simply freezes and you have to close it down in task manager. If you then re-open AS-2 and the attendant file, it then publishes correctly. I cannot find any obvious reason for this annoying behaviour that was never seen with AS-1

Hello Alan, and welcome to Heroes!

Have you tried the steps in the link provided above to see if this corrects your issue?

Hi everyone, 

Just FYI - I was having the same issue where i would click the Publish button and Storyline 2 would completely lock up. So, I upgraded to Microsoft .NET Framework 4.5 and that seems to have helped me - so far anyway!!  Instructions are in the link that Emily provided. Just thought I'd share. 

Have a great week!!

Tracy

Hello Tracy!

Thanks for sharing your update.

I am consistently seeing this problem the first time I publish after a reboot. Publish works OK after I kill SL from task manager, then restart. Same thing happens whether it's publish to web, LMS, or Word.

I am evaluating SL2 for a large corporate rollout and honestly, this is a potential show-stopper for us. Many of our users have locked-down computers and cannot run as administrator, install apps, clean their own registries, etc - doing so will require hands-on tech support. 

Are there any plans to resolve this bugginess in future releases? 

Hello Mark!

Are you seeing this on all of your files or just one in particular?

Typically running the steps listed above does resolve the issue. If you continue to see this, you could reach out to our Support team to see if they may have some other suggestions.

It's inconsistent. I've seen it in a couple instances, with a couple different files, but I can't always replicate it. The issue is not really about me being able to solve the problem - I can likely do that with the fixes recommended because I am in the minority that have control of their computers. The majority of our Storyline users do not have such control, so they would have to have our tech support do it.

I will note this as something to further test once we get more people involved in our testing cycles. Given that I'm not the only one reporting it, I was hoping it might be a bug that would be fixed in an upcoming release.

Mark Williams
Senior Instructional Design Specialist
Learning & Development
Liberty Mutual Insurance
Mark.williams@libertymutual.com | 253-509-9176

Hi,

You can add five more SL2 users to the list. we're experiencing the same crash/task manager fix/cross your fingers/republish issue.

It occurs on five separate work stations (installed to C) across multiple files about 50% of the time and as with Mark's post above we're in a similar situation to his team and don't have admin rights to run any registry hacks or reinstalls due to being on a large corporate network.

As we and other posters didn't have this issue when publishing through SL1 would it safe to assume there is a bug fix in the not too distant future?

Thanks in advance
Mark        

Hi Mark, 

Are you able to pull the error logs as described here? This will help our team isolate the issue further and look into what may be interfering with the publish.  There are directions there on how to upload the logs to our Support team. 

Hi Ashley, thanks for your response,

With regards to the error log, I'd have to log a job with our IT department to run it as it also requires admin rights. Just to note this will dependant on approval and may take some time.

I'm not over optimistic that the error log will contain anything relevant for your team other than the end task event (at best) given that the program just hangs and no visible error is reported. 

On a lighter note: myself and a colleague were able to save and publish to our local drives 5 times (presumably more) without issue.

This is a good result in the interim as it provides us with some publishing consistency, however this work-around is against our company policy as there is no automated network backup of our files and doesn't easily cater for multiple developers contributing to courses.

I think it's important to note that there has been no changes to our network and this issue has only occurred since upgrading to SL2 and we were able to publish to the corporate network in SL1 without issue.

Thanks in advance,

Mark

Hello Mark,

Thanks for the update. I am glad to see that publishing to the local drive has worked. This is the manner in which we always recommend to work from and publish files with Articulate products. If you do need to work with the files in a network environment, we recommend to follow the steps here.

If you can get the error logs from your IT, it would be helpful to send to the support team, as any information you can provide could help isolate the issue.

Hi Emily,

Oh my bad... I wasn't aware that saving/publishing to a network drive wasn't the recommended way, guess SL1's previous compatibility with our network environment lulled me into a false sense of confidence:)

Tom's article on MS Sync Toy looks like it could be a viable solution for our stable publishing and network backup requirements but once again this will be dependent on approval.

Thanks for your help with this Emily & Ashley, you guys have great support and SL2 is such a pleasure to work with!

Cheers,
Mark

I wouldn't say this is a resolved issue. I had the same issues when publishing locally. I didn't get time to go beyond initial testing and won't likely get back to it until January, but this is high on my list of things to needs to be resolved before I can sign off on rolling out SL2 to our corporate users. 

Thanks Mark L, and hopefully you can get approval to work locally.

Mark W, have you tried the repair steps listed here?

I have not yet done those steps. When I get back to testing, I will try those on another machine. Repairing my own machine does not really resolve the problem, since  many of our 80+ users will not be able to do those repairs on their own computers. Maybe there will be a fixed version before I get back to it (?)

I have been experiencing this issue as well. I've had to restart storyline at least 6 times today. I am publishing to my C drive. When you click publish, sometimes it works, sometimes it just freezes. I agree with the 50% comments above. I will look through the links above and see if anything there helps!

Deborah and Mark,

Our team is actively looking into an issue in regards to the publish freezing or crashing, and if you're able to consistently replicate this behavior we'll want to have you connect with our Support team so that we can gather some more details and specifics. 

Adding to the 50% of the time comments.  It's a toss up whether publish will actually work without crashing.

Hi Joe,

Our team is continuing to investigate this issue, so we're happy to take a look at your behavior too. You can reach out to our Support engineers here. 

Hi Ashley, has there been any progress with your team investigating this issue?

Unfortunately myself and my colleagues are still experiencing this issue about 50% of the time and it's somewhat frustrating to say the least.  

Hi Mark! Looks like I just responded to your similar question here.