Error when publishing to Success Factors LMS

Hi everyone, 

My organization is implementing the Success Factors LMS.  I have created courses in Storyline 3.   When we try to publish the courses to the LMS we get the following message:


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



Not sure if I am posting this in correct group.  Can anyone help?

4 Replies
Leslie McKerchie

Hi Tim,

Thanks for reaching out and letting us know the error you are running into when uploading your file.

Are you able to recreate this error if you upload the file to SCORM Cloud or is the issue limited to your LMS?

Be sure that you are zipping the content from the Publish Successful window prior to uploading.

I've also seen a previous conversation here that may offer some helpful tips for your environment.

Tara Luciano

Has anyone been able to come up with a true solution to this? We have a client who uses Success Factors and we have published in 2004 2nd edition and 4th edition. They are receiving the same errors as mentioned above and a new one "SCORM 2004 content package contains sequencing and navigation rules. It cannot be added to the item as the item can only contain one set of sequencing and navigation rules." 

Has it been determined what version of SCORM works best with Success Factors? 

I checked the other threads and their solutions have not worked :(

Katie (Gokhshteyn) Riggio

Hey there, Tara!

While I don't have much experience with Success Factors, I'm happy to rule out any issues on Storyline's end that could be causing those errors.

First, what version of Storyline are you using?

  • If Storyline 360: We fixed an issue in Update 30 where the imsmanifest.xml file in the SCORM 2004 output had an HTML-encoded line feed character—
—that caused an error (like the 'The parser could not validate' one) in some LMSs. 
  • If Storyline 3: You can fix this by manually editing the imsmanifest.xml file and replacing the 
 character with a line feed.

I haven't seen the other error before, though. Have you had a chance to connect with the LMS team for their insight? With your permission, we'd love to help test in another LMS environment like SCORM Cloud. Just give us a shout; we'll be right here!