Skip to main content
wfzen
Inspiring
December 19, 2016
Answered

Some Flash content stopped working after restoring a server

  • December 19, 2016
  • 1 reply
  • 664 views

This is for intranet with associates using SharePoint on IE v11.0.37 under Windows 7 Corporate environment.

Some Flash content (but not all) stopped working after the server crash and restore. IT added SWF to MIME.

Here are the behaviors I observed:

- Some Flash created in ActionScript 2 stopped working while some others in AS2 still work.

- I checked the temporary internet files folder, and found those do not work do not have the files inside that folder. It seems it refuses to load.

- Seems AS3 always work on the ones I checked. There is one page with 2 Flash content; one in AS3 and one in AS2. The one in AS2 didn't load while AS3 one worked.

- one developer was able to fix this by copy the file to HD, rename and copy it back to server, and link to the file with a new name and then it worked. This method only worked on a few occasions but not on all.

What could be the problem and solution to this?

Thanks for your help,

    This topic has been closed for replies.
    Correct answer wfzen

    It has nothing to do with Flash itself. It turns out some links with full domain name spelled out and some with just the server name. IT had to configure the server and they didn't include both. Thanks for the info.

    1 reply

    jeromiec83223024
    Inspiring
    December 20, 2016

    There's not enough information here to venture a guess.

    A great place to start would be to look at your browser's developer tools to see if all the appropriate assets are actually being served, and that they have the right mime-types.

    I have definitely run into this on IIS machines that I manage, where either permissions or the files themselves get messed up and cannot be served.  The network tab of your browser's developer tools should show you whether or not an asset is served, and if not (you're getting an HTTP 404 or 500 error instead), then you can look at troubleshooting documentation for the appropriate error codes for your IIS version to start working the problem.

    As a tip, IIS will give you an error code like 404.1234, where the numbers after the dot correspond to a particular reason for an error.  IIS is a little odd, in that if it doesn't have a defined mime-type for a particular file extension, it will return a 404.  Given the description of how you wound up in this state, that sounds like maybe a good place to start.

    The other thing you might want to do, is install a Debugger version of Flash Player, to see if it gives you any useful clues in terms of error messages...


    Hope that helps!

    wfzen
    wfzenAuthorCorrect answer
    Inspiring
    January 11, 2017

    It has nothing to do with Flash itself. It turns out some links with full domain name spelled out and some with just the server name. IT had to configure the server and they didn't include both. Thanks for the info.