Yesterday i was just going through my usual work when i got a client mail pointing to me that he is getting “Failed to Load RSL” and “Error #2032”. Not knowing the exact cause, I tried to dig into the issue and Googled for this. The only solution i could find is to use Failover swf file for RSL(Runtime Shared Library). But nothing concrete. Because serving a swf file instead of swz file was not the option i want to go with as the swf file will be placed in the browser cache, which many people clear from time to time, whereas swz file will be placed in the Flash player cache, which someone rarely reached to clear.
Then it came to my mind that it could be a #2032 i.e. stream error. That means that my application is not picking up the RSL i.e. framework_..swz file from the specified location. I checked the swz file and it was there. So tried to view that swz file in browser by browsing to that file manually http://……/framework..swz and to my surprize I got 404 page not found error. What does that mean? it means that IIS is not able to stream that file to my browser or is not recognizing the file extension or mime-type. So i searched again for the .swz mime type, it’s the same as of swf file but only the extension is different so i updated it in IIS. Following are the steps to update in IIS:
Steps to update mime type in IIS:
1. Open up IIS
2. Move to website folder
3. Right click on web site folder/virtual directory and open properties
4. Open up HTTP Headers and click on button at bottom in the tab “File Type”
5. Click “New Type”
6. Enter ‘.swz’ without quotes in Associations Extension and ‘application/x-shockwave-flash‘ without qoutes in Content type (MIME). Click ok and and you are ready to go.