WSE Error : Fault Description Destination Unreachable

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Krish - 13 Apr 2005 22:03 GMT

Hi all,
We are using WSE 2.0 for communicating between services. We've just run
into a problem on one of our servers.
The error that we get in the Event Viewer is a WSE error

Message Dispatch Failure: <?xml version="1.0"
encoding="utf-8"?><soap:Envelope
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><wsa:Action>http://schem
as.xmlsoap.org/ws/2004/03/addressing/fault</wsa:Action><wsa:MessageID>uuid:17b70
9fb-0c6d-4b86-97d1-6005ecfea32b</wsa:MessageID><wsa:RelatesTo>uuid:0337b55e-bae2
-4d45-8c63-d11bc48ca67f</wsa:RelatesTo><wsa:To>soap.tcp://10.10.20.25:9055/</wsa
:To></soap:Header><soap:Body><soap:Fault><faultcode
xmlns:code="http://schemas.xmlsoap.org/ws/2004/03/addressing">code:DestinationUnreachable</f
aultcode><faultstring>Destination
Unreachable</faultstring><faultactor>http://devapp/</faultactor></soap:Fault></soap:Body></soap:Envelope>

Background:
The Web client is a SQL Reporting Services default Web application
running on Windows 2003 server (IIS 6.0). A Report deployed in
Reporting services accesses a .Net (C#) assembly to send messages using
WSE 2.0 to communicate with another Windows service. However what we
are seeing is that the message never reaches the destination. Infact we
have tried where in the Windows service and MS SQL Reporting services
are installed on the same server. But the message never gets through to
the service and we get the above error messages.
Another thing is we have other Windows services that also communicate
with each other messages (using WSE 2.0) and they seem to be working
just fine.
So my question is if there is any kind of setting on IIS that we've
missed. "To" address doesn't match the HTTP header address or if the
destination address can't be resolved.
Is there any way to debug or get more information on this?? How do I
turn WSE tracing ON for my Reporting Services Client.
Any help is deeply appreciated. We've been fighting with this for at
least a week and are not going anywhere with it.
Thanks in advance,
Krish

Reply to this Message

John Bristowe - 13 Apr 2005 22:15 GMT

Krish,

I hit this error a while back:

http://wsefaq.com/question.aspx?id=4f1c232b-d75b-4c25-97d2-9f32d7246e6c

I would verify how your SoapReceiver/SoapService is registered.

John

> Hi all,
> We are using WSE 2.0 for communicating between services. We've just run
[quoted text clipped - 29 lines]
> Thanks in advance,
> Krish

Reply to this Message

Dilip Krishnan - 13 Apr 2005 22:48 GMT

Krish,
Might want to check if http://devapp is reachable (it doesnt seem
like a valid web service endpoint!). Because (as the error suggests) its
what WSE does when its soap sender is not able to send the message to
the destination. You'll find that if you try and send a message using
wse to a bogus endpoint (http://bogusuri.com for example) WSE fails and
makes an entry in Event log.

> Hi all,
> We are using WSE 2.0 for communicating between services. We've just run
[quoted text clipped - 29 lines]
> Thanks in advance,
> Krish

Signature

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dilip.krishnan AT apdiya DOT com

Reply to this Message

Krish - 14 Apr 2005 17:15 GMT

John/Dilip,
Thanks for you replies. Really appreciate it.

John,
Currently my Soap Receiver (on Web side) is listening or registered at
10.10.20.25:9055 and the message is being sent to a service which has a
Soap Receiver/listener registered at 10.10.20.25:9056.
I know the Service Soap Receiver address for the service is correct
because I've other services communicating with the service on the same
Soap Receiver. Is there something else that I need to look for?? As per
the article that you directed me to, the soap receiver is registered
with an address that does not match the Soap Envelope's destination
address. I don't see a destination address tag within the envelope.

Dilip,
I tried the http://devapp and it is accessible although as soon as you
enter it in IE it changes to DNS entry name http://devapp.alogent.com.

I'm attaching the actual message that had a problem. Let me know if
anything jumps out.
<?xml version="1.0" encoding="utf-8"?><soap:Envelope
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><wsa:Action>soap://aloge
nt/servicemessage/imagearchive</wsa:Action><wsa:From><wsa:Address>soap.tcp://10.
10.20.25:9055/</wsa:Address></wsa:From><wsa:MessageID>uuid:aede5b8c-5260-4ee2-8e
21-cae0e7c8aabb</wsa:MessageID><wsa:ReplyTo><wsa:Address>soap.tcp://10.10.20.25:
9055/</wsa:Address></wsa:ReplyTo><wsa:To>soap.tcp://10.10.20.25:9056//whseDevGro
up</wsa:To><wsse:Security><wsu:Timestamp
wsu:Id="Timestamp-889f3b61-968b-4462-8f63-2170cbcfa497"><wsu:Created>2005-04-12T20:18:52Z</wsu:Created><wsu:Expires>2005-04-12T20:23:52Z</wsu:Expires></wsu:Timestamp></wsse:Security></soap:Header><soap:Body><ImageArchiveParameterSet
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://alogent.com"><Parameters><ImageArchiveQueryParameter><name>ImageSource</name><type>System.String</type><value>F:\WareHouse\Image\Image\20050412\Cap2\41010000_4018</value></ImageArchiveQueryParameter><ImageArchiveQueryParameter><name>Source</name><type>System.String</type><value>Cap2</value></ImageArchiveQueryParameter><ImageArchiveQueryParameter><name>ImageDIN</name><type>System.Int32</type><value>2064324</value></ImageArchiveQueryParameter><ImageArchiveQueryParameter><name>BusinessDate</name><type>System.String</type><value>2005/04/12</value></ImageArchiveQueryParameter></Parameters></ImageArchiveParameterSet></soap:Body></soap:Envelope>

Reply to this Message

Dilip Krishnan - 14 Apr 2005 19:08 GMT

How about the soap sender? Where is it sending the web service request,
to 10.10.20.25:9056? The receivers are all good... its the sender that
causes that problem

> John/Dilip,
> Thanks for you replies. Really appreciate it.
[quoted text clipped - 25 lines]
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns="http://alogent.com"><Parameters><ImageArchiveQueryParameter><name>ImageSource</name><type>System.String</type><value>F:\WareHouse\Image\Image\20050412\Cap2\41010000_4018</value></ImageArchiveQueryParameter><ImageArchiveQueryParameter><name>Source</name><type>System.String</type><value>Cap2</value></ImageArchiveQueryParameter><ImageArchiveQueryParameter><name>ImageDIN</name><type>System.Int32</type><value>2064324</value></ImageArchiveQueryParameter><ImageArchiveQueryParameter><name>BusinessDate</name><type>System.String</type><value>2005/04/12</value></ImageArchiveQueryParameter></Parameters></ImageArchiveParameterSet></soap:Body></soap:Envelope>

Signature

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dilip.krishnan AT apdiya DOT com

Reply to this Message

Krish - 14 Apr 2005 21:24 GMT

Dilip,
For sending the message we are creating a SoapSender object
SoapSender sender = new SoapSender(message.To);
message.To is of type EndpointReference which is
soap.tcp://10.10.20.25:9056//whseDevGroup.
And then
sender.Send(message.Envelope); message.Envelope is of type
SoapEnvelope.

We've checked the version of WSE.
Microsoft.Web.Services2,Version="2.0.2.0".
And this seems to be happening only for a web based request and not for
Windows Service to Service communication (using WSE 2.0). I'm trying to
think if there is a policy/security setting that we missed.

Another thing, we tried a similar setup where in we moved Web setup
(including reporting services) to a different server. This time the
communication between the Web service request and Windows Service was
fine. It could find the destination address.
Thanks,
Krish

Reply to this Message

JJ - 14 Apr 2005 21:29 GMT

Hi Krish

are you using any trace tools to to view the SOAP messages, sent by HTTP,
between a SOAP client and a service on the server.
I'm just looking for SOAP Trace tools

Thanks

Reply to this Message

Krish - 14 Apr 2005 22:10 GMT

JJ,
I'm using a tool called as wseTrace.exe to read trace messages. Most of
our communications are using TCP or Named Pipes. This is tool lists all
the messages but you need to set up WSE tracing in your
<Assembly>.exe.config file. In your case I would presume you'll have to
add this to Web.config file (although I haven't set up for tracing for
a web request).
<configSections>
<section name="microsoft.web.services2"
type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration,
Microsoft.Web.Services2, Version=2.0.2.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" />
</configSections>
<microsoft.web.services2>
<diagnostics>
<trace enabled="false" input="InputTrace.webinfo"
output="OutputTrace.webinfo" />
</diagnostics>
</microsoft.web.services2>

I can send you the tool if you need. This would be only useful if you
are using WSE though.
Krish.

Reply to this Message

JJ - 14 Apr 2005 23:59 GMT

Cool,

Ijust installed and it works for me.

Thanks

> JJ,
> I'm using a tool called as wseTrace.exe to read trace messages. Most of
[quoted text clipped - 19 lines]
> are using WSE though.
> Krish.

Reply to this Message

WSE Error : Fault Description Destination Unreachable

Free Magazines