I have had a problem of publishing my large AW piece to the web as it hangs on the loading files screen of the player. So I rigged a simple test web published piece (two files which jumps back and forth on button click) which initially worked fine on my development machine and also on my website.
I then modified it to testout the PostURL function and now have a file loading problem which seems unrelated to the PostURL function (since I also uploaded a version with that function commented out). The piece hangs in a window with the loading files thermometer stuck and after a minute or two, it times out with an error:
"Error downloading content file. Internal error: Time out. http://www.mywebsite.com/ddyc/Testweb/XTRAS/INETURL.X32". My piece is published to theTestweb folder which also contains the XTRAS folder.
I have checked and reloaded the INETURL.X32 module and still have the problem. Not sure why this second version is failing and also seems to have the same problem as the large production piece. Seems like the player doesn't think the INETURL.X32 file is there when it is.
When this happens the first test I do is to enter the filename directly in the browser window. If you get the "file save as" dialog box then the server is sending the file. If the file doesn't come down there are a couple of possibilities to check out. If the server is case sensitive then make sure you have the right case sensitivity in the file name. Another possibility is that the server MIME type isn't set up. If one file works on that same server then the MIME type is most likely set up correctly. However IIS has a way that you can create MIME types that don't apply the whole server using a web.config file.
If neither of these things explain the problem then I turn to a protocol 'sniffer' tool like Charles (www.charlesproxy.com) or Wiresharkm (www.wireshark.org/) which will track the internet traffic and you can view the requests for the file downloads and the responses from the server.
The INETURL.X32 module is in the XTRAS library on the server but fails to be recognized by direct reference
- page not found. My ISP added .aas .aam and .aab after I initially had problems loading the files (should have read the documentation better ) and managed to get a test to run.
Does the ISP also have to add the .X32 type as well (I cant find mention of this in the documentation)?
Yeap, gotta add the .x32 mime types.
See here for a decent guide on prep'ing for Authorware Web Delivery: