WSE 3.0 declarative security problem.

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

iidelchik@yahoo.com - 08 Aug 2006 00:41 GMT

Hi all,

I've a really stupid problem. I've declared policy for my WS proxy in a
policy file, referenced from app.config and added an attribute to my
proxy class [Policy("MyPolicy")]. Everything looks to be pretty
straight forward. But on a stage of proxy object creation I'm getting
problem:
"WSE2000: PolicyAttribute cannot resolve policy name 'ClientPolicy' to
a policy instance. This may indicate that the policy file does not
specify a policy with such name."

I've checked everything, naming is ok. Proxy is auto generated by
WseWsdl3.

Any ideas would be highly appreciated.

Elijah

Reply to this Message

iidelchik@yahoo.com - 08 Aug 2006 00:57 GMT

Just realised, it can be misleading. Of cause I use 'ClientPolicy' in
Policy attribute instead of "MyPolicy", mentioned above.

Reply to this Message

Jerry - 31 Oct 2007 17:34 GMT

> Hi all,
>
[quoted text clipped - 13 lines]
>
> Elijah

I have this exact same problem.
It only manifests itself on Windows Server 2003 (using SP2). It works on Windows XP and Vista.
It also only manifests itself in the Debug build. The release build works fine (even on Server 2003).

What could be different between the Release and Debug builds? I've searched for #if(DEBUB) statements throughout my code and there is nothing related to WSE that should have any effect. Also, I've compared the App.config and wse3policyCache.config files between Release and Debug and they are exactly the same.

Has anyone else experienced this issue?

BizTalk Utilities - Frustration free BizTalk Adapters
http://www.topxml.com/biztalkutilities

Reply to this Message

WSE 3.0 declarative security problem.

Free Magazines