PolicyException when using DotNetOpenAuth library?

Oddly, I found the solution was related to this.

Oddly, I found the solution was related to this. The application pool identity has a property called Load User Profile. When this value is false, you may receive the error shown above.To resolve this, open IIS Manager and navigate to your application pool identity.

You will find the setting in the Advanced Settings window. Change it to true. I found that when I set it to true, the library began working again.

When I flipped it back to false it continued to work even after service restarts and app pool recycles. So, strangely everything seems okay now.

OMG OMG OMG OMG OMG YES I AM GOING FULL CAPS HERE, THANK YOU TLIANZA! I have been pulling my hair out over this for weeks after moving to a new server with iis7! THANK YOU – MvcCmsJon Nov 23 '10 at 22:50.

It looks like Code Access Security does not consider DotNetOpenAuth to be loading with full trust. It only needs medium trust, actually, but here is the list of minimum permissions DotNetOpenAuth requests: assembly: SecurityPermission(SecurityAction. RequestMinimum, Execution = true) assembly: WebPermission(SecurityAction.

RequestMinimum, ConnectPattern = @"http://. *") assembly: WebPermission(SecurityAction. RequestMinimum, ConnectPattern = @"https://.

*") The second couple MAY be missing from some Medium trust configurations, but again if you're running with full trust it should be a non-issue. Try adding to your web. Config file in its section and see if that either helps, or generates an error that will help you narrow down the problem.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.