Hello, I need help. Because I can´t upload a SCORM-Package on my LMS. It is done in Storyline 360. I never had this problem before. It was working all the time. The problem report of my LMS (SABA) says invalid content. The manifest file can´t be extracted.
Hi Nica, we would need a bit more information on the error if possible. Also, it would be good if I could take a look at the manifest file. Maybe it has a character in it that SABA does not like. This can sometimes cause problems when parsing the manifest. Also, have you tested in SCORM Cloud to see if the same result happens there? If it does, it may give you some useful information on the error.
Hello back. Thanks for your answer. Yes, I have tested it on SCORM-Cloud and it works fine there. You can find the Scorm zip file in the attachment. Thanks a lot for your help.
I tried to upload your published content to SCORM Cloud, and yes, it successfully uploaded. Since we can upload it to SCORM Cloud, we don’t think it has a bug.
(...)
Can you try to create a new project file? A simple course with basic slides and a couple of quiz slides will do. Save it to your Desktop, then publish it for LMS. Once done, try to upload that to your LMS and see if you’ll receive the same error.
Please also make sure that you’re using the latest update of Storyline 360. Here’s how you can install the update:
This will help us narrow down the problem. Please follow the troubleshooting steps here if you’re able to replicate the problem even in brand-new files:
Additionally, ensure that you’re working on your local hard drive (typically your C: drive) when creating, editing, and publishing your Storyline courses.
Please note that working on a network drive or USB drive can cause erratic behavior, such as file corruption. Also, see to it that file paths to your projects and published output are well under the 260-character limit imposed by Microsoft Windows.
Also, syncing applications such as Dropbox, Google Drive, or One Drive may have stalled while trying to sync your project to the cloud storage you use, causing erratic behavior when working on your project files.
We recommend disabling automatic syncing of your files from these applications to avoid such issues.
thank you very much for your commitment. We have now found the following solution:
There is no longer a link to a file in the course and there is no longer a file in the resources. I have converted them into graphics and integrated them via the scroll element. So the file could be saved in the LMS.
Afterwards we checked every single file and found out that the error was caused by a file in the resources.
Many thanks. You gave us the idea to check the attachments again even if they were only simple PDFs.
5 Replies
Hi Nica, we would need a bit more information on the error if possible. Also, it would be good if I could take a look at the manifest file. Maybe it has a character in it that SABA does not like. This can sometimes cause problems when parsing the manifest. Also, have you tested in SCORM Cloud to see if the same result happens there? If it does, it may give you some useful information on the error.
Hello back. Thanks for your answer. Yes, I have tested it on SCORM-Cloud and it works fine there. You can find the Scorm zip file in the attachment. Thanks a lot for your help.
Hi Nicole,
I tried to upload your published content to SCORM Cloud, and yes, it successfully uploaded. Since we can upload it to SCORM Cloud, we don’t think it has a bug.
(...)
Can you try to create a new project file? A simple course with basic slides and a couple of quiz slides will do. Save it to your Desktop, then publish it for LMS. Once done, try to upload that to your LMS and see if you’ll receive the same error.
Please also make sure that you’re using the latest update of Storyline 360. Here’s how you can install the update:
https://articulate.fyi/2IZKEKs
This will help us narrow down the problem. Please follow the troubleshooting steps here if you’re able to replicate the problem even in brand-new files:
https://articulate.fyi/2iFZi8U
Additionally, ensure that you’re working on your local hard drive (typically your C: drive) when creating, editing, and publishing your Storyline courses.
Please note that working on a network drive or USB drive can cause erratic behavior, such as file corruption. Also, see to it that file paths to your projects and published output are well under the 260-character limit imposed by Microsoft Windows.
Please do review this article for more details: https://articulate.fyi/2mlEsPf
Also, syncing applications such as Dropbox, Google Drive, or One Drive may have stalled while trying to sync your project to the cloud storage you use, causing erratic behavior when working on your project files.
We recommend disabling automatic syncing of your files from these applications to avoid such issues.
I hope this helps and let me know how it goes.
Ronaziel Lopez
Customer Support Engineer
Articulate Support - https://articulate.com/support/
Hi Ronaziel,
thank you very much for your commitment. We have now found the following solution:
There is no longer a link to a file in the course and there is no longer a file in the resources. I have converted them into graphics and integrated them via the scroll element. So the file could be saved in the LMS.
Afterwards we checked every single file and found out that the error was caused by a file in the resources.
Many thanks. You gave us the idea to check the attachments again even if they were only simple PDFs.
Best regards
Nica (alias Nicole)
Thanks for sharing your reply with Ronaziel as well, Nica. I see the two of you are still working together.
This discussion is closed. You can start a new discussion or contact Articulate Support.