[flexcoders] Re: Error #2032: Stream Error. URL: datavisualization_3.0.0.477.swz

2008-07-29 Thread Vijay Ganesan
OK found the issue using the web server call as you suggested. I had to explicitly specify the path to the .swz file in my build file: arg line=-runtime-shared-library-path '${FLEX_HOME}'/frameworks/libs/datavisualization.swc /foo/bar/datavisualization_3.0.0.477.swz ... I had omitted /foo/bar

[flexcoders] Re: Error 2032 - Stream error

2007-11-30 Thread Abyss Knight
I just had this same error yesterday and had a couple answers posted. You might try a search on this board, but the checklist I was asked for was: 1. Is it using SSL? 2. Are you using Pragma: no-cache or cache control? 3. Is the server using gzip? 4. Did you check the URL of your HTTPService

[flexcoders] Re: error 2032 Stream Error

2007-05-08 Thread bhaq1972
Your not alone. We have these inconsistent problems as well. Its a shame flex doesn't show what the server fault is. would help. --- In flexcoders@yahoogroups.com, scott_flex [EMAIL PROTECTED] wrote: I just started getting the 2032 error when calling a web service and for the life of

[flexcoders] Re: error 2032 Stream Error

2007-05-08 Thread scott_flex
Well, i'm glad i'm not the only one, except that i released my app and now it seems every other time or so i get this error...i'm in a tight jam right now. It appears but NOT always, that when call my web service and pass it xml, the larger the xml parameter, at some threshold, it throws the

[flexcoders] Re: error 2032 Stream Error

2007-05-08 Thread bhaq1972
do you have any webmethods that takes more than one argument? I don't have this problem, but if you do a search on '.net webservice error' at http://flexsearch.org/. Previous answers suggest that the arguments could get muddled up. We've started to put a few more catches on the .net side and

[flexcoders] Re: error 2032 Stream Error

2007-05-08 Thread scott_flex
And... this is not just an IE thing for me, it's Firefox and Netscape, running on Windows xp. And.. the only time I ever get this message is with a single web service call, and it's one where I can potentially pass an xml parameter up to 15k. This was working in the past, not sure what's