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
Ashley Terwilliger-Pollard

Hi Danielle,

Also, I wanted to confirm that the trial is a full version of Articulate, so you can test out all the functions such as zipping and uploading to your LMS. In addition to using the Zip option on the publish successful window - where are you placing the output? You'll want to check that you're using a short file path along with the file name/path conventions outlined here to prevent any odd behavior.

Also, to narrow down the issue and see if it's specific to the SuccessFactors LMS you can also test in SCORM Cloud. Take a look at the steps on how to do that here.

Veljko Roskar

The latest SuccessFactors learning (Release: b1805.20180802073351) still exhibits this error when uploading SCORM 2004 zip packages generated by Storyline360 <schema>ADL SCORM</schema><schemaversion>CAM 1.3</schemaversion>:

 "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'."

Deleting the offending string &#xA; from imsmanifest.xml and re-zipping the package resolved this error, however why are these linefeed escape characters added to the manifest schemalocation strings in the first place?


Aidan Simpson

Hi Michael, 

We got around this by editing the manifest publish templates at :

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

This works on every publish, but the drawback is that they need updated every time Storyline 360 receives an update. We keep copies of all the SCORM version xml manifests to quickly do this.

Until this is fixed, I hope this helps you.

Heras Safety

Hi there,

Im experiencing the same issues and we're getting the following error when uploading to SuccessFactors:

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

From what I understood in other topics this is related to this topic. However, I'm not sure what I should edit in the XML file, I have downloaded an XML editor but I'm not familiar with editing XML files.

Also; I'm using scorm 2004 4th edition, does this fix apply for the 4th edition too? Appreciate the help!



Matthew Leathes

Any update on a fix for this from Articulate?

Note that, in some organisations where desktops are quite locked down, users will not have the rights to edit the manifest template file without having to involve IT which may require considerable effort if your firm has very strict IT policies. It would actually be easier to request that they patch the software with an official update from yourselves...

Please also note this which I also believe to be a problem.

Ashley Terwilliger-Pollard

Hi Matthew,

This issue is still open with our team. I do see it noted that the error is one that's safe to ignore, and if it can't be ignored, you'd need to make that edit to the manifest file.

We'll let you know here if anything changes on this issue, and we'll take a look at your other discussion too. 

Katie Riggio

Hi, Kim. Thanks for checking in!

Our team is still monitoring this issue, so I appreciate you letting us know that it's affecting your projects. Here's a glimpse into how we tackle bugs when they're reported!

The current workarounds are to either ignore the error or delete the string &#xA; from the imsmanifest.xml file. If there's anything else we can help with, please let us know!

Jacques Maeda

I have also experienced the same issue with SuccessFactors (SF) and Articulate Storyline with SCORM 2004 2nd and 4th. SCORM 1.2 works perfectly and SCORM 2004 3rd is not compatible.

As advised, I have ignored the warning and imported and SCORM package, but it does not track completion (only progress).

Then, I have implemented the proposed solution, I have changed the imsmanifest removing the character &#xA; as recommended, and the SCORM package has been imported successfully (no warning message anymore).

However, when I finish the course and close the window, I get the error:

"Validation Error: Sorry, but you have been exited from the item as a result of the content you just took."

And the progress is reset.

I have contacted the SAP SucccessFactors support and they asked to contact the content vendor: Articulate. Additionally, I have found an SAP Note saying this error is caused by the SCORM version 2004 3rd (which is not).

SCORM Cloud requires signing up just as free for trial only.

Please could you advise and provide a permanent fix?

Thank you.



Leslie McKerchie

Hello Jacques,

I do not have an update on the issue at this time, but if you need assistance testing your project file in SCORM Cloud for the tracking issue you're running into, I'd be happy to help you out.

With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.

Vincent Scoma

Hey all,

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.

Katie Riggio

Greetings, everyone. A quick update!

For those using Storyline 3: We're excited to share that Update 7 is now live – check out all the goodies here, and here's where you can download this latest version!

One of the fixes addresses the issue Vincent mentions above: In SCORM 2004 output, the imsmanifest.xml file had an HTML-encoded line feed character—&#xA;—that caused an error in some LMSs.

Let us know what you think!