This content has been marked as final. Show 4 replies
Can't speak to the problem, but are you aware that the resultFormat="xml" produces the old legacy as2 xml object and not the new, super-cool e4x XML object?
Actually I have the same type of a problem:
See the topic
I never saw on by myself, it happens on IE7 and in only 1% of the cases.
You've mentioned that some clients have this problem on constant basis - what is the configuration of your server?
The server is running Apache/PHP 4.3 and the XML is returned in the body of the response. The XML is basically a list of images to load into the app and I've verified for all these users the XML is properly formated, etc.
The frustrating part is the only widely know issues to cause a 2032 error is the crossdomain.xml and the HTTPS issues with caching that is mentioned in several places and gzip encoding. My crossdomain is fine and I'm not using HTTPS.
I am using gzip encoding but the the known GZip issue with IE6 and HTTPS according to the msdn knowledge base it is an XP SP1/ IE6 and not an IE7 issue.
I'll keep digging from here and I'll update you all if I find anything out.
I wanted to post here that at least part of my 2032 Stream Error problem comes from Real Player 11. Several users have reported uninstalling the Real Player has fixed the issues with my applications. Although, I haven't been able to recreate the issue myself with the latest version off of their site although I can't get the feature involved to work at all.
I came across several blogs while attempting to if Real Player could be at fault after receiving the reports:
Hopefully this helps others