Cannot publish or preview after re-saving

Jul 22, 2013

Have started a new post as the issues I'm getting crop up in several others.  Here's the problem:

I produced 70 modules last year using a Win 7 machine.  We used the Storyline characters and the customer now wants a refresh of all 70 using photos of real people.  I'm now on a Win 8 machine. All the files OPEN OK and I can edit and publish them without problems.  However as corrections are coming back I have realised that whilst I can now open all the modified files, I cannot preview or publish them after they've been re-saved once.  If I try to access the template I get the dreaded LOW MEMORY message.  If I try to preview, it sticks on the last slide.  If I try to publish, it appears to go through the motions then returns to the publish screen.

Apart from swapping out the characters, the only other change requested is to swap the menu from the left to the right.   Anyone had issues with this?

Here's what I've tried so far:

  1. Opened old copies and tested by removing slides etc - No effect
  2. Did a system restore with no effect.
  3. Deleted and reinstalled Flash player - no effect.
  4. Did a repair installation of Storyline - no effect.
  5. Bit the bullet and did a full re-install (using the registry clear file supplied).  BINGO - I could preview and publish files again.

However, as soon as I save them I'm back to square one.  I'm on a deadline so panic is setting in.  Any thoughts and suggestions gratefully received.   I can only recover the work by copying and pasting the whole thing into a new file and re-publishing but this is painful as most have complex links and multiple scenes.  This works - incremental saves are fine but as soon as I close and re-open it's back to square one!

5 Replies
Justin Grenier

Good Afternoon, Paul.

We've seen issues like you describe when the player contains an invalid logo image.  If you can please share one or two of your .story project files with us, we should be able to confirm whether or not this is the case.  If this is the root cause, we may have a work-around for you, but we need to confirm it by taking a look at your files first.

Please send them over and we'll take a look.  Thanks!

Paul Wolstencroft

Hi Justin,

Wish I posted this sooner.  I just experimented with removing the logo and for the first few files I've tried it seems to work.  Great tip, thanks.

If it works for all of them, that's yet another gold star for the Storyline team!

Before I put a new logo file back - Two Questions:

  1. What do you consider to be an 'invalid' logo image?
  2. Is it possible to remove an offending image from a template file?  (Bearing in mind that I now have several large publications in which I can't access the player template.)

If I get stuck I'll send you over a bunch of files.

Justin Grenier

Good Morning, Paul.

In most cases, when examining similar files internally, we have found that the logo image is missing.  If you'd like us to examine a couple of your files internally, we'd be happy to receive them.  If we verify that we can consistently repair them using internal tools, we may have a work-around for you, but we need to confirm it by taking a look at your files first.  Thanks!

Paul Wolstencroft

Hi Justin,

After a lot of experimenting and numerous permutations, we've worked out that it WAS a logo file as you hinted at.  Originally, we'd been using the logo file supplied by our client.  This was an 8 bit palatted PNG image.  We re-saved this as an RGB 24 bit image and the issue disappeared!  We replaced the logo on published versions but substituting the swf file.  Seems to work.

Interesting though that this could cause such a major issue, which I notice appears in other posts.  Really great to know that you're prepared to looked at individual files.  I think we survived this time but if you're interested, a proof version (uncorrected) of module 24 of 70 is at www.consult.pw/dya  (Back to a very basic player template as part of the testing!)

Thanks again for the really speedy response.

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