Engage + WebDAV + IE 6 = Eternal Pinwheel

[dduncan]

Has anyone else run into any issues when publishing Engage interactions to a WebDAV hosting environment (such as SAP LS or Livelink) ... and when you try to call the interaction in IE 6 ... the interaction hangs or only displays the 'Eternal Preloader Pinwheel'?

I've been fighting this issue for about three weeks ... and noticed that upgrading to IE 7 solves the problem. However, deploying IE7 to 10,000 machines worldwide isn't really a great option just to deploy one training program.

If anyone has any tips or tricks that I could pass on to our IT folks ... that would be great.

[Justin]

Could you please do the following to see if it resolves the issue you are having:

1) Clear your cache. You can do this in Internet Explorer by going to
Tools -> Internet Options -> General -> Temporary Internet Files and select
Delete Cookies and Delete Files.
2) Under the Security tab, click on the Internet, Local intranet, Trusted Sites, and Restricted Sites and select Default level for each.
3) Under the Privacy tab make sure that is set to the Default level.
4) Under Advanced click Restore advanced settings and click OK.
5) Restart your web browser.

Also, does it work in IE6 outside of your corporate environment?

[dduncan]

Updating the browser settings does not remedy the issue.

The Engage content does not display internally or externally in IE 6 when pulling from WebDAV.

The Engage content displays perfectly internally or externally in IE6 when pulling from Apache Web Server.

The Engage content displays perfectly in IE7 when pulling from WebDAV.

The Engage content displays perfectly internally or externally in IE7when pulling from Apache Web Server.

[Justin]

What version of Engage are you using? Are the interactions standalone or are they in a Presenter presentation? If you haven't already done so I would submit a case about this.

[ayang]

Hello Justin,

I am working with a customer and am experiencing the same issue when publishing Presenter courses with embedded Engage interactions. Have you determined a resolution to this issue?

Cheers,
-Alan

[Justin]

I don't believe so. I would suggest you submit a case.

[ayang]

Hi Justin,

The issue we are encountering is with the Engage interaction being delivered over SSL. After running HTTPWatch I noticed that the interaction is getting hung up on "interaction.xml". Have you encountered this issue before and do you have any resolution?

Cheers,
Alan

[dduncan]

We discovered that the SAP LS servers use object compression. Object compression tends to make the SWF (and other rich media) files pretty crabby ... especially in IE6. By disabling or adjusting these settings on the server ... the issue was resolved ... after a three month delay in deploying the training. Most web servers don;t even use object compression .... yet another quirk of SAP.

Feel free to email me at daniel.duncan@yahoo.com ... and I can put you in touch with the IT guys who figured this out.

[Justin]

Thanks for sharing your solution!