Rise Export (Scorm 1.2) not uploading into LMS

Seeing this too in Cornerstone OnDemand. 

I think the upload process in the LMS is being overly picky about the files contained in the zip. This is pretty annoying for publishers. The uploader should simply ignore any files within the zip if it's uploaded as a SCORM file, "Uploaded with Errors", rather than rejecting the file with a critical error. Here's how I am fixing it:

1) Unzip the SCORM file. 

2) Search the unzipped folder for tincan.xml. 

3) Delete the tincan.xml files that return in the search. 

4) Rezip the contents of the unzipped file, ensuring that the imsmanifest file is at the root of the zip.

** If you don't remove the tincan.xml files from the imsmanifest file, you'll get warnings for every missing file. Not a big deal. It'll still upload. 

The CSOD square dance. Less than fun. Glad there's always a way but weary of fighting with my tools. The above process will need to be done after every publish. Ugh... To be clear, the LMS should ignore these files. It'd be great if Rise would remove them at publish but this is an LMS fail.

Hi folks

Thanks for the steps above, but I just had a question. This just started happening for me yesterday and was only resolved by deleting the tincan.xml file as well as any references to tincan in the imsmanifest.xml file. Do you know if this is a problem when using Rise and Cornerstone that could be fixed?

Thanks

Mark

I am experiencing this same problem, but I was not having this same problem with the exact same course when I tested it last week.  This doesn't make any sense. 

Also I submitted a case to Articulate support on this, and their response was that the issue is with Cornerstone.

That makes sense since the files we're having issues with upload and work fine on scorm.com. I found that if I removed storyline blocks I could upload to Cornerstone. I know that's not a viable solution but it is a data point. I just was granted admin status with Cornerstone and will submit a ticket. I'll report here on what I hear back. 

Even I am facing the same issue in the Corner Stone LMS. I have a RISE course that is giving me the same error - 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. 

I have a storyline block in my course and I reckon this could be the reason for the error. My colleagues have uploaded their RISE courses on the same LMS and it worked for them. 

Would be great if you could provide a resolution soon.

Hi everyone. We are looking into this issue. I've tagged this discussion so I can update you with any changes!

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 got a response from Cornerstone and they are in insisting that there are two launch types in the zip file. I responded that this is not the case as reported back by scorm cloud. Steve's workaround does not work me.

Thanks, Crystal. 
Steve's workaround does work for me. Thanks alot for that, Steve.

Neha, Do you have storyline blocks in your course? I'm wondering why Steve's workaround works for some folks and not for others.

Thanks

Steve's work around works for me.  Anything with a Storyline block will contain tincan files in the zip.  You have to delete them, as well as their references in the imsmanifest file, in order to get things to load without an error.

Rise files with no Storyline block will load fine without any manipulation, from my experience.

Hi Maryanne,

Rise courses without Storyline blocks work fine for us also. For the course with Storyline blocks, I went in to the zip and deleted all instances of tincan.xml as per Steve's workaround. Is there anything else we need to delete?

Yes i do have a storyline block and the workaround worked perfectly fine for me. But I hope the team is working on a permanent solution.

 I also am not able to upload a rise (SCORM 1.2) into cornerstone LMS.  Just added the block, and went to test.  A previous version which was exactly the same without the block worked fine.

Having the same issue with Cornerstone. Hadn't seen this thread before I started my own:https://community.articulate.com/discussions/rise-360/storyline-block-and-lms-tracking-error. Course was working and uploaded earlier but when trying to update it with a new SL Block I get the critical error. Interestingly the course that was successfully uploaded a couple of weeks ago had SL Blocks in it. 

Do we have some idea of when this will be resolved? 

Hi Brett,

Did you try Steve's workaround above? I don’t currently have any updates on a fix, but you are now subscribed to this conversation which means as we share updates here, you’ll automatically be notified.

Let me know if there's anything else I can do to help. :)

Hi Allison,

I haven't tried Steve's workaround yet but will try to do it later today. I'll post back the results of that just for the record.

FYI...I'm currently working with Cornerstone support on this. No resolution yet, but here's hoping.  I'll keep the group in the  loop. 

Hi, Kevin,

Deleting the tincan.xml files will get it to a state where you're able to load it.  It will still receive error messages, but it will load and work.

If you want to eliminate all "Resource file is missing" error messages, you also need to delete any references to those files from the manifest file.  I have included instructions below.

Unzip the SCORM file.
Search the unzipped folder for tincan.xml.
Delete the tincan.xml files that return in the search.
Open the imsmanifest.xml file. (I use Notepad)
Search the imsmanifest.xml file for tincan.xml.
For each result, delete the entire < > line. (You should have the same number of lines in this file as you had individual tincan files to delete)
Save the updated imsmanifest.xml file.
Rezip the contents of the unzipped file, ensuring that the imsmanifest file is at the root of the zip.

That should remove all errors when you upload to Cornerstone.

Sounds good! :) 

Thanks, Maryanne!!!! I'll give it a try. Still in conversation with CSoD support.

FYI, Here is the response I got from Cornerstone:

"We are aware that Articulate courses that export as a SCORM course sometimes have storyline blocks inside the courses - these blocks are exported as tin tan in the SCORM package and we are currently blocking the option to have more than one protocol per package.

 The reasoning behind us blocking this option 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 and we would like to avoid as many errors in this case for the clients.

The course can be uploaded to SCORM CLOUD because it's more lenient than us, we have many compliance and security requirements that we need to uphold for the clients and mixing more than one protocol in a course can potentially create many versioning issues for our clients.

The suggested workaround in the article and in the URL you provided will work.

I've tested this and it seems there's no reason for the blocks to be exported in tin can if you can delete all trace of it and the course still runs as expected, I understood that Articulate are working on this issue and we will be monitoring any additional issues that might arise in the future."

I also just discovered this issue as I have just published a Rise file to Cornerstone and it has a Storyline block in it. I will actually be meeting Cornerstone next week so I will also bring it to their attention.