SCORM Manifest Causing Issues with UNIX-Based Server

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

Thanks for clarifying the impact, Aidan.  We'll take a look and discuss this with the team!

Thanks - appreciate it!

Hi Justin, just checking in on this - has there been any update from the team?

I also wanted to confirm the workaround as we'd need to be sure that removing these characters from the published manifest won't have any unintended consequences.

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. 😀

Hi Ashley,


 actually is the HTML code for a line feed - what we're wondering is, can we delete this from the manifest without causing another issue? Is it safe to do this?

Thanks for getting back to me - I appreciate it! 

Hi Aidan,

Yes - sorry for the odd wording, you can remove it to stop the error from
happening. Let us know if you need anything else!

Hi Ashley,

Thanks for the clarification!

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?

Thanks!

Aidan

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.

HI

My team and I are new to the Storyline 360 world having just installed our licences this month.  We are now carryout some tests with compatibility with our LMS and are also experiencing the issues reported above and wondered if there was any update or timeline for a fix?

Thanks

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="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"

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

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"

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

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"

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?

Thanks,

Aidan

I just realised that the forum software formatted the last manifest snippet. I've attached screenshot of the solution we used.

We are using Success Factors and getting the following error when we try to upload a Storyline 360 export (we just now converted to 360), which doesn't happen at all with the Storyline 2 version.

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.

Hi Leslie, it tested OK on SCORM Cloud but we get the following message: "Error on line 2... Cannot find the declaration of 'element manifest'" that you see at the end of the French message (sorry about that) in the attached image. Our system is SAP Success Factors.

What I mean is everything is OK on SCORM Cloud but the error appears on the SF LMS.

Valerie please see solution above - this worked for us when a client was using SAP Successfactors.

Regards,

Aidan

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="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 http://ltsc.ieee.org/xsd/LOM lom.xsd" xmlns:lom="http://ltsc.ieee.org/xsd/LOM" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:imsss="http://www.imsglobal.org/xsd/imsss" xmlns:adlnav="http://www.adlnet.org/xsd/adlnav_v1p3" xmlns:adlseq="http://www.adlnet.org/xsd/adlseq_v1p3" xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_v1p3" xmlns="http://www.imsglobal.org/xsd/imscp_v1p1" version="1.3" identifier="TS1535_FR">

-<metadata>

<schema>ADL SCORM</schema>

Thanks,

Danielle

Apologies Danielle, not Valerie!

Could you upload your manifest xml file?

Here it is... It was created and zipped straight from the Publish function in Storyline 360.

Thanks!

Yes it’s the same issue Danielle - it’s the line break characters 

&#xA;

that SuccessFactors has an issue with. If you remove those as we did in the above examples then you should be good to go.  

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?

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!