Composition runs properly locally, but buggy remotely

Question

Hi friends. Just want to preface that the following composition works locally whether I am launching an Edge Animate Preview, or looking at the composition through http on my local Apache installation.  When I access the composition through a remote server, is when the errors occur.  The silver lining is that the same errors occur regardless of who is accessing the page across location and browser. 
With that I'll post the document.compositionReady code:
/* Initialize Sound */
var assetsPath = "media/";
EC.Sound.setup(
        {src: assetsPath + "Coaching_5.mp3|" + assetsPath + "Coaching_5.ogg", id: "slide_5"},
        {src: assetsPath + "Coaching_5a.mp3|" + assetsPath + "Coaching_5a.ogg", id: 'slide_5_1'},
        {src: assetsPath + "Coaching_5b.mp3|" + assetsPath + "Coaching_5b.ogg", id: 'slide_5_2'}
    function(){ EC.info("Sound setup finished", "DEMO"); }
/* Initialize Z-Indexing */          
var currZI = 1000;
/* Apply functionality to the two buttons */
sym.$("polaroid_1").click( function() {
          shiftButtons(1);
sym.$("polaroid_2").click( function () {
          shiftButtons(2);
/* shiftButtons will trigger a series of GSAP animations to show popup content based on selected photo icon */
function shiftButtons(_arg)
          stopAllAudio();
          playAudio(_arg);
          if (_arg == 1)
             sym.$("polaroid_1").css({ "position":"absolute", "z-index":currZI});
             TweenMax.to(sym.$("polaroid_1"),1,{css:{left:680, top:70}});
             TweenMax.to(sym.$("polaroid_2"),1,{css:{left:680, top:170}});
                    TweenMax.to(sym.$("popup_1"),1,{css:{left:33}});
                    TweenMax.to(sym.$("popup_2"),1,{css:{left:1000}});
                    EC.info( "clicked on pic 1, depth = " + currZI);
                    currZI++;
          else if (_arg == 2)
             sym.$("polaroid_2").css({"position":"absolute", "z-index":currZI});
                    TweenMax.to(sym.$("polaroid_1"),1,{css:{left:0, top:170}});
                    TweenMax.to(sym.$("polaroid_2"),1,{css:{left:0, top:70}});
                    TweenMax.to(sym.$("popup_1"),1,{css:{left:-1207}});
                    TweenMax.to(sym.$("popup_2"),1,{css:{left:481}});
                    EC.info( "clicked on pic 2, depth = " + currZI );
                    currZI++;
function playAudio(_arg)
EC.info( "audio trigger: " + _arg);
EC.Sound.play("slide_5_" + _arg);
function stopAllAudio()
   //EC.Sound.stop("slide_5");  // Not used for now
   EC.Sound.stop("slide_5_1");
   EC.Sound.stop("slide_5_2");
What's happened here when viewed remotely, some of the Tween instructions were "skipped" (not executed).  I solved the problem with the two popups not firing by simply combining them into a single div and "pushing" that single div with all of the popup content around the stage.
After that however, I'm finding that remotely, the first time audio should play (when launched by a button click) it does not play.  Every subsequent audio trigger works, just not the very first one.  I'm wondering if there is a conflict here with the stopAllAudio() function. 
Thank you.
Patrick

Answer 1

I had already tried commenting out the second line (setting of the FileName property) on the report object and got the same results.  If I comment out the first line, I need to replace it with something like...
ReportDocument cr = new ReportDocument();
... otherwise where would I specify the path and filename of the report?  If I replace that line with the web report object like I was originally...
CrystalDecisions.Web.Report cr = new CrystalDecisions.Web.Report();
... this won't work either because the Logon() routine (borrowed from the sample app) expects the report reference passed in to be a CrystalDecisions.CrystalReports.Engine.ReportDocument object.
Incidentally, this alternative approach from the sample code, unlike my original code using Web.Report, won't even work in my development environment.  So I'm back where I started.  Since all of my other reports work just fine both in the dev environment and on the server, I'm forced to assume that the problem is something specific to sub-reports since none of my other reports have them.  If I can find a way to apply the LogOnInfo to the sub-reports using the Web.Report object, that might do the trick.  No luck yet, however.
Oh, and one more thing, I found a surprising bug in the Logon() routine of that sample app:
// If the ApplyLogon function fails then return a false for this function.
// We are applying logon information to the main report at this stage.
if (ApplyLogon(cr, ci))
                return false;
It should be...
if (!ApplyLogon(cr, ci))
- Robert -