Re: WSE464: No policy could be found for this message.

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
.

Relevant Pages

  • Re: WSE464: No policy could be found for this message.
    ... The problem is only happening when coming in through the isa server. ... My endpoints are upper and lower case. ... I changed the CLIENT policy file so that the endpoints ... But I had no problems with my web services this way. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • WSE2.0 SP2 Unknown Issue?
    ... I have these policy endpoints defined: ... all endpint definition ... With SP2 it seems unable to distinguish both endpoints uri. ... to, String requestAction) at ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: WSE2.0 SP2 Unknown Issue?
    ... WSE won´t let you have two different endpoints mapped to the same physical ... uri suffers when WSI parse the policy file. ... "Hernan de Lahitte" wrote in message ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Certificate-based DHCP authentication
    ... What we did with their IT is set up ISA server and made a policy that only ... > access to Internet from clients that are not members of domain... ... Via ISA server and ipsec or ?? ...
    (microsoft.public.windows.server.security)
  • Re: no external web server with dns www host sbs2000
    ... ISA Server 2004 does not allow outbound access to the Internet ... Firewall policy specifies: ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)