Skip to main content
K
kiva_79
Participant
April 20, 2018
Question

Captivate 9 course loading blank screen on Citrix Desktops

  • April 20, 2018
  • 1 reply
  • 256 views

Assessment questions created on Captivate 9 throws a blank screen intermittently and does not appear to load the radio button controls. From here on none of the button works and users have to completely exit out of the course in order to retake it. The users are taking the course from the Citrix desktops. The desktops are restricted with no access to F12. At the point where the course is getting stuck there does not seem to be any LMS call. This issue is seen both with a single server or multiple servers (two) on F5 load balancer. Load Balancer is set to Cookie persistence.

Have anyone faced a similar problem and if so is there any solution for this. Any assistance in debugging the problem would also be helpful.

Thanks,
Avik

This topic has been closed for replies.

1 reply

RodWard
Community Expert
RodWardCommunity Expert
Community Expert
April 21, 2018

It sounds to me like your SCORM API connection is being dropped out and that is preventing things from working. 

If you have Interaction Data turned on and Send Data On Every Slide turned on, then each quiz question will try to communicate results to the LMS server and wait for it to respond before moving on.  Your issue may be due to some timeout kicking in that terminates the API connection.

I've not personally tried to deliver SCORM content via Citrix to an LMS.  I don't think it's the ideal environment.  I was actually surprised to see that you got it to work at all.

K
kiva_79Author
Participant
April 21, 2018

Thanks Rod for your reply. We tried checking Fiddler captured from the Citrix server (not the kiosks) but did not seem to see any Post call to LMS after every question but we will check and see if the interaction data is turned on.

RodWard
Community Expert
RodWardCommunity Expert
Community Expert
April 21, 2018

Perhaps if there is NO regular communication then there IS a timeout that is cutting off the API communication.  If the Interaction is NOT turned on, try setting it to ON and see if that makes a difference.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices