Articulate Presenter 13 has stopped working - Audio Editor Crashes and how I fixed this particular problem

Everyone,

One of our trainers sent me a 10 slide Articulate presentation with audio that she could open, but not go into the Audio Editor.  When she tried going into the Audio Editor, it gave the error message below;

The text of the error was this;

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: Articulate.Presenter.exe
Problem Signature 02: 7.7.1509.1618
Problem Signature 03: 55f9bd8d
Problem Signature 04: System.Windows.Forms
Problem Signature 05: 4.0.30319.34251
Problem Signature 06: 54daee67
Problem Signature 07: 93a
Problem Signature 08: 142
Problem Signature 09: System.ObjectDisposedException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

After a few google searches everything pointed to uninstalling Articulate Studio and Office 2010 and reinstalling.  I did not have the time, energy, or admin rights to do this, so i figured if it was happening on multiple machines (hers and mine) it had more to do with the presentation than the install.

I was able to open the presentation and then open the Import Audio screen from the Articulate tab.  Once in there I noticed that the audio file names were longer than I liked and could potentially be causing the error I was seeing.  I exported the audio files out, saving them with a simple "slide 1,2,3..." file name. I then removed the audio from the presentation, saved and closed the presentation.

I reopened the presentation and was able to successfully open the Audio Editor with no errors.  I re-imported all the audio files I had saved with the shorter file names and then saved and closed the presentation one more time.  Upon re-opening the presentation I was able to go in and out of the Audio editor with no issues.

I don't know if this is a bug in Articulate in how it handles long file names or what, but this process saved my trainer from having to recreate the entire presentation.  Hope this helps someone else and sorry for the long post.

Scott

2 Replies
Christie Pollick

Many thanks for sharing, Scott, and in addition to the information you've shared, I also wanted to provide the following troubleshooting options for others who may come across this thread seeking assistance:

Unexpected or Erratic Behavior in Presenter '13 

How to Fix a Corrupt PowerPoint File 

How to Repair Studio '13 

We appreciate your help! :)