Storyline 2: Update 4 - Issues while sending quiz interactions to LMS
Mar 03, 2015
Hi all,
I needed some help from you in figuring out the following issue our client is facing on a huge scale.
We have been delivering similar courses to our client and we did not face this issue before, but after we upgraded to Storyline 2 Update 4, the course is sending too much data to the LMS which is used by as many as 20k people at the same time leading to a server crash and throwing them out of the LMS.
The course contains 40 odd questions and all the interactions are tracked, however, the data that is sent to the LMS is in large volumes. I have attached the client LMS data log and Rustici log for the same course here for your reference. Can you please help us out of this situation as this is affecting several learners on a national scale and our client is extremely worried about this?
Regards,
Deeps
3 Replies
If it is the server crashing due to increased loads, I would speak to the web host / LMS host about the issue.
Hi James,
Thanks for your reply.
We tested a course built on previous update of Storyline 2 and did not come across such issues. Also, we created some sample quiz questions and tested them on Rustici and found that the score(setscore) is updated twice for a question. We wanted to be sure if anyone else is facing such issue and if this is occurring only due to the update.
This to has been affecting us for sometime, now. It happens on AICC courses. Most users have low interaction communication with the LMS. When the issue happens for 1 person, there are LOTS of calls to the LMS. The longer they are in the course, the more rows that are created on our AUDIT table from those LMS calls. Our LMS is Oracle PeopleSoft ELM 9.2, PeopleTools 8.5.
It just happened yesterday on a course that was created and the course content uploaded on 10/10/2017. Never had any large audit counts on this course until 11/01/2018 and 11/02/2018.
The problem is not with the LMS. And, it does not seem to be a course content issue. It has to be something with the software the course content uses (i.e. Flash, Java, HTML5, ...) because it is not affecting everyone. It also seems to be happening more often. But, what is causing this? It has been a freaking nightmare as it will crash the ELM.
One way to stay ahead of it for courses that have this issue, we changes the ForceCommit value on the lms.js file to some large number because 0 does not always work. For courses we have had issues with, we change this value to 28800000 for 8 hours. After that, the course is no longer a problem.
Deeps, any update on what the resolution was for your client?
This discussion is closed. You can start a new discussion or contact Articulate Support.