SCORM Manifest Causing Issues with UNIX-Based Server

Hi Folks,

I'm wondering if anyone experienced any issues with the formatting in the published manifest file? 

The publish is showing up like this - and seems to be adding formatting characters to the end of the XSD file reference in imsmanifest.xml: 

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

Unfortunately this is causing an issue with one of our clients who utilizes a UNIX server, as this formatting is being read as a line break.

1. Is this a glitch/error on publish?

2. Will removing this formatting cause issues that anyone is aware of?

The reference documentation gives an example of the manifest schema headers as:


Many thanks,


45 Replies
Justin Grenier

Thanks for letting us know about this, Aidan.  As you pointed out, one other customer encountered similar behavior, and you should be able to remove the offending characters as a workaround.

Can you elaborate on the issue that this is causing for one of your clients who utilizes a UNIX server?  What is the specific problem or error message that these characters cause?

Aidan Simpson

Thanks, Justin.


They are getting an error when uploading to their LMS:

Issue: The parser could not validate the SCORM Import file due to the following reason(s). Proceeding with the import may incompletely import the file, or the file itself may be corrupt. You may choose to continue with the import at your own risk.

Error on line 2: cvc-elt.1: Cannot find the declaration of element 'manifest'.

Ashley Terwilliger-Pollard

Hi Aidan,

Thanks for checking in! 

I just saw an update from our team on this, so perfect timing. 

The error message from the LMS can safely be ignored, or you can manually edit the imsmanifest.xml file and replace the 
 character with a line feed. That'll stop the error message from popping up - as I know those can be alarming! 

Let us know if you need anything else. 😀

Aidan Simpson

Hi guys, just wanted to bring this one up again.

Another of our clients are affected by this, as the manifest template contains these characters (&#xA).

The question I need to ask is, is there a reason this is contained in the publish? If not, is there a timeline for a fix?




Leslie McKerchie

Hello Aidan,

Sorry to hear that this has caused an issue for you again. I'm not sure of the 'why' on this, but we do have it reported. I wanted to share some information on how we define bugs and how we tackle them when they occur.

I also verified that the report reflects the number of users affected.

Aidan Simpson

Hi Lynn - we think we've isolated the issue but we're still doing some testing - hopefully this helps you. We tracked down line breaks in the Storyline manifest template files for each SCORM edition found here:

C:\Program Files (x86)\Articulate\360\Storyline\Content

There are folders for each SCORM edition, and we manipulated the imsmanifest.xml file for the required publish. Once changed, this is the basis of each publish. Whether this file remains changed when there is a Storyline 360 update

Bear in mind that we're using SCORM 2004 2nd Edition, so we updated the file in the scorm_2004_2nd folder. If you'd like to try this, take a copy of the imsmanifest.xml file and keep safe in case you need to roll back the changes.

For the entry:

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

For some reason, on publish, Storyline seems to be reading the new line breaks here and converting them to:

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

The solution that we're implementing is to remove the line breaks, mitigating the publish error:

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

This seems to have helped, but as I say, we're still in testing. Hope this helps you.

Out of interest, by any chance are you using SuccessFactors for your LMS?




Leslie McKerchie

Hi Danielle and welcome to E-Learning Heroes :)

Sorry to hear that you're having difficulty uploading your published file to your LMS.

Are you using the Zip feature in the Publish Successful dialog box? 

Do you experience the same error when uploading the content to SCORM Cloud or is this limited to your LMS?

If you need us to take a look, please share the .story file.

Danielle Vallee

Here is what we're getting at the beginning of the imsmanifest.xm document, which is quite different fromwhat you have on your image:

<?xml version="1.0"?>

-<manifest xsi:schemaLocation=" imscp_v1p1.xsd adlcp_v1p3.xsd adlseq_v1p3.xsd adlnav_v1p3.xsd imsss_v1p0.xsd lom.xsd" xmlns:lom="" xmlns:xsi="" xmlns:imsss="" xmlns:adlnav="" xmlns:adlseq="" xmlns:adlcp="" xmlns="" version="1.3" identifier="TS1535_FR">


<schema>ADL SCORM</schema>



Danielle Vallee

I was finally able to put my hand on a tool that could show me the code and I was able to correct the file. Now, when trying to upload, the upload fails and we're getting another very strange message in French saying "The postal code that was imported does not contain any valid content file". We just bought a 360 subscrition and I know that with a trial we can't upload on an LMS but that shouldn't be the case, right? Can you confirm that as soon as we subscribe, the paid subscription goes into effect? If that is so, I think it is either the LMS or the person's computer or both that are acting up... Unless you have another idea?

Aidan Simpson

Hi Danielle, I think the translation of that error into English messed up a bit - possibly on Google Translate? I think you might be referring to "imported zip does not have valid content files". From my experience this error mostly happens when the SCORM package isn't zipped properly or is missing the manifest file. Hope this helps!