Storyline - SABA, Error on course complete.

Try turning off resume (unfortunately you'll lose the bookmark).  The resume data being sent to Saba is exceeding what it can handle.

http://www.articulate.com/support/kb_article.php?product=st1&id=jrrv9j8vulu0

Otherwise, see if you can use SCORM 2004, 3rd or 4th edition and you can probably keep resume on.

BTW, what version of Saba are you using?

Oh, man, I was hoping you wouldn't say that, Gerry.  I was the process as your eamil came through to remove the save state option.

We're on SABA 5.5.......

That's actually good.   Support for SCORM 2004 is better with Saba 5.5.

Do you have issues with SCORM 2004 with your Saba system?

We were on Saba 5.4 SP2, and even though it said it supported SCORM 2004, we were advised not to use.

I've tried Storyline content in a SCORM 1.2 and 2004 in a Saba 5.5 system  and everything seemed fine, but I've never tested the resume limits.  The only issue I had was not being able to use one of player templates with SCORM 2004.

I'm told we only have 1.2.....  I feel like I live in the penatly box as I seem to push the limits of everything.....So thankful for the community as sometimes I feel like I have three eyeballs when I try to tell my story. 

I don't seem to have the same errors the tester does...which is little (OK a lot) frustrating.  Darn testers! 

Hmm, I'd push back on that. 

My memory may be faulty on this but once you got SCORM set up it should be able to support both.  Just can't remember if there was a configuration setting or not to "turn on" support for SCORM 2004 or if it was automatic once SCORM was working.

If a configuration setting that's no great effort to turn it on--unless the powers that be require extensive testing.

Just an update Gerry.....I was able to get it to pass by resetting each page to the initial state.  I still have bookmarking, but not the save state. 

As for the 2004, I pushed, but I guess SABA is telling us that they don't recommend using 2004.  Just for my sanity, I published and tested the 2004 file and it worked...without any changing to the save state option. 

Good times....

Cool--thanks for the update! 

Hi to all, 

I have similar issue with  SetValue("cmi.suspend_data"). Actually, I am having an issue with bookmarking features. My client wants to bookmark learner progress so "always resume" is enabled in storyline. But, since my course is developed in Chinese language, bookmarking isn't working and I am receiving an error like this:

LMSSetValue("cmi.suspend_data",
"2o748060ji1001011a0101201011~2O6g$$$$$$$$100000V71^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1
介绍cIntroduction1^2d11^n5Y4t1PudRCF.6bKyKbQfrGp1^1^000000000") has been invoked.
LMSSetValue() finished unsuccessfully.
ERROR: The data model element value contains non-ASCII characters.

Does anyone have any solution for this. Is that something I can fix in storyline regarding this?
My LMS is Saba.

Thanks, 

Hi Rizah,

This forum discussion is a bit older, so I'm not certain that folks are still subscribed or that it's the same issue or situation. Have you looked at testing it in SCORM Cloud in addition to Saba? I ask as it's a good way to test and confirm if the issue is something within the LMS or how Storyline is dealing with the content. This article will assist you with walking through the testing at SCORM Cloud. 

Hi Ashley, 

Unfortunately, My SCORM package is too large for uploading it on SCORM cloud,.. I sow similar issues here so I thought maybe someone can suggest a solution.

Cheers,

Hi Rizah,

If you'd like our team is happy to upload to our test account - we've got a bit more than 100MB of space. :) 

You can share it with us here. 

Thank you Ashley, but unfortunately, I don't have permission from my client to upload it. I really appropriate. 

By chance, are you using checking questions or a quiz?

If you are, for each question, try taking the question text box off the slide and replace it with all English words.  Then insert a text box on the question slide with the question in Chinese.

That might work.

Thanks for that suggestion Gerry - is it something you've seen in terms of Chinese characters in a scorm file within Saba? We've seen issues with the course title - but not the question title.

Thanks Garry. You are probably right. Since my course is full of different custom made interactions, I difficulties to find where are these causing problem slides. I have good error logo from Saba and it looks like this:

"LMSSetValue("cmi.suspend_data",
"2o748060ji1001011a0101201011~2O6g$$$$$$$$100000V71^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1
介绍cIntroduction1^2d11^n5Y4t1PudRCF.6bKyKbQfrGp1^1^000000000") has been invoked.
LMSSetValue() finished unsuccessfully.
ERROR: The data model element value contains non-ASCII characters.
LMSSetValue("cmi.suspend_data",
"2z76807060on1001111f010120101101111~2S6g$$$$$$$$100000V71^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^
模块 1（共 5 个模块）5概述和目标1^2j11^n5Y4t1PudRCF.6Tb7RfiHbWw1^1^000000000") has been invoked.
LMSSetValue() finished unsuccessfully.
ERROR: The data model element value contains non-ASCII characters.
LMSSetValue("cmi.suspend_data",
"2C7880706090ts1001013k01012010110111101013~2O6g$$$$$$$$100000V71^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1
模块 1（共 5 个模块）2教程1^1c1^n6XdsSRFdoZM.5YvCYeJdM1f1^1^000000000") has been invoked.
LMSSetValue() finished unsuccessfully.
ERROR: The data model element value contains non-ASCII characters.
LMSSetValue("cmi.suspend_data",
"2L7a80706090a0yx1001113p0101201011011110101301113~2Q6g$$$$$$$$100000V71^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^
模块 2（共 5 个模块）4标题屏幕1^141^n6XdsSRFdoZM.61LeHN7hadU1^1^000000000") has been invoked.
LMSSetValue() finished unsuccessfully.
ERROR: The data model element value contains non-ASCII characters.
LMSSetValue("cmi.suspend_data",
"2T7c80609070b0a0DC1001213u010120101101111010130111301213~2R6g$$$$$$$$100000V71^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1^1
模块 2（共 5 个模块）5概述和目标1^1t1^n6XdsSRFdoZM.6KVsAXS3CI91^1^000000000") has been invoked.
LMSSetValue() finished unsuccessfully.
ERROR: The data model element value contains non-ASCII characters."

Its seems like  slides where I am facing the problem.

Just something I've noticed sometime with interaction title text is in the suspend data.  Instead of seeing compressed data, I've part of my slide text a couple of times.  (I'm testing for long SCORM 1.2 courses to be sure resume data doesn't go beyond 4096 characters.)

So I made a wild swing for the fences with the suggestion. :)

Have not worked with a Chinese course yet.  Just one Japanese course last month and that one had completion by number of slides viewed.  And bookmarking seemed to work fine.  Whew . . . 

Hey, if the suggestion works - it's not that wild. :) 

Keep us posted if that helps you out Rizah, and perhaps others in the community will have some other ideas to share here as well. 

Hi to all. At the and we found a solution. Here's the explanation:

In order to bookmark content , Articulate Storyline tends to send data to an LMS field called “suspend_data”. Bookmarking entails more than just resuming where a learner left off during subsequent launches, it also includes remembering how learners answered questions, how many times they took quizzes, etc. Because of this, the data that is written to the suspend_data field may include text that appears on the screen or in the project.
Articulate Storyline projects that include double‐byte characters may include those characters in the suspend_data field when communicating with an LMS. Whether it’s a configuration issue, or a database issue, SABA does not seem to support storing double‐byte characters in the database for suspend_data strings that contain double‐byte characters.

The solution is to compress the strings before sending to SABA, and then to decompress them after retrieving them from the database (before passing to the content).

Thanks so much for popping in to share with everyone Rizah :)