Forum Discussion
Error initializing communications with LMS
When uploading published Rise courses to SCORM Cloud for testing, I'm getting an "Error initializing communications with LMS" error message on launch. I get the same error with any Rise course I publish to SCORM 1.2. (AICC seems fine.)
I've submitted a support ticket, but wanted to see if anyone has any tips.
4 Replies
Hi Traci,
Good call on opening a support ticket. It looks like your course works just fine when uploaded to SCORM Cloud on our end. Here's the link to the course for your reference. Would you mind opening it to see if it works for you?
If you still get the same error when opening the link, please let us know and we'll continue troubleshooting the issue with you through the support case that you opened.
- ChanceHunter1Community Member
Were you able to find a solution for this? We are experiencing the same issue. (Our Rise courses run fine on SCORM Cloud too.)
Hi ChanceHunter1,
Sorry to hear you're also having trouble uploading Rise 360 content to your LMS.
I see that you've also opened a support case being handled by my teammate, Angelo. As he shared:
"I understand you are having issues launching Rise courses in SAP SuccessFactors. You mentioned that you are uploading the unzipped course files via FTP. This is something we do not recommend or support. If you publish a course for LMS distribution, we recommend uploading the original zipped file to your LMS platform. If you will be uploading your content via FTP, you may need to publish the course for Web distribution instead.
You mentioned that the original zipped SCORM package works just in SCORM Cloud, which means that there isn't an issue with how you published it or with the actual content. It may have just been the way it is being or has been uploaded to your LMS platform, which may be causing the issue.
At this point, I would suggest reaching out to your LMS administrator at SAP SuccessFactors to confirm if there's anything missing from the files you are uploading via FTP. Or if they have a different way, they can recommend to you how to upload the published output via FTP.
Let me know what they suggest or require, and I'll check it from our end".
It looks like Angelo's e-mail was sent on 01/21/26. It's possible it slipped by or was diverted to a SPAM folder. No worries! I've resent that email again, for your reference.
If you have any follow-up questions, feel free to reconnect with Angelo through your case!
- ChanceHunter1Community Member
I read the email. We've tried both uploaded methods with no success. Wondering if there was a tip or trick the OP could recommend since we're getting that exact same error.
Related Content
- 5 months ago
- 9 months ago