Forum Discussion
Articulate Storyline Publishing to Review - 'Something Went Wrong' Error Message
I've been attempting to publish to review an Articulate Storyline containing several MP4 files. Unfortunately, when I go to publish to review I get this pop up notification. I suspected that this was occurring because the MP4 file was originally stored on my personal drive before being imported into Storyline but had then been deleted.
However, when I try to delete the videos and reimport them from SharePoint (where they will not be moved, renamed or deleted), I still receive this error message.
My colleagues who have their own Articulate licenses are however able to publish to review my Storyline file once, but when they go to do it a second time they also receive the same error message.
Has anyone come across this before and how did they fix it?
So far I have tried the following troubleshooting but with no luck:
- Ensuring the blank Storyline file is automatically saved to SharePoint and never lives on a local drive
- Importing MP4 files from a shared space rather than a local drive
- Opening the Storyline file through both SharePoint online & SharePoint via files navigation
The .ts file that is calling the error is a temp file type created when adaptive encoding… switching to static/fixed encoding should fix the issue…
6 Replies
Change the video encoding to static when publishing. That should fix it
This happened to me last week. I was told to open a new blank Storyline file and import all the slides from the affected file over to the new one. That worked, however I do not use Sharepoint when working in Storyline.
The .ts file that is calling the error is a temp file type created when adaptive encoding… switching to static/fixed encoding should fix the issue…
This has worked - thank you :)
I have the error message come up for me when I try to publish to review -- but there is no message on what I can do to fix. This is very frustrating. I try over and over and sometimes it works.
Hey TracyWindsor-96,
So sorry to hear that you're having trouble publishing from Storyline to Review.
Since the behavior is intermittent, can you confirm that the .story file is stored on your local hard drive while editing and publishing? Authoring directly from a network drive may introduce unexpected behavior such as this.
It would also be helpful to know whether the failure occurs with other projects, or only this one. If the behavior is widespread, does the error pop up at roughly the same point each time?
If you're comfortable sharing the affected project file, we're happy to take a closer look and test it on our end. Feel free to upload the .story file here in the discussion or through a support case.
