Issue with revisiting published content

Hi All,

We have a number of courses that have been created in Storyline (what a God send!) - All play fine as 'stand alone' content (launched via story.html) and also mostly fine when uploaded to our Oracle LMS (OLM).

The issue arises when the course has been completed - The status is marked as complete in the LMS (so I know that SCORM is working correctly), yet when the user tries to re-launch the course again, they see the scrolling wheel (as if it is going to launch) but then it stalls on the first screen, meaning that they can't continue.

To add something else into the mix, this ISN'T the case for ALL learners (we do have around 70,000 of them!) - In most cases, the content is fine, and replays as it should  (suggesting that the output content ISN'T at fault).

Yet our LMS providers say that there is nothing wrong their end either (and small, test courses they have asked me to upload are working correctly), and that I should question the content provider...

Which, of course is ME!

Any ideas?! It looks/feels like the the content fails when it is trying to work out where to re-start the course...

Thanks for any advice

Paul

3 Replies
Mike Taylor

Hi Paul! I can totally relate to your challenge. I've been in those very same shoes before. Troubleshooting LMS issues can be tricky. Here is an article that might give you some good things to try: http://www.articulate.com/blog/troubleshooting-lms-issues/

Since it seems that only some of your learners are having the trouble, have you tried to identify if there are any differences on the PCs that do not work? i.e. different browsers, java versions, etc etc?

Good luck!

Mike

Mike Taylor

Are you able to test this in SCORM Cloud.? Here's an article that might be helpful for that.

That would help us determine if the issue is Articulate-related or if it's on your LMS's side. If it appears in SCORM Cloud as well, we'd be happy to take a closer look at what might be going on. If you can't replicate the issue in SCORM Cloud, it's probably an issue that you'd want to discuss further with your LMS team.