Java.Lang.Exception

Wish I had a solution for you. We're using Captivate and loading content into Saba via I.E. 9. I'm getting the same error. Will post more if I find a solution.

After uploading a project (about 3 mb in size), I received the Java.Lang.Exception: Failed to get cmi entry error when I attempted to preview the content. The error subsided after I logged out of Saba, waited about 5 minutes and logged back in again. I did not need to re-load the content.

I believe this error is encountered if you attempt to view content published to Saba before the content is fully uploaded to the Saba server. Typically, there isn't much of a delay, but our Saba server seems to be slower than usual today. 

Hi Karessa, 

You may want to review the troubleshooting steps here on working with your LMS, specifically even testing it within SCORM Cloud. 

We're currently on update 4, so if you're able to update you may want to and resolve any other conflicts. 

Hello! Our team found a solution to this problem and we wanted to share it in case anyone else has the Saba LMS and experiences this error.

The error that students will sometimes get when trying to access a course in Saba is:

Java.Lang.Exception: Failed to get cmi entry.

The solution is to click Yes when you are uploading course content and Saba asks if you want to clear the records. Normally we click No because we want to preserve the data, but something about keeping everything that way confuses the systems when the students try to access Storyline courses. I wish I could give a less convoluted solution, but that is about all I understand about it. Anyway, it works!

Thanks Karessa! 

Ashley,

I'm afraid that doesn't apply in OUR situation. I get this error regardless of whether I hit OK or cancel on upload. I get this error pretty frequently, both as content admin in saba and as an end user, but I haven't been able to find out much about it.

Hi Martin and welcome to Heroes!

Have you checked in with your Saba team as well? It seems the issue only occurs within the Saba environment (you could confirm this by testing it at SCORM Cloud which is a great, industry standard for testing Scorm content).

Also, what update of Storyline are you using for the course you've created? We're currently on update 5, and it's worth checking that you're using the most recent update.

Ashley -- the course runs fine in SCORM cloud, but of course that doesn't buy us anything because the issue is with the attempts being recognized and the SCO status and transcript in Saba. Before I can take this up with Saba or our hosting company, I need to validate that I've taken the steps to ensure it's not content-related. I was just responding to Karessa's comment that the error crops up regardless of how the import question is answered. -Marty

Hi Martin,

If it works as expected at SCORM Cloud, I'd assume it wasn't the content or anything specific in the Storyline published output. You may want to send Karessa a private message as well to see if she has any additional light to shed on the issue from the Saba side of things

Thanks Jane for sharing here - and as you can see this thread is a bit older, so I'm not certain that folks are still subscribed. I'm certain though as you found this thread, others may come upon it too so it's always helpful to share your solutions here.