Forum Discussion
Corrupt ZIP file when publish to LMS
Hello, I have been publishing to LMS using SCORM 1.2 format for more than 2 years now, without any issue. But suddenly I get problems.
The zip files are not handled by me personally, but by our Learning Service department. The latest ZIP file was erroneous, according to them with the following explanation.
"We checked the folder that you have shared and one of the entities which is "imsmanifest file", that LMS searches in order to upload content is not available. It is the primary file that system looks out for to start the import process, and I checked in the folders as well but could not find any. Therefore, please ask the content vendor to provide the .zip file along with the manifest file else it will error out".
What can have gone wrong here?
B.R
10 Replies
Problem solved, apparently there was some problem with the IT Service Management-system. I don't more details than that, but at least there was no faulty behavior by Storyline 360.
But what I have been told that system we are using for uploading the ZIP files don't like spaces in the title of the zip file. So heads up, you might need to remove the spaces in the filename before deliver the zip file.Until only very recently, Saba (Cornerstone SBX) was notorious for unilaterally replacing spaces in the filename of an uploaded file with underscores. Made it a real pain when you were searching the shared development environment for a file based on the filename Saba displayed versus the actual filename. 🙄🤦
I wonder if the ZIP file got ZIPped again. I had a developer who thought they knew better than the app, and proceeded to ZIP the published ZIPped file. Of course, the LMS barked when I tried to import the file because there was no imsmanifest.xml at the root of the ZIPped file, it was one level down.
Hi OlleSchlin!
Glad to see Eric has been helping you!
Publishing from Storyline to LMS should always include the imsmanifest file, automatically. Eric highlighted the benefits of working locally, as publishing directly from a network drive may introduce fragmented output such as this.
If the .story file is already located on your local drive, but the imsmanifest file is absent, it would be helpful to see a copy of the project for testing. Do you mind uploading the file here in the discussion or privately through a support case?
Looking forward to hearing from you!
As far as I can see, the imsmanifest file is included in the output from the publication as well as in the zip-file. See below. So I cannot really see any error from my side. So my question either related to
1) if any users have experienced a situation where the imsmanifest have disappeared or have been automatically removed later the process.
or
2) the information I got from Learning Service department indicating something else, not directly related to the missing imsmanifest file
Some days I hate computers. Sound like you and your department knows a lot more about these files than I do. However, every time I hear about corrupt files this seems to be part of the fix. The other part of my fix was to uninstall the 104 update and reinstall the 103 version. As all my files are stored on my OneDrive.
You might want to start a case with Articulate and have them check your file.
You could be 100% correct, it sounds like you know a lot more about these
I recently had issues with a file, here's what i was told by Articulate.
When working with syncing applications like OneDrive, Dropbox, or Google Drive, these apps can sometimes stall while trying to sync your project to their cloud storage. This can cause erratic behavior in Storyline, such as errors during publishing, saving, or even corruption of files.
To avoid such issues, we recommend ensuring that your project files are saved to a local folder that is not being automatically synced to any cloud storage service. If needed, here’s an external guide on how to stop syncing to OneDrive.
They recommended all files be stored on your hard drive. In our world today i don't see how this is possible working with Teams to produce content.
I would see if you can make a copy on your hard drive to see if it fixes the issues. You may try creating a new blank project and import all the slides from the old project into the new project. Here’s how: https://community.articulate.com/kb/user-guides/storyline-360-importing-slides-from-other-storyline-projects/1140094
Good luck
Thanks for your reply, but I´m not sure if your issue relates to mine. To my knowledge (correct me if I´m wrong), the imsmanifest file is generated by Articulate when publishing something towards LMS. At least it is like that for me; imsmanifest files only exist in outputs I have generated towards LMS.
Could it be like that the imsmanifest.xml is removed when you extract the zip file? I have never heard about that, but it happens from time to time that Winzip (or similar program) delete what they consider to be suspected files. But I have no idea why the imsmanifest should be considered as suspected
