I have a feeling this question might be better answered by our LMS, but I thought I'd try here too.
I have a course built in Storyline that won't play in our LMS if it's published in SCORM 2004. It just says "Loading content...please wait." However, if I publish in SCORM 1.2 everything works fine.
Has anyone run into this before and do they have any suggestions for what I might do to resolve this?
The strange thing is that I posted a course built in Articulate Studio with SCORM 2004 and it worked just fine. It seems to be Storyline that isn't working.
I'd test the course at SCORM Cloud, as it's an industry standard testing method for SCORM Content, and if it works there then you'll want to connect with your LMS team. If it doesn't work there, let us know.
I tried uploading to Scorm Cloud and it worked there. The strange thing is that I tested another Storyline course on our LMS with the same settings, and that worked. Could it be that my file has gotten corrupted somehow?
I'm going to try to rebuild it quickly tomorrow and see if that fixes it.
If it worked on SCORM Cloud, I wouldn't suspect it to be a corruption issue - but there could have been some issue that occurred when uploading it to your LMS. To start out fresh, I'd recommend deleting the original version from your LMS and then take the original .story file and import into a new project as described here. Then you'll want to upload that version to the LMS and see how it behaves.
I actually tried several times with different versions. Each time had the same result.
This morning I created a new project file and copied and pasted all my slides into that one, sort of like what you recommended except I did things manually. I wish I'd seen your suggestion earlier. Anyway, it seemed to do the trick. Thanks!
Glad that everything is back to normal now, and if you run into it again, the import is actually known to behave better than copy/paste which can sometimes lose images or audio.
Hi again! Someone else within my organization experienced a similar issue. However, this time she claimed that changing the Java settings on her computer allowed her to view the course in the LMS with no problems. Specifically, she had to go into her computer's Control Panel and either changing the Java Security Level to Medium (rather than High or Very High) or by adding the URL to the Exception List.
We obviously can't have potentially thousands of learners running into the same issue, but I know that suggesting security changes on all company computers to our IT department will be met with major resistance.
So my question is, is there anything that can be done from within the Storyline project to overcome this issue (perhaps including some kind of Javascript in the course)? I'm not very familiar with Java, so I'm hoping someone here might have some suggestions.
Unfortunately I'm not equipped to assist with Javascript, but it sounds like this is a browser setting your describing, so as far as I know, there wouldn't be a way to control it from Storyline.
9 Replies
Does your LMS support scorn 2004?
You can test your package in Scormcloud to see if has a problem, apart from that it is probably something that needs taking up with your LMS
The strange thing is that I posted a course built in Articulate Studio with SCORM 2004 and it worked just fine. It seems to be Storyline that isn't working.
Hi Arend,
I'd test the course at SCORM Cloud, as it's an industry standard testing method for SCORM Content, and if it works there then you'll want to connect with your LMS team. If it doesn't work there, let us know.
Hi Ashley,
I tried uploading to Scorm Cloud and it worked there. The strange thing is that I tested another Storyline course on our LMS with the same settings, and that worked. Could it be that my file has gotten corrupted somehow?
I'm going to try to rebuild it quickly tomorrow and see if that fixes it.
Hi Arend,
If it worked on SCORM Cloud, I wouldn't suspect it to be a corruption issue - but there could have been some issue that occurred when uploading it to your LMS. To start out fresh, I'd recommend deleting the original version from your LMS and then take the original .story file and import into a new project as described here. Then you'll want to upload that version to the LMS and see how it behaves.
Hi again Ashley,
I actually tried several times with different versions. Each time had the same result.
This morning I created a new project file and copied and pasted all my slides into that one, sort of like what you recommended except I did things manually. I wish I'd seen your suggestion earlier. Anyway, it seemed to do the trick. Thanks!
Hi Arend,
Glad that everything is back to normal now, and if you run into it again, the import is actually known to behave better than copy/paste which can sometimes lose images or audio.
Let us know if you need anything else!
Hi again! Someone else within my organization experienced a similar issue. However, this time she claimed that changing the Java settings on her computer allowed her to view the course in the LMS with no problems. Specifically, she had to go into her computer's Control Panel and either changing the Java Security Level to Medium (rather than High or Very High) or by adding the URL to the Exception List.
We obviously can't have potentially thousands of learners running into the same issue, but I know that suggesting security changes on all company computers to our IT department will be met with major resistance.
So my question is, is there anything that can be done from within the Storyline project to overcome this issue (perhaps including some kind of Javascript in the course)? I'm not very familiar with Java, so I'm hoping someone here might have some suggestions.
Hi Arend,
Unfortunately I'm not equipped to assist with Javascript, but it sounds like this is a browser setting your describing, so as far as I know, there wouldn't be a way to control it from Storyline.
This discussion is closed. You can start a new discussion or contact Articulate Support.