SCORM error 405
Feb 06, 2014
Hi community!
I've created a random question draw of 25 questions, with answer shuffle turned on. I've uploaded the SCORM file to ScormCloud and upon viewing the debug log found that all responses to these questions receive the following error:
Set Error State: 405 - cmi.interactions.n.student_response must be a valid CMIFeedback
I understand that the CMIFeedback value much be a single letter and this does appear to be happening just not in a way that is intuitive. The questions are graded appropriately, the issue is that the error makes item analysis incredibly difficult. It appears that the first letter of each choice is assigned as the CMIFeedback value.
For example:
This is the question.
a. This is a possible answer.
b. This is a possible answer.
c. This is a possible answer.
d. This is a possible answer.
The answer choices above seem to be assigned "t" as the CMIFeedback value so it's impossible to decipher which choice a learner actually selected.
Is there a way to set this value in Storyline? I've already renamed the choices which seemed like the most logical thing to do. I look forward to your help with this!
Thank you (in advance)!!
21 Replies
Hi Lesley,
Were you viewing the scorm cloud debug info, or had you turned on the Storyline debug mode? In a similar thread, it looks like Darrell needed to change to submit all questions at once.
In regards to determining the answer chosen, were you able to look at any of the reports to see how a user answered?
Hi Ashley,
I was viewing the SCORM Cloud debug log. I'm not having issues with the grading which I believe is what the thread with Darrell is about. I'm unable to decipher what a student selected because rather than seeing "a" "b" "c" or "d" which is the answer choices for a question, I'll see that a student answered "w". If they got the question right then I can figure it out, but if they got the question wrong, I have no idea which choice they selected!
Any other ideas? Thank you!
Hi Lesley,
I'm not as familiar with the SCORM Cloud debug log, but to check and see what the user answered, you'd want to look at the reporting features.
Hi,
We have also had this problem and found that when publishing in Scorm 2004 you don't have this Issue.
It turns out that the single characters described by Lesley above are actually the first letters of the answers text.
Hope that helps shed some light.
Thanks Lee for sharing here and welcome to the Heroes forum!
I have this problem with storyline 1 and 2. what can I do to fix my answers so they are correct?
Hi Kevin,
I'm not sure I understand what situation you're running in to? With Lesley's post the information she was seeing in her report was determined by how she was publishing and the information held in the SCORM files, and as Lee mentioned publishing with SCORM 2004 provided more information and detail.
If you're running into an issue with how answers are reported, I'd first look into what options are available within your LMS for reporting and information provided. You could also look into using a site such as SCORM Cloud which is an industry standard for testing SCORM Content. If something isn't behaving as expected in SCORM Cloud than we're happy to take a look.
I have created a test in Storyline 2, there are 85 questions and I am randomly selecting 50 questions. The majority of the questions are multiple choice. When the test is put on the LMS, several people finish the test but the LMS doesn't show the grades. I have debugged on SCORM cloud like described on this site. When I publish to SCORM 1.2 I get error 405 for every multiple choice question. If I publish to SCORM 204 I get error 403. I need some help on this issue.
Hi Kevin,
We'll need to take a look at the .story file, and have the LMS debug logs as detailed here (these are different than the logs generated by SCORM Cloud). You can share this information here with us or send along here. Please let me know once you've submitted the information.
I have send the information.
Thanks Kevin.
Hello
I have the same Problem ...
I created a FreeFormPickMany Question and
1.) Sometimes it works and I get result
2.) sometimes it s not working and I get "undefined"
I tested it in SCORM Cloud and get:
"Set Error State: 405 - cmi.interactions.n.student_response must be a valid CMIFeedback - value must be consistent with interaction type."
________________
[11:21:03.465] LMSSetValue('cmi.interactions.0.id', 'Scene6_Slide1_FreeFormPickMany_0_0') returned 'true' in 0.002 seconds
[11:21:03.465] CheckForSetValueError (cmi.interactions.0.id, Scene6_Slide1_FreeFormPickMany_0_0, cmi.interactions.n.id, 0, )
[11:21:03.465] Element is: interactions.id
[11:21:03.465] Call is error free.
[11:21:03.466] StoreValue (cmi.interactions.0.id, Scene6_Slide1_FreeFormPickMany_0_0, cmi.interactions.n.id, 0, )
[11:21:03.466] Element is: interactions.id
[11:21:03.466] Adding new interaction at position 0
- [11:21:03.467] LMSSetValue('cmi.interactions.0.type', 'choice') returned 'true' in 0.002 seconds
[11:21:03.468] CheckForSetValueError (cmi.interactions.0.type, choice, cmi.interactions.n.type, 0, )
[11:21:03.468] Element is: interacitons.type
[11:21:03.468] Call is error free.
[11:21:03.468] StoreValue (cmi.interactions.0.type, choice, cmi.interactions.n.type, 0, )
[11:21:03.468] Element is: interacitons.type
- [11:21:03.469] LMSSetValue('cmi.interactions.0.student_response', 'Posture:_se_tenir_assis_et_droit,Pr_paration_de_la_vente,Pr_parer_un_bloc-notes_et_un_stylo') returned 'false' in 0.001 seconds
[11:21:03.469] CheckForSetValueError (cmi.interactions.0.student_response, Posture:_se_tenir_assis_et_droit,Pr_paration_de_la_vente,Pr_parer_un_bloc-notes_et_un_stylo, cmi.interactions.n.student_response, 0, )
[11:21:03.470] Element is: interactions.student_response
[11:21:03.470] SCORM ERROR FOUND - Set Error State: 405 - cmi.interactions.n.student_response must be a valid CMIFeedback - value must be consistent with interaction type. Your value is: Posture:_se_tenir_assis_et_droit,Pr_paration_de_la_vente,Pr_parer_un_bloc-notes_et_un_stylo
__________________
Hi Axel! Sorry to hear that you ran into this issue as well. I was able to dig into the case mentioned above and it seems it was a data restriction for SCORM 1.2.
Have you tried to publish to SCORM 2004? This standard resolves the character limits that are imposed upon suspend_data.
Hello, when I exportet it with SCORM 2004 I only get the last (one) choice -
I need three ... so I switched to SCORM 1.2
In the GERMAN and ITALIEN Version it seems that everything works fine -
just the FRENCH one - (sometimes) cause this error
cheers
Axel
Interesting Axel. Would you be able to share the details and the file with our team here so that we can look into this since you are able to replicate in SCORM Cloud?
yes would be great
I send you the "small" version (without the long content arround) just the ONE AND IMPORTAND Pick many question:
People should only select 3 out of 13 ...
cheers
Axel
Hi Axel!
Thanks for sharing your file. I published it, but I'm not getting an error.
Can you take me through the steps to re-create the error you are reporting?
https://cloud.scorm.com/sc/InvitationConfirmEmail?publicInvitationId=84803ca1-4b45-4e11-befa-d7f170f3f8c8
https://cloud.scorm.com/sc/guest/ViewDebugLog?logId=a2d903dc-65f2-4c64-b535-d75bf94e81b6&courseTitle=e-Learning%3A+SHINE+-+Focus+sur+la+phase+1
This is crazy - here I have this error - but only sometimes ...
and I think in the german and italien version everything is ok
Hi Axel!
Have you tried to re-publish the content to see if you get the same error? I'm not able to re-create.
Yes this is very strange
Now it s online/live and it s difficult to change it ...
I tried it today and get one error out of 3 tries -
I don t know what is wrong
- I think it s only in the pick many questions ... so in future I will better not use it.
I don t know what the reason for this is
cheers
Axel
cheers
Axel
Hi Axel!
If it's only one file, it may be beneficial to try to import into a new file to see if this helps alleviate the issue as well.
This discussion is closed. You can start a new discussion or contact Articulate Support.