[RPC Fault faultString="HTTP request error" faultCode="Server.Error.Request" faultDetail="Error: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2032: Stream Error. URL:xxx"]. URL:xxx”]
Yesterday this error raised the first time. Today I figured out what it could be.
It seems this error raises when Flex tries to access two files at the same time through a HttpService. Looks like a SandBox restriction.
More information on error #2032 (ioError) and other occurences can be found in a post by Judah here (seems to give a lot of 404 pages).
Filed under: Flex | Tagged: 2032, fault, Flex, httpservice, ioerror, rpc, sandbox
When i run the flex program on my system i found the following error. can anybody solve this problem?
[RPC Fault faultString="HTTP request error" faultCode="Server.Error.Request" faultDetail="Error: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2032: Stream Error. URL: file:///E:/flex%20workspace/HTTPservice/bin-debug/data/tests.xml"]. URL: data/tests.xml”]
at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:216]
at mx.rpc::Responder/fault()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\Responder.as:49]
at mx.rpc::AsyncRequest/fault()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\rpc\AsyncRequest.as:103]
at DirectHTTPMessageResponder/errorHandler()[E:\dev\3.0.x\frameworks\projects\rpc\src\mx\messaging\channels\DirectHTTPChannel.as:343]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/redirectEvent()
Hello Vinuth,
Do you use a HTTP request? If so, that could be the one generating this error. You might want to check wether your destination url can’t be found/read. So check the URL (i see it returns a stream error for file:///e:/ (notice the 3 ///).
I am also getting the same error. I am using a HTTP request to connect to a .NET service and the same error is displayed. My flex code is deployed in IIS. I tried accessing the .NET service through the browser, it is working fine. But when I do it from my flex application I am getting the same error.
This exception is really making me bad. My server logs are not showing any problem and getting execute without any problem, but on client side i am getting this fault. I have no idea what to do now. Plz help
I’m getting the same,
weird, it was all fine, only at one specific method it goes wrong.
so far I’ve found out IT WON’T CALL THE WEBSERVICE,
I tried to debug the server-side and it won’t show a thing.
this is an ONLY-FLEX-PROBLEM,
one of the guys here said something about trying to access the same file twice at same time.
Let’s try something out in here
I FOUND OUT!!!!
IT’S BECAUSE WE ARE USING WRONG PARAMETERS…
I had changed the parameters at server side,
some functions showed problems at compile time, some didn’t…
REPEATING…
JUST CHECK YOUR PARAMETERS…
solved,
seems Adobe Flex can’t use Complex-Objects as parameters,
but it can as result types.
hope someone reads it so I can help
xD
Hi
I have the same problem
Thiago what did you mean “JUST CHECK YOUR PARAMETERS” .. the type or the name?
pls help thanks
Andrei,
you can only take simple types for parameters…
such as string, int, double…
althought, not refreshing the webservice inside adobe flex may cause this error to raise too.
btw, you can use int[], string[], int[][], string[][] (never tried 3rd level)
Flex has a problem with DateTime due to LocalTime, UTC, this kind of stuff… (not this error, but it brings time values with some minutes wrong, absolutely inexplainable)
I solved it by passing strings with DateTime.ToString()
and then parsing it on the other side.
here is how I solved it…
I had a webservice that has a complex-type as a parameter.
public bool DoSomething(AnimalVO vo)
{
//my code here using the “vo”
}
so I just changed the method to…
public bool DoSomething(int idAnimal, string name, int idOwner, int age)
{
AnimalVO vo = new AnimalVO();
vo.idAnimal = idAnimal;
vo.name = name;
vo. = ;
vo. = ;
vo. = ;
//and down here I change nothing…
//my code here using the “vo”
}
don’t forget to update your wsdl on flex when you do it
found out more,
the specific reason that you can’t use complex-types is that
some Number-typed values are set to NaN,
and the webservice doesn’t understand what a Nan is…
althought, you can’t say:
if (vo.some_property == NaN)
vo.some_property = 0;
you have to use
if ! (vo.some_property > 0) //if not > 0
vo.some_property = 0;
I’m getting this error:
[RPC Fault faultString="HTTP request error" faultCode="Server.Error.Request"
faultDetail="Error: [IOErrorEvent type="ioError" bubbles=false cancelable=false eventPhase=2 text="Error #2032"].
URL: https://path.to/files/file.php“]
But *only* in Internet Explorer. The app works just fine in Firefox.
I too got the “HTTP request error” on a web service invocation today. Even splitting up the complex request object into multiple simple parameters, and initializing numbers din’t help either.
Ultimately what I found was that a date property in the request object was defined as not null in the .net web service. (all DateTime declarations are by default not null. Only the DateTime? declarations are nullable). But I was passing null for that date.
After I declared the date as DateTime? in the service class and initialized my AS3 integers, the complex request object went through smoothly.
Thankfully, Flex is not stupid to reject complex request objects.
I was getting the same error but mine was because i was using old version of Flash! Once i installed Flash 10 it went away.
I’ve been getting this same error, but only in IE 7. In Firefox, my app works just fine, no problem. But in IE, I get the error.
I thought flash was supposed to be better than java at write once, run anywhere.
Bob,
I have the same problem you stated (works in FF but not in IE7). Were you able to solve that problem?
Thanks!
Connie
I’m having the same issue.. anyone find the solution?
I got that error and the issue when I was calling the WS was that the webconfig in .NET didn’t have the following code:
After I added the code, I was good to go!
Hello Mike, your codeblock isn’t visible