Hi All,I have a client who is having an issue when re-visiting a Rise course. It works perfectly and as expected when testing in SCORM cloud.Oddly the course launches fine but on re-visit they just get a blank screen.One of the difficulties is that I don’t have any access to the system to see what is happening in real time to further debug. My only real course of action was to get a bit more system specific details to see if anything here would be an issue, they have come back with the following:LMS: Kallidus Version 10.1.12Tested on desktop PC running Windows 7Browser: IE 11Pop-Up Blocker: Off Version of JavaScript: Version 8 This all looks fine and in line with the Rise browser compatibility specs.Since this runs all fine in SCORM cloud I’m at a bit of a loss as to what the issue could be. Has anyone had any similar issues and any resolutions? Or areas for the client to look into further their side of things? Thanks

Nicole, in short, Rise + Suspend Data = No go. My team and I learned this the hard way and it was a huge headache for some of the projects we where working on back then. We came up with different workarounds this issue: A) We broke-up larger RISE modules into smaller chucks without any sidebar menu. We uploaded the smaller sections into the LMS and used the divider blocks with a shortcut to start the next Rise course. From a user experience, the LMS and RISE would work like one system, however, for clients using Agile development, a small update in one module would only reset a learner to the beginning of that micro lesson, not the entire course. B) For meduim-sized courses where we wanted to keep the sidebar navigation AND the updates where minor or non-critical: We would hide the course from the LMS catalog and create a new course. This meant any current learners would still be able to complete the course without losing their progress and any new learner would be assigned the latest version. I know these are not optimal solutions, however, once we got the system and process down, we were able to keep the courses in RISE, and leverage some of the advantages this tool offers. Hope this helps. Mauricio

I am experiencing this issue too (in Totara) and just read this entire thread. Looks like the only solution proposed so far is from David Lockett -- "find an old Rise course (pre-Nov update) copy out the scorm driver and use this in any new packaged content." Is Articulate working on a fix?

Hi everyone, Was there a solution to this problem? I have the exact same issue with my Rise file. I have updated content and republished for scorm 1.2. I have uploaded the zip to the course and all i get it a blank screen. I wanted to see whether the issue lay only within an existing course so i created a new mock course and uploaded the exact same file - it worked perfectly. I cant erase learner records, etc so what would my solution to this problem be? Thank you

Hi Katie, this took a long time to solve and was found after much testing by our LMS provider (Kallidus). For us it turned out that the problem was caused after Articulate made a change to the Scorm driver file in the last Rise update (which I think was around November 2020). Our LMS couldn't handle the change (where a course was published as 1.2 but was being detected as 2004) and therefore anything that was packaged with the new driver would return a blank screen on second launch. The fix was to simply find an old Rise course (pre-Nov update) copy out the scorm driver and use this in any new packaged content. It iss a complete pain having to swap out the scorm driver every time we create or update some Rise content, but we don't have the issue any more. Incidentally there's a few mentions in this thread of testing in scormcloud. However our LMS provider stated that this doesn't fully test the granular detail and functionality of courses in the same way that a commercial LMS does, so it's a litmus test at best. I hope this helps.

Hi Chris, if Kallidus v10.1.12 is also known as Classic, then it's the same issue as we had. We are currently using Kallidus Classic (sorry only know it as this rather than the version number). This took a long time to solve and was found after much testing by Kallidus. For us it turned out that the problem was caused after Articulate made a change to the Scorm driver file in a previous Rise update (which I think was around November 2020). Kallidus couldn't handle the change (where a course was published as 1.2 but was being detected as 2004) and therefore anything that was packaged with the new driver would return a blank screen on second launch. The fix was to simply find an old Rise course (pre-Nov update) copy out the scorm driver and use this in any new packaged content. It is a complete pain having to swap out the scorm driver every time we create or update some Rise content, but we don't have the issue any more. It might be worth looking in to. My previous thread on this is https://community.articulate.com/discussions/rise-360/rise-blank-screen-issue?page=2#reply-725609

Rise blank screen issue | Articulate

KarlMuller
Community Member
4 years ago
Working with our LMS vendor, we determined that that when we uploaded the new version of the course some files that were in the ZIP file were not copied to the server.

