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" <[EMAIL PROTECTED]> 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