LMS SCORM 1.2 Error

Uploading Storyline module to LMS (Rubicon Intuition) gives "Input string was not in a correct format." error.  However, uploading modules make with Presenter works fine.   Of course, the bulk of my content is built in Storyline.  Uploading Storyline to SCORM Cloud works fine.   So, I'm caught between my LMS support and Storyline.  Any similiar experiences with error above. 

8 Replies
Peter Anderson

Hi Neil

You may want to try testing your course in SCORM Cloud to 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 take to your LMS team. The articles here and here may also help clear up common LMS issues.

Hope that helps!

Neil Stadlman

Thanks for the suggestions.  Yes, the module works fine in SCORM Cloud and I am working our LMS provider regarding the issue.  SCORM Cloud is a great resource to confirm viability when working with other sources.   Thanks for the article resources as well.  Always value the great Articulate support. 

Bryan Tregunna

We too have the issue with Intuition Rubicon and they have identified the issue and have a workaround for you.

In the manifest file locate the following XML node
   
               
                                  PT1H0M0S
                
   

Change the duration to time        01:00:00

This begs the question why does Storyline convert the hh:mm:ss format to a different format? 

Bryan Tregunna

This time with the tags replaced with square brackets!!

We too have the issue with Intuition Rubicon and they have identified the issue and have a workaround for you.

In the manifest file locate the following XML node
[educational]
[typicallearningtime]
[datetime]PT1H0M0S[/datetime]
[/typicallearningtime]
[/educational]

Change the duration to time    [datetime]01:00:00[/datetime]

This begs the question why does Storyline convert the hh:mm:ss format to a different format?

Neil Stadlman

It took us countless back and forths to discover the issue, so much so I forgot I even posted this.  Yes, we discovered the need to modify the manifest file to insert the time as  00:00:00.   

As is the case usually, the simplest things cause the biggest problem.  However, you raise a good point as to why this happens.

Thanks so much for posting as I should have.   That’s why I appreciate this resource