Skip to main content

Does anyone know why this error message and issue is occuring. I had recently updated Articulate to their newer version and this error started occuring when I had overwritten the Scorm. I have rolled back Articulate and republished the course to LMS scorm but it is still happening even when not overwriting a course but when adding as a new scorm and assigning to a new course. Thanks

 

@ChristineW Hi, Christine … are you still having issues? Did you find a solution? Where are you in Docebo when you get this error?

Here’s some troubleshooting ideas that I use with Articulate:

  • Cleared Temporary files for Articulate and Windows (assuming a PC here)
  • Check the published .zip file up on Scorm.com to just confirm that the .story file has published correctly.
  • Checked the e-Learning Heroes community from Articulate? If it’s related to a new update, there might be others.
  • Renaming the .story file to a new file name and/or coping the scenes to a new .story file

Good luck!  Would love to hear the solution.

 


@KMallette Hi the error occured when I launch the course in the LMS. It would play but with no communication between the Scorm and LMS and so it wasn’t tracking any progress and returning to the start every time I accessed the course.

Yes I cleared the temporary files but this didn’t resolve the issue. The Scorm was tested in ScormCloud and worked fine. The trouble with renaming the .story file or copying scenes to a new .story would most likely mean I couldn’t overwrite the previous version on Docebo which is what I wanted to do, although the versioning didn’t work either even though I didn’t change the course structure. Although the renaming of the file or copying to another .story was going to be my last resort if all else failed.

Good idea on checking the e-Learning heroes community again, which I’ll do.

In the end I rolled back the Storyline version to the November 28 version build and it works fine again but have the black screen appear at the start still now which we’d resolved previously with a fake start screen.


@ChristineW Thanks for the follow up.  I’ll watch out for the issue when we publish.


We now seem to have resolved this with a further Articulate Storyline update.


Reply