Hello, folks! I wondered if anyone has encountered this problem.
We are using a Learnshare LMS. For _some_ (not all) of our students, when they try to access our Storyline course, they see the error "Data downloaded, connection closed". We can reset their enrollment in the LMS to fix the problem and let them access the course.
We have over 300 enrollees, and it would be nice to nip this in the bud. The best I can tell is that it's a SCORM player issue. Our LMS uses SCORM 1.2 (2004 doesn't work). Does anyone know if Storyline has any issues playing nicely with a Learnshare LMS or SCORM 1.2, and what we might be able to do about it if so?
I'd appreciate any help or suggestions. Thanks so much!
If resetting their enrollment within the LMS corrects the issue, it sounds like it something that Learnshare should investigate. Have you reached out to them to see if there are any known issues that may result in that error?
I don't personally have access to this LMS, but it sounds like it's specific to learner accounts. It probably wouldn't hurt to have them take a look at an account that's currently experiencing this issue.
It's peculiar that it only seems to be affecting our Storyline module, but we have hundreds of enrollments, so maybe the problem is only more visible there.
Additionally, a useful tool for deciphering the communication between your Storyline content and your LMS is to enable LMS Debug Mode. If you can provide the resulting LMS debug log to Learnshare, they should be able to nail down what's happening.
Anyone know if this issue is fixed? And does the error happen with Rise courses? I’m hoping to purchase an Articulate license at my new job and they use LearnShare...
We haven't identified anything within Storyline or Rise 360 that could lead to that error in LearnShare, but we're happy to explore further!
The best way to pinpoint the cause of this problem is to upload the published output in another LMS environment. We like to use SCORM Cloud since it's industry-standard:
8 Replies
Hi Marie,
If resetting their enrollment within the LMS corrects the issue, it sounds like it something that Learnshare should investigate. Have you reached out to them to see if there are any known issues that may result in that error?
I don't personally have access to this LMS, but it sounds like it's specific to learner accounts. It probably wouldn't hurt to have them take a look at an account that's currently experiencing this issue.
Let us know how it goes!
Thanks, Christine. We'll look into that.
It's peculiar that it only seems to be affecting our Storyline module, but we have hundreds of enrollments, so maybe the problem is only more visible there.
Stay tuned.
I am using Learnshare and getting the same error - just wondering what the solution was.
thanks
Hey Devin,
This conversation is a bit dated, so I'm not sure what the solution for Marie was, but I'd be glad to help you out.
just tested in Scorm Cloud and it works fine - so It must be with the learnshare lms. - I will contact them
Sounds like a plan, Devin!
Additionally, a useful tool for deciphering the communication between your Storyline content and your LMS is to enable LMS Debug Mode. If you can provide the resulting LMS debug log to Learnshare, they should be able to nail down what's happening.
Good luck, and do keep us posted!
Anyone know if this issue is fixed? And does the error happen with Rise courses? I’m hoping to purchase an Articulate license at my new job and they use LearnShare...
Hi Jessica,
We haven't identified anything within Storyline or Rise 360 that could lead to that error in LearnShare, but we're happy to explore further!
The best way to pinpoint the cause of this problem is to upload the published output in another LMS environment. We like to use SCORM Cloud since it's industry-standard:
If you need a hand with testing, share the LMS output files with us right here and we'll take care of the rest!
This discussion is closed. You can start a new discussion or contact Articulate Support.