

When I try to take Captivate SCORM course on some Learning Management Systems (LMS) which support both SCORM and AICC, Captivate SCORM course freezes on load with “Loading…” screen and does not move forward. This is usually seen with only few LMSs which support both SCORM and AICC. When I look at the SCORM API calls to LMS, I don’t see Initialize API being called at all. When dug deeper, I found that Captivate course was loaded as SCORM course by LMS but course was trying to make AICC calls.
The reason for this was that LMS was also sending AICC parameters in course URL though course was loaded as a SCORM course. In Captivate SCORM HTM, all the course URL parameters are propagated to Captivate SWF along with SCORM type and SCORM version. If the URL parameters contain AICC parameters then Captivate SWF tries to make AICC calls. So, solution to this problem is just not to propagate the course URL parameters to Captivate SWF. This requires simple SCORM HTM template change.
Please follow the steps described below:
1. Please go to $CaptivateInstallFolder/Templates/Publish/SCORM/1_2
2. You will find Default.htm and Custom.htm
3. Open the Default.htm file.
4. Find the following line of code:
strURLParams += (strURLParams==””?”?”:”&”) + “SCORM_API=” + g_zAPIVersion + “&SCORM_TYPE=” + g_intAPIType;
5. Change that line of code to this:
strURLParams = “?SCORM_API=” + g_zAPIVersion + “&SCORM_TYPE=” + g_intAPIType;
6. Save the html file.
7. Publish the course now and use the SCORM package on LMS.
Repeat the same steps for SCORM 2004 if required. Updated HTM template for SCORM 1.2 is attached
This issue will be fixed in the upcoming version of Captivate.
When I try to take Captivate SCORM course on some Learning Management Systems (LMS) which support both SCORM and AICC, Captivate SCORM course freezes on load with “Loading…” screen and does not move forward. This is usually seen with only few LMSs which support both SCORM and AICC. When I look at the SCORM API calls to LMS, I don’t see Initialize API being called at all. When dug deeper, I found that Captivate course was loaded as SCORM course by LMS but course was trying to make AICC calls.
The reason for this was that LMS was also sending AICC parameters in course URL though course was loaded as a SCORM course. In Captivate SCORM HTM, all the course URL parameters are propagated to Captivate SWF along with SCORM type and SCORM version. If the URL parameters contain AICC parameters then Captivate SWF tries to make AICC calls. So, solution to this problem is just not to propagate the course URL parameters to Captivate SWF. This requires simple SCORM HTM template change.
Please follow the steps described below:
1. Please go to $CaptivateInstallFolder/Templates/Publish/SCORM/1_2
2. You will find Default.htm and Custom.htm
3. Open the Default.htm file.
4. Find the following line of code:
strURLParams += (strURLParams==””?”?”:”&”) + “SCORM_API=” + g_zAPIVersion + “&SCORM_TYPE=” + g_intAPIType;
5. Change that line of code to this:
strURLParams = “?SCORM_API=” + g_zAPIVersion + “&SCORM_TYPE=” + g_intAPIType;
6. Save the html file.
7. Publish the course now and use the SCORM package on LMS.
Repeat the same steps for SCORM 2004 if required. Updated HTM template for SCORM 1.2 is attached
This issue will be fixed in the upcoming version of Captivate.
You must be logged in to post a comment.

- Most Recent
- Most Relevant
Hi Amanda,
Can you explain the exact issue that you are facing and on which platform. Please specify all the details and drop a mail to agnihotr@adobe.com.
We will surely be able to help you.
Regards
Shriyansh
Adobe Engineering Team.
I’ve had this problem, it was just affecting me, my other colleagues it was working fine. I’m using Cpativate 5.5, Totora/Moodle, IE v8.
The solution for me was to go into Totora, there is a record of who had taken the SCORM module, and I deleted my record. I tried it again and it worked.
I have a Captivate 5.5 course for SumTotal Scorm 2004. Required to use bookmarks. After launching successfully the first time, then closing the course midway through, the relaunch gives a blank white screen. No loading, no nothing. Code for default.htm and custom.htm matches above fix so that’s not the issue. Has there been an update to this issue?