Storyline 3 crash/error during publishing

I've discovered that this seems to be caused by the browser (Firefox in this case) locking some files in the published output. Storyline is unable to overwrite the files when re-publishing because the browser has them locked. The simple solution is to close that browser tab before re-publishing. This could be caused in part by my publishing to a network drive, but it's really not practical to work locally.

8 Replies
Ashley Terwilliger

Hi Michael,

I haven't heard of this behavior in Storyline 3 with Firefox - but we do always recommend publishing and editing files locally. Once you've published them you can move them to a network or shared drive by zipping the files and then copying to the network drive.

If you'd like our team to take a look at the crash/error logs we're always  happy to do so! Reach our to our Support Engineers here and they'll provide you with next steps. 

yiu alex chun yip

問題事件名稱: APPCRASH
應用程式名稱: Storyline.exe
應用程式版本: 3.1.12115.0
應用程式時間戳記: 59388281
錯誤模組名稱: MSVCR120_CLR0400.dll
錯誤模組版本: 12.0.52398.36398
錯誤模組時間戳記: 58fec95a
例外狀況代碼: c0000005
例外狀況位移: 0000137a
作業系統版本: 6.1.7601.2.1.0.256.48
地區設定識別碼: 3076
其他資訊 1: 0a9e
其他資訊 2: 0a9e372d3b4ad19135b953a78882e789
其他資訊 3: 0a9e
其他資訊 4: 0a9e372d3b4ad19135b953a78882e789

Sheila Y

Hooray! Michael, thank you so much for this information. I'm still using Storyline 2, but this resolved my publishing issue. In my case, I would publish the file once, and then click the View Project button to view the output. It would launch in Firefox, and then I'd notice some detail that I needed to change. After saving the changes, I'd publish again, and then the crash would happen. Now I know to close the browser before republishing, and it's made a world of difference. :)

Mara Cain

Thank you Michael for figuring this out! I publish locally, but ran into the same issue with IE and was completely upset at having to change the folder to republish after even an small edit. Now, when I close the browser tab, it works beautifully to republish! BTW, I've sent the error logs multiple times when I received them and didn't get any response, so I'm glad to have a fix.

Katie (Gokhshteyn) Riggio

Woo-hoo, glad to hear Michael's suggestion helped! While I haven't heard of this browser behavior, I will certainly circle back with any new insight.

I also wanted to apologize for the trouble, Mara! The error report generates logs for our product team to help them investigate potential bugs. I'm really sorry if the verbiage of that message was confusing.

If anyone runs into this oddity again, please let us know. We're happy to dig into those error logs and let you know what we find in the backend!