Using the same SCORM file, we repeated the upload and that resolved the issue.
- DavidLockett
  Community Member
  4 years ago
  Thanks Karl.
  
  Do you know whether it was an issue with the zip file being incorrectly generated from Rise or an issue with the transfer of the files to the LMS server? Given that you must have been uploading new and updated content for quite a while, it's odd that suddenly a few files weren't being transferred.
  
  In the mean time I'll make this known to our LMS provider and see if this works.
  - KarlMuller
    Community Member
    4 years ago
    Hi David,
    
    The SCORM file was generated correctly.
    
    What happened in this case, a single file was not copied over from the SCORM package to the LMS.
    
    main.bundle.js was not copied over for some reason.
AndrewGlennie-3
Community Member
4 years ago
Thanks David. Unfortunately the modules we are having problems with are developed post November 2020 so your solution isn't going to fly. Think Articulate need to revert to the old driver.
AndrewGlennie-3
Community Member
4 years ago
Pleased to be able to say that we've resolved the issue by publishing the Rise modules using SCORM 2004 2nd edition. The problems appeared to come from publishing as 4th edition. Not sure why though.
cvsankarsdesign
Community Member
4 years ago
I still have this issue. I ended up deleting the SCORM activity in Moodle and publishing it again. I think that this situation is just stupid. Most teams just want to make the content updates in RISE and replace the SCORMs on their LMS.
- Renz_Sevilla
  Staff
  4 years ago
  Hi Candice! Sorry to hear you had some trouble updating your course on your LMS.
  
  We'd like to take a look at your course file and help if you're still experiencing this on Moodle. Could you please open a case and submit the files at this link?
  - MichelleKotulsk
    Community Member
    3 years ago
    We are still having this issue on Moodle, I have a ticket and I was told "reboot your machine" "clear your cache", This is way bigger than an "reboot".
JacquelineCarde
Community Member
4 years ago
I am having the blank screen issue only with some learners too. My Rise course was updated and the SCORM zip file replace several times, but all of that occurred BEFORE any learners were assigned. It occurs regardless of browser, and I am able to recreate the issue on these specific user accounts when I emulate the learner using our "login as" feature in our LMS.

It has also occurred when a learner exits the course before completing it and attempted to resume the course.

I found that deleting the user's scorm attempts resolves the issue. Hoping you have a solution.
- hazelB
  Staff
  4 years ago
  Hi Jacqueline!
  
  So sorry some of your learners are encountering the issue. Please open a case with us here so that one of our technical support engineers can take a look at it.
  - JacquelineCarde
    Community Member
    4 years ago
    Thank you. Submitted this morning: case number 02874962
ChrisWant
Community Member
4 years ago
Hello all
We are also having this issue, on multiple browsers, but only with some colleagues.
It is a fresh course on LMS with no revisions.
Issues on Chrome, Edge and IE.
Any ideas please?
Many thanks
- Renz_Sevilla
  Staff
  4 years ago
  Hi Chris! If this is happening on a brand new course that didn't overwrite the spot of an old course, could you please share a copy of this file with us?
  
  Please note the exact browser version numbers where this is happening for your colleagues. You can submit the published Rise course files here.
  - LoriPyska-539f5
    Community Member
    3 years ago
    Hello Renz,
    
    I've been following this thread and it looks like no one from Articulate has responded in a while, hence I'm replying directly to you. I just loaded a new RISE module to our LMS (Successfactors) in hopes that this issue had been fixed, and just like the others, it opens to a blank screen. Can you recommend specific settings, etc. for using Chrome to run the modules. If not, is there an easy way to convert RISE to Storyline or another elearning platform? Thank you for any help that you can provide.
ChrisWant
Community Member
4 years ago
Thanks all.
Will open a case as am concerned that this cannot be replicated by me and do not want >2,000 colleagues potentially having this issue.
LoriPyska-539f5
Community Member
4 years ago
Has any more information been provided for this? We are having this issue as well. I opened a case (02881580) but after testing in Scorm Cloud, I was directed to work with Successfactors to resolve. I have found that Safari works, but Chrome and IE do not.
JerryDonney
Community Member
4 years ago
Also experiencing this blank screen just recently from LMS launch. Any resolution? Was a case opened by anyone previously?
- LoriPyska-539f5
  Community Member
  4 years ago
  Hi Jerry, unfortunately, my case was never resolved. I was hoping to see a fix here, but it looks like there's been no progress yet.
JacquelineCarde
Community Member
4 years ago
I opened a case, but didn't really get a resolution. The best we could do was to delete the user's previous SCORM attempts, and that seemed to resolve it. Most of the people who experienced the issue had not started the module due to the blank screen issue, so deleting their attempts was not a huge deal.