Re: WSE464: No policy could be found for this message.
- From: "Julie Lerman" <jlermanATNOSPAMPLEASEthedatafarm.com>
- Date: Thu, 16 Jun 2005 15:45:55 -0400
interesting and thanks.
so here's what I have learned and tried, based on your insight.
This problem happened again today all morning and then it magically was okay
at about 3pm.
Before it resolved itself, I did look at the tracing, but just the soap , I
didn't get a chance to trace the policy before the problem disappeared.
What I saw is that the outgoing message looked find (from the client) and ws
being processed becasue I was getting the correct data back from the web
server. However the incoming message had no policies applied to it! So it
was the client app that was rejecting the message.
I discovered that at this time and the last time we had the problem, the
i.t. guys were working on the exchange server and had taken it down. The
exchange server happens to be the master domain controller on the network.
THe webserver is on a different box and the isa server is on a different
box.
The problem is only happening when coming in through the isa server. No
problems in-house on the intranet.
My endpoints are upper and lower case. They are like that in both policiy
files (client and server) and also in the actual application.
As an experiment, I changed the CLIENT policy file so that the endpoints
were all upper case. But I had no problems with my web services this way.
(I.E. at this point, everything was working and I couldn't break it by
changing this particular policy file)
I am not sure if any of these points will help, but can you make anything
out of it?
I would like to understand it so that I can protect my apps in the future.
Julie
"Dilip Krishnan" <"dilip.krishnan AT apdiya DOT com"> wrote in message
news:eSgrVNocFHA.3940@xxxxxxxxxxxxxxxxxxxxxxx
> The policy to be applied is resolved using the endpoint and its possible
> that the ISA server is altering the endpoint ever so slightly (read case).
> The policy resolution is case sensitive so that could be a cause. The
> other thing that could be happening is that ISA server is routing to the
> web service and translating the domain name of your endpoints... i.e.
> hostname.domain.com/webservice.asmx to hostname/webservice.asmx
>
> Try seeing if you can factor your policy cache so that you use default
> endpoints if none is automatically resolved. Turn policy trace on just to
> see what the endpoints are that are being resolved to the default policy
> and that should give you a clue on how to solve the issue from there on.
>
> Julie Lerman wrote:
>> We had a strange thing occur that I cannot duplicate and therefore debug
>> and fix for next time.
>> This is an app and web service that have been working together with WSE2
>> for many many months. Last night I was told that on one particular
>> function in teh application, they were getting the above message. Over
>> and over again from numerous computers. This morning, when I tested it
>> from MY computer , hitting the same webserver, I did not have the
>> problem. They said the problem also disappeared this morning.
>>
>> I don't know where to start investigating this. This function was the 3rd
>> in a series of WSE2 wired web services calls. So it wasn't that the
>> webserver disappeared. They would always get past the first two and then
>> get this on the third call (the particular function).
>>
>> What type of event would cause this to disappear and then reappear. These
>> computers were all hitting the webserver through the internet and through
>> an ISA Server. They endpoints have not changed. Nobody edited the policy
>> config file.
>>
>> Can anybody get me pointed in the right direction?
>>
>> Thanks!!
>>
>> Julie Lerman
>
> --
> HTH
> Regards,
> Dilip Krishnan
> MCAD, MCSD.net
> dilip.krishnan AT apdiya DOT com
.
- Follow-Ups:
- References:
- WSE464: No policy could be found for this message.
- From: Julie Lerman
- Re: WSE464: No policy could be found for this message.
- From: Dilip Krishnan
- WSE464: No policy could be found for this message.
- Prev by Date: wse 3.0 - problem using kerb ticket on localhost for devlpmnt.
- Next by Date: Re: WSE .net client and apache axis server
- Previous by thread: Re: WSE464: No policy could be found for this message.
- Next by thread: Re: WSE464: No policy could be found for this message.
- Index(es):
Relevant Pages
|
