Users from Indonesia of a course my company uses worldwide (US based) have reported that they have gotten lengthy reports instead of a working course. This isn't happening anywhere else that we know of. We use Success Factors and have replicating servers worldwide (but I don't know about Indonesia specifically).
Has anyone seen anything like this? Or, after looking at the report I attached, do you have an idea of where the failure is occurring? I think it's related to the network / LMS delivery rather than the Storyline course... but I'm really out of my depth here.
Sorry your post was flagged - it happens sometimes when our site things it's possibly spam. Luckily our team checks it and releases posts back into the wild!
That error message does look similar to what you'd see if you had enabled LMS debug mode, but you could also look at testing it in SCORM Cloud.
The course has been tested in SCORM Cloud and our LMS. My LMS admin hasn't gotten back to me on whether or not we have any kind of debugging mode turned on.
I assumed that but was just checking. :) It does sound LMS specific then. Not the quickest solution, but you might have to wait to hear back from the LMS admin. I believe you can also turn on debugging by editing the published output from Storyline, but this is not something that could have been done by accident.
I'd also wait to hear from your LMS team - or look at uploading a new copy to see if you can produce the same thing again. As Michael mentioned the LMS debug mode for Storyline isn't something that can turn on automatically or by accident- you'd have to follow the steps here to enable LMS debug mode.
They say nothing is evident from their end which would indicate enabling a debugging mode... And now the LMS admin that's been helping me is on sick leave.... So, Indonesia is gonna have to wait. Thanks for all your help.
11 Replies
Why is my OP flagged? It's a legit problem...
bump my own thread
Paul, did you do anything to enable debugging in your course or on the LMS itself? This looks kind of like a debugging report.
Not from the course side... Unlikely on the LMS side, but I will ask our admin to doublecheck.
Hi Paul,
Sorry your post was flagged - it happens sometimes when our site things it's possibly spam. Luckily our team checks it and releases posts back into the wild!
That error message does look similar to what you'd see if you had enabled LMS debug mode, but you could also look at testing it in SCORM Cloud.
Hi Ashley,
The course has been tested in SCORM Cloud and our LMS. My LMS admin hasn't gotten back to me on whether or not we have any kind of debugging mode turned on.
Paul, did you see the same thing appear when tested on SCORM Cloud?
Good question... Should have put in that in my last repsonse.
No. It would never have passed into the LMS had either the SCORM Cloud testing or initial LMS testing produced a report like this one.
I assumed that but was just checking. :) It does sound LMS specific then. Not the quickest solution, but you might have to wait to hear back from the LMS admin. I believe you can also turn on debugging by editing the published output from Storyline, but this is not something that could have been done by accident.
Hi Paul,
I'd also wait to hear from your LMS team - or look at uploading a new copy to see if you can produce the same thing again. As Michael mentioned the LMS debug mode for Storyline isn't something that can turn on automatically or by accident- you'd have to follow the steps here to enable LMS debug mode.
Let us know if you hear back from your LMS team!
They say nothing is evident from their end which would indicate enabling a debugging mode... And now the LMS admin that's been helping me is on sick leave.... So, Indonesia is gonna have to wait. Thanks for all your help.
This discussion is closed. You can start a new discussion or contact Articulate Support.