Publishing fail on one PC, but not another for the same source file

Hi, all. Need some advice for a fix.

I passed off a source file to another developer also on Storyline 2 Update 6 (both PCs using Win7 64-bit). I do NOT get this error report upon publishing, but she does:

http://i.imgur.com/o25mMVp.jpg

We believe it's one particular slide that is the issue. It's nothing complicated (just changing text object states against cue points). I made a new slide (and deleted the old one) to no avail.

I've seen this happen on another project, to which I passed the source file to another PC of mine with Storyline and published with no issue (with no understanding why it happened in the first place on the first PC). I'd like to believe it's Storyline just being Storyline but there has to be some reason and a real fix that doesn't involving hot-potating the source file to another workstation.

 

3 Replies
Ashley Terwilliger

Hi Stevie,

Sorry to hear about the error message you're running into. You mentioned you think it's one particular slide - is that based on where it stops publishing and you can see that's the slide number it was last referring to? How are you sharing files back and forth across the PCs? You'll want to confirm you're working on local project files and then following the steps here to collaborate on files. 

You'll also want to make sure that you're both using the same update of Storyline, we're currently on Update 6 of Storyline 2. 

Stevie V

We're working locally after pulling from a shared folder (similar to a Dropbox desktop app). I can't recall how she determined that slide was the culprit but she knows her stuff quite well I assure you.

And yes we are using the same version as mentioned prior.

She tried sending to another Developer and that person had no issue either with publishing like myself. Seems to be isolated to one user.

Ashley Terwilliger

Hi Stevie,

If it's just one particular user, I'd also have them look at conducting the repair process as detailed here as well. If you've isolated it to one particular slide, but recreating it didn't solve the problem I'd look at what other assets were on that slide such as images or media elements that could be causing the corruption.