Storyline SCORM 2004 packaging error

Hi all,

I've been publishing a Storyline file for SCORM 2004 3rd edition using Storyline's publish for LMS feature. I've encountered a weird behaviour: the imsmanifest.xml file never seems to be valid. Here's an excerpt from the file:


xsi:schemaLocation=" imscp_v1p1.xsd adlcp_v1p3.xsd adlseq_v1p3.xsd adlnav_v1p3.xsd imsss_v1p0.xsd>

Notice at the end of four of the lines there is " " (which is an HTML Encoded line feed character). I've never seen these before in an imsmanifest.xml file. When I remove these characters and re-ZIP the files, my files validate.

This seems really bizarre and I was wondering if anyone else has had the same problem or could offer ideas on a fix.

I'm using Storyline update 3: 1305.2012 on Windows 7.

Grateful for any help.

12 Replies
Stimpson Cat

Hi Leslie, thanks for your reply.

I'm testing on a range of LMSs, but ultimately it's being deployed on an in-house LMS. At run-time it has no effect on the operation of the course, which is good. Reporting is OK as well.

I'm getting the error:

  • on ADL's SCORM 2004 3rd edition test suite the imsmanifest fails the content package conformance test at the lines with the line feed character strings
  • on a local instance of Ilias, where it fails the validation step of the publish process.

I've tested on SCORM Cloud, and at publish and run-time there are no errors. However, I don't know if SCORM Could validates the files at any stage.

I've used the ADL test suites for a while now and have never seen this particular error. Ordinarily I would remove the errant characters as part of best practice, but since various people will be producing Storyline-authored SCOs this won't be done all the time.

Since there are only validation errors perhaps this thread should be changed to a bug report.

Justin Grenier

Aidan, can you share how this is impacting you?  Is this (like Stimpson above) only a failure within the ADL SCORM Test Suite, or is this also causing a failure within your LMS?  If it's causing a problem in your LMS, what LMS are you using, and what specific problem is it causing?  We'd like to get a clear picture of the impact this is causing.


Vincent Scoma

Hey Aidan,

We just released another update for Articulate 360 and included a few important fixes and new features that you'll see in the release notes here.

One of the fixes addresses the issue where the SCORM 2004 output, the imsmanifest.xml file had an HTML-encoded line feed character—&#xA;—that was causing an error in some LMS's.

The first step is to update Storyline 360. Head over to the desktop app and click the "Update" button for Storyline. More detail here.

If you have any questions, feel free to reach out here or contact our support engineers directly.