Storyline SCORM 2004 packaging error
Jun 24, 2013
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:
<manifest
xsi:schemaLocation="http://www.imsglobal.org/xsd/imscp_v1p1 imscp_v1p1.xsd
http://www.adlnet.org/xsd/adlcp_v1p3 adlcp_v1p3.xsd
http://www.adlnet.org/xsd/adlseq_v1p3 adlseq_v1p3.xsd
http://www.adlnet.org/xsd/adlnav_v1p3 adlnav_v1p3.xsd
http://www.imsglobal.org/xsd/imsss 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
Hi Stimpson and Welcome to E-Learning Heroes! Can you tell me what impact this is having in your LMS? Have you tested the content in SCORM Cloud to see if it's the file or your LMS?
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:
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.
Thanks for the information, Stimpson.
I'm having a little trouble with my copy of the SCORM Test Suite right now. Would you be able to supply a report or screenshot from your copy that demonstrates this error? Thanks!
Hi Justin,
Please find the screenshot attached.
Thanks for the screenshot, Stimpson.
I have reported this behavior to the Articulate Quality Assurance Team, and we will keep you posted on any further developments. Have a great day!
Thanks Justin.
Hi all - just wanted to check and see if there was ever any resolution to this 4 year old issue? :)
I may be experiencing something similar in Storyline 360.
Thanks for joining the conversation, Aidan, and sorry to hear you're running into this. We are seeing a problem in Storyline 360 where a 
 is generated in the imsmanifest.xml file of SCORM 2004 4th Edition output.
Does that seem to match what's happening in your file?
Hi Alyssa - exactly the same thing, except I'm seeing it on 2004 3rd edition publishes.
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.
Thanks!
Hi Justin - I created this question a couple of days ago:
https://community.articulate.com/discussions/articulate-storyline/scorm-manifest-causing-issues-with-unix-based-server
Thanks for the reply!
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—

—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.
This discussion is closed. You can start a new discussion or contact Articulate Support.