Repair Site
Troubleshooting Flash Player Error 2032
Flash player error 2032 is the result of incorrect code by the programmer. It is unlikely that an end user will encounter this error as most programmers thoroughly test their Flash applications before putting the Flash file live on the internet. If you are a regular visitor (not a programmer) and are experiencing this error it is most likely due to an error by the programmer- there is little that you can do to solve this error.
If you are completely sure that the website you are visiting works properly and that the error stems from your computer you may find some relief in removing and then reinstalling Flash. Removing and then reinstalling Macromedia Flash is a relatively simple process. Follow the steps below:
- Uninstall Flash via the Adobe uninstall tool - Found here (http://kb2.adobe.com/cps/141/tn_14157.html), this tool is the only way to completely remove Macromedia Flash from your system. Choose the version that is appropriate for your operating system, download, and then run the program.
Once the program has run it will have completely removed Flash from your computer. You can verify this by trying to visit any Flash-enabled website.
- Reinstall Flash - Once Flash has been completely uninstalled, reinstall Flash by visiting the Adobe Flash website (http://www.adobe.com/products/flashplayer/). Be sure to download the latest version (as of this writing it was version 10).
If you are a developer, see below for information about Flash player error 2032.
Background Information about Flash Player Error 2032:
Specific error name: Error #2032: Stream Error.
There are two primary causes of error 2032:
- The HTTPService call is unable to find the URL or the URL is blocked - If the URL is blocked or HTTPService call is unable to locate it the error will be produced.
- The SWF is attempting to access a file on another/restricted domain - The permissions on a domain that you are trying to access in this instance may not be granting the appropriate permissions to the SWF.
Another cause of this error (though it is very minor in comparison to the two above) is browser caching. As well, you may receive this error if you recently upgraded your Flash player version and did not update your code accordingly. Many elements of prior versions of the Flash player are not compatible with updated versions and will result in the error 2032 being displayed. In some exceedingly rare instances the file may load after clicking "ok" on the error dialog box.
Fixing Flash Player Error 2032:
The first, and most obvious, solution is to ensure that all of your code is compatible with your version of the Flash player. This should be the first thing you address, as it may save you hours of headache later if the fixes below do not work for you. In many cases updating your code to be compatible with your version of the Flash player solves the problem.
As well, and this is also quite obvious, it is imperative that you ensure that there are no typos in your code and address references. Misspelling a domain in your HTTPService call will result in Flash player error 2032 being thrown.
Assuming that you have checked your code/spelling, if you are still receiving the error try the following:
- If referencing a SWF file on another domain - Ensure that you have granted the SWF file the appropriate permissions to access content/change permissions on another domain. You can do this by adding additional code to the file being referenced. For more information, click here (LINK TO RELEVANT POST/ARTICLE ABOVE).
- If referencing information on the same domain - Ensure that the content is where you are referencing from and that the files are able to be read.
- Check the HTTPService call - The characters "<" and ">" seem to cause the error 2032 in some instances. Escaping these characters will solve this issue.
As well, the httpService.contentType="application/xml" string may also cause this error to appear. Removing this string will solve the error in this instance.
- Update all references - Often, a file will be moved and the code will not be updated to reflect the new location for the referenced file. Update your references to resolve the error in these instances.