Like i said, nothing "just all of a sudden happens".  An error, deep 
down in a nested component, based on the data passed to my web 
service was throwing an error... there was a small change in a 
nullable field in our database.

So...i couldn't just let this post die without confessing that I 
caused my own bug (my first... yeah right!!) and my back end didn't 
log it at all....  Then some of my debugging code was failing too, 
ha, what a morning.

I'll take full blame on this one but it sure would have been nice if 
the real error message could have travelled back to my Flex app.  I 
probably would have caught it much earlier, instead of sorting 
through all the code to finally realized what was happening.


--Scott



--- In [email protected], "scott_flex" <[EMAIL PROTECTED]> wrote:
>
> 
> 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 different now.
> 
> --Scott
> 
> --- In [email protected], "scott_flex" <skrause@> wrote:
> >
> > 
> > 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 
> > error more often.  That's just a symptom i've noticed.
> > 
> > Searching the web for the error doesn't turn up to many results.
> > 
> > I possible could have changed something in my code, doubt it but 
> > possible or something changes on my server but nothing to my 
> > knowledge.  So it appears to "just" start happening.  Which 
> normally 
> > is never true to "just" all of a sudden start happening.  I'm at 
a 
> > loss of where to begin searching for the resolution.
> > 
> > --Scott
> > 
> > 
> > --- In [email protected], "bhaq1972" <mbhaque@> wrote:
> > >
> > > 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 [email protected], "scott_flex" <skrause@> 
wrote:
> > > >
> > > > 
> > > > I just started getting the 2032 error when calling a web 
> service 
> > > and 
> > > > for the life of me cannot determine what's causing it.
> > > > 
> > > > Code snippet looks like:
> > > > var ws:WebService = new WebService()
> > > > ws.addEventListener("fault", faultHandler); // alerts error
>       
> > > > ws.loadWSDL("http://mylocalservers/test.asmx?WSDL";);
> > > > ws.updateTest(__xml);
> > > > 
> > > > 
> > > > Sometimes i get it, and sometimes i don't.  Not sure why 
though.
> > > > 
> > > > faultCode Server.Error.Request
> > > > faultDetail: Error: IOErrorEventtype: "ioError"
> > > > faultString: HTTP Request error
> > > > 
> > > > I getting in production when i'm in an SSL environement and I 
> get 
> > > it 
> > > > in my development environment where i'm running the flex app 
> and 
> > > web 
> > > > services all locally.
> > > > 
> > > > The url to my web service url is correct and the web services 
> > runs 
> > > > properly when called and tested from other apps.
> > > > 
> > > > What's weird is that i haven't changes how my web service 
calls 
> > or 
> > > > web service itself works...
> > > > 
> > > > Any help or pointers would be greatly appreciated.
> > > > 
> > > > --Scott
> > > >
> > >
> >
>


Reply via email to