Verify that the .JS file is correctly referenced from the page. The path can be specified either relative to the current document, or an absolute path name can be used.
Ensure that the .JS file on the web servers have permissions appropriately set so that the file may be downloaded and executed by website visitors. If a different .JS file is used on development servers, set the "read only" attribute for the .JS file on production servers to avoid an overwrite. If altered, ensure that the following settings are set appropriately at the top of the .JS file:
If " s_account " is assigned a value at the top of the .JS file, ensure that the report suite ID (populated in the s_accountvariable) is correct. Also ensure that the code in the page is not setting the Report Suite ID ( s_account variable).
Examine the image request and variables to ensure that the "fallback method" (the third part of the "split" code in the example above) is not creating the image request instead of the .JS file. This can be determined since the "fallback" method only creates an image request with minimal information.