Hi Pedro, I had a problem that looked the same when I added WSE to my .NET
configuration. In that case it was caused by WS-Routing and was solved by
turning off the MustUnderstand flag on PATH, like this in your .NET client
code:
service.RequestSoapContext.Path.MustUnderstand = false;
Note, this
Hi,
I created a WS with Axis and
a .NET client and all works fine in my development machine. But, when I try to
run the .NET client in another machine (both machines running Windows XP Pro) I
get the exception:
"The underlying
connection was closed. Unable to connect to the remote ser
Hi,
I created a WS with Axis and
a .NET client and all works fine in my development machine. But, when I try to
run the .NET client in another machine (both machines running Windows XP Pro) I
get the exception:
"The underlying
connection was closed. Unable to connect to the remote ser
