Forum Discussion
Publishing failed — LMS SCORM and Review 360
Hello,
Since yesterday, I have been unable to publish my Storyline 360 project.
The issue occurs in both cases:
- Publishing for LMS using SCORM
- Publishing to Review 360
I receive the following error message:
Something went wrong.
Storyline 360 encountered an error while trying to publish the project.
The troubleshooting message says that Storyline 360 cannot find a temporary file located in:
C:\Users\[username]\AppData\Local\Temp\Articulate\Storyline\...\story_content\...\stream_1data000013.ts
It says the file may have been moved, renamed, or deleted.
I have tried publishing again, but the same error keeps appearing. This started only yesterday.
Has anyone experienced this issue before, or could you advise what I should check? Could this be related to temporary files, antivirus software, or a recent Storyline 360 update?
Thank you for your help.
Thank you for your suggestion.
Strangely, everything started working again overnight. I tried publishing the project again using my original method and settings, including adaptive video compression, and the project published successfully without any further changes.
I am therefore not sure what caused the issue or why it resolved itself so suddenly. It may have been related to temporary files, but the error message did not make the cause very clear.
Thank you again for your help.
11 Replies
".ts" is the extension for a type of MPEG encoded video file. It's likely to relate to a video file you have embedded in your course. See if all the videos will play in preview.
Hi CarlFink1
Thank you for your reply.
I checked the project carefully, and I don’t have any media file with a .ts extension in the Storyline project. All the videos are .mp4 files.
I also tested the course in local preview/review mode, and the videos play correctly there. The issue only happens during publishing, both for LMS/SCORM and Review 360.
Could the .ts file mentioned in the error message be a temporary file generated by Storyline during the publishing process? I’m wondering whether it could be deleted or blocked by Windows, antivirus software, or a recent Storyline update while publishing.
Thanks again for your help.
The fix that I proposed should fix your problem
Change video compression to static instead of adaptive when publishing... the .ts file is a temporary file created during encoding of adaptive video...
Hi DShaw
Thank you, that seems to be the issue.
I changed the video compression setting from adaptive to static/fixed, and the project now exports correctly.
However, I still don’t fully understand why this suddenly started happening, because the same adaptive video compression setting worked perfectly on my previous Storyline projects.
Could this be linked to a recent Storyline 360 update, or to a change in how temporary .ts files are generated during publishing?
Thanks again for the explanation.
Hi DShaw
Thank you, that seems to be the issue.
I changed the video compression setting from adaptive to static/fixed, and the project now exports correctly.
However, I still don’t fully understand why this suddenly started happening, because the same adaptive video compression setting worked perfectly on my previous Storyline projects.
Could this be linked to a recent Storyline 360 update, or to a change in how temporary .ts files are generated during publishing?
Thanks again for the explanation.
It could be a number of things only related to this particular project. Very large video files in a project can create very large temp file sizes when encoding with adaptive compression setting. This can cause issues... looking at the error you had this would seem to be the case...
Thank you, that makes sense.
For now, exporting with static/fixed video compression solves the problem.
However, I also noticed that some older projects, which I was previously able to export successfully using adaptive video compression, can no longer be exported with that setting today. So it does not seem to be limited only to this new project.
Thanks again for clarifying what the temporary .ts file is and why it may fail during encoding.
