Forum Discussion
Error uploading Rise course to SABA
Hi - I have a client that uses SABA cloud, and they can't upload one of my courses. They get an error stating "Invalid content. Invalid manifest XML. Forward slash, Ampersand, left angle bracket or space in beginning or end in the identifier is not permitted." I looked in manifest XML, and don't see any of those characters. They do report that they've been able to upload a Rise course before.
Any ideas on how to resolve? I tried republishing, and that didn't work.
Thanks, Steve.
21 Replies
Hi there, Steve. Do you know if there are any PDFs or other assets that have symbols in the file name? We recently released a fix for an issue we had with file names, but you may need to remove and re-attach the file if you added it prior to the fix.
Let me know what you think! We can also have a closer look at the output if you share it privately with us here.
Hi Crystal -
there's one PDF: DR Glossary.pdf. Would the space cause an issue?
There's videos and storylines too, but I can't see their file names.
I uploaded the file and submitted a case at your link.
Thanks, Steve.
Thanks for sharing, Steve. We didn't see anything that looked problematic in your output. If you reach out to SABA support, let us know if they have any insights.
Heard back from my client. They found a file that had name starting with a symbol (-). This is a file name assigned by Articulate Rise when I publish the course. The client changed the file name to remove the symbol and was able to upload it to their SABA LMS successfully.
Is there a way to prevent Rise from assigning file names that start with a symbol?
Is there a way to find all the instances of a file name in all the output created when publishing in Rise?Thanks for the follow-up, Steve. We found an indication that some LMS servers won't accept that symbol as the first name of a file. I'm going to meet with our team to see how we can improve the file encoding during the publishing process to avoid this issue. I don't expect an immediate change, but we'll keep you posted.
If you suspect this issue in other output, you can unzip and open the output folder, and look in the
scormcontent > assetsfolder. I arrange the files in that folder by name so that any files that start with symbols will be listed first. The assets will also be listed in the lmsmanifest.xml.I'm sorry the file naming caused this issue for you!
Hi Steve! Quick update -- we've updated our encoding so that you shouldn't run into this issue anymore. Let me know if I can help further!
Hello,
I'm testing rise compatibility with Saba LMS. I've uploaded a scorm 1.2 course with no problem. But, I'm trying to upload the web export, but I get an error that the index file is missing. I have checked and the index file is in the folder. Do you have an idea about this issue?
If you are using a LMS you should publish for LMS.
Web export is intended for use outside of a LMS.
I know this is an older post but it helped me. I am testing a new Rise course and I am finding that it is randomly naming assets with dashes as the first character still. Saba obviously doesn't like this and will throw an error when uploading it. I can get around it by changing the filename in the manifest and the asset folder but now I am dealing with those files being broken links or images. Not sure where else I need to change the filenames.
Based on this post it seems like your encoding was updated to address this. Has something changed or is this a new issue?
Hi there, TJ. Would you mind exporting a course where this has happened, or otherwise privately sharing an exported SCORM package with us that is giving you trouble? You can use this link to share the file and start a case, and we'll delete it once we're done troubleshooting. Thanks!
Sure thing. I still have a copy that won't import into Saba. When looking at this ones manifest, line 118 has a file that starts with a dash. I will use the link you provided to upload it. Thanks!
Just to add to this if you are experiencing issues. We had Saba look into this and they suggested a potential fix of extracting and rezipping the course files. I was skeptical at first, but I tried it and it worked for me. I also did not have to change any filenames starting with special characters.
Hi, everyone.
I have some great news to share!
We just released the fix for the issue about being unable to upload a Rise 360 SCORM package into an LMS when an asset file has a symbol in its filename.
Since Rise 360 is a web app, there's nothing to install! New features and fixes are available immediately.
Please let us know if you have any questions by posting here or by reaching out to our Support Engineers directly.
Having this same issue with SABA and a RISE Scorm - but also don't see any asset issues. Does anyone see anything worth mentioning here?
Help!
Thanks!
I had a similar issue and when reaching out to Saba support, they were able to get it to upload by unzipping and then rezipping the contents. There was no need to alter the manifest file. I have also solved the issue before by renaming assets too that had these special characters, but that was prior to Articulate's latest update.
