I'm trying to publish a course that I created in Rise. I've exported the course as a scorm 1.2 file. I've tried in multiple browsers now, and I've tried exporting the course multiple times. I get the following error message:
"Multi standards (AICC/ SCORM/ xAPI) are not allowed in one file. Please create a separate file per each (AICC or SCORM or xAPI) and try again."
Any advice on how to successfully upload this course?
Darren, Are you going to Convergence (I'm not but people from my team are)? It would be great if folks from here could coordinate in some fashion at that conference to get CSoD's attention regarding this issue.
Thanks for sharing your experience, folks. Keep us posted on what you find out from Cornerstone!
In the meantime, Steve's workaround above will help you upload your content in LMSs that are picking up on the tincan.xml file in your Rise 360 output. Thanks for sharing, Steve!
I noticed this as well. I have some courses that I loaded in the past with storyline blocks that worked fine. Was there an update from Cornerstone or Articulate that was responsible?
I also use Cornerstone, this is only affecting us for Rise Exported courses. Normal Articulate courses are working fine. We have a ticket open with Cornerstone. Will keep you all posted for feedback.
Update from Cornerstone:
The error is triggered by the presence of tincan.xml traces in the Storyline blocks. Since Tincan (xAPI) is now a supported package type in Content Uploader, the system will not upload the course with multiple types detected (SCORM and xAPI). I have attached a Knowledge article covering this in further detail.
Error received: "Multi standards (AICC/ SCORM/ xAPI) are not allowed in one file. Please create a separate file per each (AICC or SCORM or xAPI) and try again."
Reason
The Content Uploader no longer allows for more than one launch type to be uploaded in one course zip.
The reasoning behind this is when creating a new version to a course that has multiple launch types, there are many points during the re-version process which may cause an unsuccessful re-version of the LO.
As the error code indicates, we do not allow for more than one launch type to be uploaded in one course zip file. This was effective in the February release.
Solution To upload the course you will need to separate each standard (AICC/SCORM) in a different zip.
Articulate Rise - Storyline Blocks Courses that were created using the Articulate Rise authoring tool can get this error when uploading. The error is triggered for courses that are using storyline blocks inside them.
Articulate exports the course in a SCORM protocol however, the storyline blocks are exported in the TinCan (xapi) protocol - causing the course package to have both SCORM and TinCan protocols inside which triggers the error.
Solution
1. In the course package (unzipped) search for all the files that are "tincan.xml" and delete them.
2. Open the imsmanifest.xml file in the root folder and search for "tincan.xml" and delete all <file> tags to avoid the missing resources error.
Hi Angie. I had uploaded one earlier that worked fine as well, and I was using the "Course Uploader" in all cases. Luckily Steve's workaround works for me — thank you Steve :-)
Of course. I asked them if this was a long term solution or not and got this response:
"In regards to the solution, Articulate is said to be working on a fix on their end on exporting the Storyline blocks in a different manner. The current workaround is to be used in the meantime."
I just published 4 Rise courses in Cornerstone, all with similar content and no Storyline blocks. Three published with no problem, and for one I had to remove the tincan file. Thankfully that worked, but this isn't consistent at all!
Hello, Anyone out there loading RISE files into Fazzi? If so, how did you get the files to work for loading. I have tried the insructions that I used for Cornerstone and they are not working. What am I missing? Thank you!
We are experiencing the same issues with Cornerstone and currently have an open case which has let me to this discussion. Thank you for sharing your response Kevin. It more information than I was given.
I have the same problem. Work around is fine but if you are uploading 10-15 modules at a time it is not feasible. I hope that Articulate will be able to help as I somehow get the impression that Cornerstone is not really interested - this worked before, its just since the last updates from cornerstone that this has happened? Thanks articulate for at least trying. Appreciate it.
Hey everybody. I'm excited to let you know that we just released update 29 for Storyline 360! Here are all the details.
One of the fixes addresses an issue where a Tin Can file was showing up in Rise 360 courses that included a Storyline block, causing errors when uploading SCORM packages to your LMS.
Here’s how you can update Storyline 360. After updating, please republish your Storyline project to Review 360 as HTML5-only, and reinsert your Storyline block in Rise 360. Let me know how you make out!
Hi everyone. I have used the "fix" Joseph graciously shared. We'll be sure to use that for our upcoming courses, but I noticed in my colleague's recent file I am working on, there are no storyline blocks or TinCan protocols in this particular file. Does anyone know a great troubleshooting way to solve this concern? We are also using Cornerstone LMS. We have no issues playing it on the RISE cloud.
Hi Alyssa! Thank so much for responding. When I use giffs or videos within RISE. It works fine on the RISE cloud network with no issues. Whether I publish it as a 1.2 SCORM or 2004 SCORM, it will not upload the published course properly. I noticed if I removed all of the videos and giffs attachments within the course, it plays properly. Do you know if there is a best practice regarding video size and the size of the giffs used within a RISE published course? Is there a best practice to how many videos and giffs can be used in one RISE published file? I have the screenshot of the error message I received from our Cornerstone LMS site when it contained the giff files.
Hi there. Technically this file was created by my colleague. I'm not comfortable sharing that without his permission and he is out of the office for a few days. I did wonder if the team has any best practices regarding how many videos and giffs can be used in one published RISE export file?
50 Replies
Darren, Are you going to Convergence (I'm not but people from my team are)? It would be great if folks from here could coordinate in some fashion at that conference to get CSoD's attention regarding this issue.
Thanks for sharing your experience, folks. Keep us posted on what you find out from Cornerstone!
In the meantime, Steve's workaround above will help you upload your content in LMSs that are picking up on the tincan.xml file in your Rise 360 output. Thanks for sharing, Steve!
I noticed this as well. I have some courses that I loaded in the past with storyline blocks that worked fine. Was there an update from Cornerstone or Articulate that was responsible?
CSoD updated their "Course Publisher" to "Course Uploader" which has a very different look-and-feel and evidently different functionality
I also use Cornerstone, this is only affecting us for Rise Exported courses. Normal Articulate courses are working fine. We have a ticket open with Cornerstone. Will keep you all posted for feedback.
Update from Cornerstone:
The error is triggered by the presence of tincan.xml traces in the Storyline blocks. Since Tincan (xAPI) is now a supported package type in Content Uploader, the system will not upload the course with multiple types detected (SCORM and xAPI). I have attached a Knowledge article covering this in further detail.
Error received: "Multi standards (AICC/ SCORM/ xAPI) are not allowed in one file. Please create a separate file per each (AICC or SCORM or xAPI) and try again."
Reason
The Content Uploader no longer allows for more than one launch type to be uploaded in one course zip.
The reasoning behind this is when creating a new version to a course that has multiple launch types, there are many points during the re-version process which may cause an unsuccessful re-version of the LO.
As the error code indicates, we do not allow for more than one launch type to be uploaded in one course zip file. This was effective in the February release.
Solution
To upload the course you will need to separate each standard (AICC/SCORM) in a different zip.
Articulate Rise - Storyline Blocks
Courses that were created using the Articulate Rise authoring tool can get this error when uploading.
The error is triggered for courses that are using storyline blocks inside them.
Articulate exports the course in a SCORM protocol however, the storyline blocks are exported in the TinCan (xapi) protocol - causing the course package to have both SCORM and TinCan protocols inside which triggers the error.
Solution
1. In the course package (unzipped) search for all the files that are "tincan.xml" and delete them.
2. Open the imsmanifest.xml file in the root folder and search for "tincan.xml" and delete all <file> tags to avoid the missing resources error.
3. Zip the course and upload.
Hi Angie. I had uploaded one earlier that worked fine as well, and I was using the "Course Uploader" in all cases. Luckily Steve's workaround works for me — thank you Steve :-)
Thanks, Joseph, for sharing the Cornerstone response. I've added their information to our report.
We're continuing to see what we can do on our end to make this easier for our affected customers. I'll share an update as soon as I can!
Of course. I asked them if this was a long term solution or not and got this response:
"In regards to the solution, Articulate is said to be working on a fix on their end on exporting the Storyline blocks in a different manner. The current workaround is to be used in the meantime."
This post was removed by the author
I just published 4 Rise courses in Cornerstone, all with similar content and no Storyline blocks. Three published with no problem, and for one I had to remove the tincan file. Thankfully that worked, but this isn't consistent at all!
Hello, Anyone out there loading RISE files into Fazzi? If so, how did you get the files to work for loading. I have tried the insructions that I used for Cornerstone and they are not working. What am I missing? Thank you!
We are experiencing the same issues with Cornerstone and currently have an open case which has let me to this discussion. Thank you for sharing your response Kevin. It more information than I was given.
Yes Steve's solution worked for me as well-Thanks!
and thanks Joseph for the why behind the issue.
I have the same problem. Work around is fine but if you are uploading 10-15 modules at a time it is not feasible. I hope that Articulate will be able to help as I somehow get the impression that Cornerstone is not really interested - this worked before, its just since the last updates from cornerstone that this has happened? Thanks articulate for at least trying. Appreciate it.
I hear you, Debbie. We'll keep you posted!
Hey everybody. I'm excited to let you know that we just released update 29 for Storyline 360! Here are all the details.
One of the fixes addresses an issue where a Tin Can file was showing up in Rise 360 courses that included a Storyline block, causing errors when uploading SCORM packages to your LMS.
Here’s how you can update Storyline 360. After updating, please republish your Storyline project to Review 360 as HTML5-only, and reinsert your Storyline block in Rise 360. Let me know how you make out!
Thanks, Crystal, That's Awesome! Thank you for the update.
We are testing this now...has anyone else tested yet?
The updates work perfectly! Thanks Articulate. I tried it out the minute Articulate let us know.
Thanks Debbie!
Hi everyone. I have used the "fix" Joseph graciously shared. We'll be sure to use that for our upcoming courses, but I noticed in my colleague's recent file I am working on, there are no storyline blocks or TinCan protocols in this particular file. Does anyone know a great troubleshooting way to solve this concern? We are also using Cornerstone LMS. We have no issues playing it on the RISE cloud.
Thanks.
Hi John,
Can you tell us more about what you're seeing in Cornerstone? Also, what LMS standard did you use when publishing?
Hi Alyssa! Thank so much for responding. When I use giffs or videos within RISE. It works fine on the RISE cloud network with no issues. Whether I publish it as a 1.2 SCORM or 2004 SCORM, it will not upload the published course properly. I noticed if I removed all of the videos and giffs attachments within the course, it plays properly. Do you know if there is a best practice regarding video size and the size of the giffs used within a RISE published course? Is there a best practice to how many videos and giffs can be used in one RISE published file? I have the screenshot of the error message I received from our Cornerstone LMS site when it contained the giff files.
Hi John!
Would you mind sharing one of the troublesome output files with our team? We'd like to test the upload from our side.
If that works for you, you can share your file by clicking here. We'll delete it when we're finished testing.
Hi there. Technically this file was created by my colleague. I'm not comfortable sharing that without his permission and he is out of the office for a few days. I did wonder if the team has any best practices regarding how many videos and giffs can be used in one published RISE export file?
Thanks again for always being responsive.
This discussion is closed. You can start a new discussion or contact Articulate Support.