Trying to upload published course in Saba yeilds this Error
Jan 05, 2016
So, what's different about me publishing and uploading these courses from other successful efforts is that I'm getting these .story files back from a vendor who internationalized them (8 different language versions). I've tried three now and I get the same error for all of them...see below
(43073) Failed to import Content Inventory: Getting Started with Aspire - German
(43269) Invalid content. (*)ERROR: Failed to extract the manifest file from content package. Possible cause: The markup in XML document (manifest file) preceding the root element is not well-formed.
I'm using Saba LMS...but I'm thinking the issue is the .story files I've gotten back. When I preview the .story files, they work fine.
Any ideas?
25 Replies
UPDATE:
I've narrowed this down. They upload fine when I remove my resources. The resources are .pdf files with long names in foreign languages...accent marks etc. Do you think that is a factor?
Hi, Russell -- Sorry to hear you are having difficulties! Have you tested your course in the SCORM Cloud, by chance? If you do not see the same behavior there, you may want to reach out to your LMS provider directly for additional assistance. :)
Hi Russell!
I have seen this reported before in this thread and yes, the length and special characters can cause issue.
I received the following error when trying to upload a SCORM file in Saba from Articulate Studio 13. Any insight into why this might be? When I recreated the same file, I got the error mentioned previously in this post. I'm not sure what is going on. Can anyone advise?
(43073) Failed to import Content Inventory: Org Charts (43209) Failed to generate TOC. Error: "java.io.FileNotFoundException: /home/spc/SabaWeb/temp/sabacr1128832556174271373/imsmanifest.xml (No such file or directory)". Please make sure the Asset Storage is configured correctly.
Hi, Angela -- Thanks for reaching out and sorry to hear of your troubles! May I ask if you have had an opportunity to reach out to Saba directly for their thoughts on the error message you are receiving? And as noted above, have you had a chance to take a look at at whether the names of your resources are lengthy or include special characters? You may also want to store your resources on your local C drive to see if you find improvement, as well.
Hi Angela!
Are you zipping the contents from the publish successful dialog box prior to upload? This typically works better than manually zipping.
Are you able to recreate this issue in SCORM Cloud or is this limited to your LMS?
I renamed my files and republished them and tried again and still got the error. When I reached out to Saba I received the following:
Hello Angela,
Thank you for contacting SABA support.
I have checked the case and also checked the error that you are getting and seems that the issue is with the content file and the imsmanifest.xml and need to liaise with your content vendor.
Could you please check the same with them and try uploading this once again.
So as you can see, they are telling me to ask you, and you are tell me to ask them...leaving me unsure how to proceed.
I'm zipping from the publish successful dialog box. I have not tried to recreate in SCORM Cloud. Will try that.
Thanks Angela! If you are able to recreate, please share the .story file for us to take a look.
it's not a .story file. It's a studio file. Will that make a difference?
Haha! No, I assumed Storyline as that is where you've posted your issue. If you are able to recreate, then share your Articulate Package for us to take a look :)
I'm facing a similar problem with loading a Storyline SCORM in SABA LMS. Any update on this thread might help me.
Hi Sushmita,
Thanks for reaching out with what you are having difficulty with. This thread is a bit dated, but I'd love to be able to help you out.
A great way to test if an issue lies within the project file or your LMS is to test in an environment such as SCORM Cloud.
We'd be happy to test this out for you if you'd like to share the .story file for us to take a look.
Hi Leslie.
Thank you for your response. The published project tests well on the SCORM cloud. I'm attaching the error the client is seeing on the LMS and the published file for you to test. Really appreciate your help.
Hey Leslie, Can I have your email id to send you the Story file?
Hi Sushmita,
Thanks for sharing the .story file so that I could take a look.
I was able to publish the file and successfully upload it to SCORM Cloud.
Here is the published link.
You can find the zipped published output here if you'd like to test upload to your LMS.
Hi Leslie, I was also able to test it well on the SCORM cloud but it doesn't seem to work on the SABA LMS.
Thanks for the update Sushmita.
Are you zipping the output from the publish successful dialog box or manually zipping the content?
Did the output that I shared above not upload to your LMS either?
I did notice that the title is a bit long, so be sure that you are publishing locally and perhaps reduce the number of characters to see if that works better for you.
HI all. I am having the same error for the Rise files I published in web format. Any suggestions on what I can do to avoid this would be awesome.
My published file didn't work on the SCORM cloud either :(
Thanks in advance.
Hi there, Sonica. We found an issue with Rise 360 output exported for SCORM when it includes Storyline blocks. There is an unnecessary
tincan.xml
file in the output that is giving some learning management systems trouble identifying the SCORM format.We'll help pinpoint what's happening and give you some next steps!
Hi Crystal
Thanks for your response. I have no storyline blocks in the Rise content I created, but it's good to be aware of that. Are you suggesting deleting the tincan.xml file in such an instance?
For now, the Rise content is exported for web and hosted on a LMS. I have done this multiple times in the past with no issues.
Appreciate your help and attention.
Cheers
Hi Sonica,
It sounds like you may be running into a different issue than we've seen.
I'm opening up a support case on your behalf so that you can work directly with one of our support engineers.
Hi Leslie
Fortunately I was able to resolve this at my end by renaming the files - shorter naming conventions might be the way to go for us now.
Thank you for your support and raising the support case. Mystery solved - case closed :)
regards
Sonica
That's great news, Sonica.
Thanks for popping in and sharing that update. I've passed this information onto Gren in your support case as well :)
This discussion is closed. You can start a new discussion or contact Articulate Support.