I have Published a Biztalk WCF Service.
I am getting the following error when I try to invoke the service.
Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Net.DnsPermission, System, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
[SecurityException: Request for the permission of type 'System.Net.DnsPermission, System, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.]
System.ServiceModel.AsyncResult.End(IAsyncResult result) +4413209
System.ServiceModel.Activation.HostedHttpRequestAsyncResult.End(IAsyncResult result) +183
System.ServiceModel.Activation.HostedHttpRequestAsyncResult.ExecuteSynchronous(HttpApplication context, Boolean flowContext) +205
System.ServiceModel.Activation.HttpHandler.ProcessRequest(HttpContext context) +77
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
I even tried setting the identity to impersonate my login credentials but it does want to work.
This appears to be a Code Access Security issue. What credentials are your BT Instance running as? ALso look at the credentials that your IIS Server virtual directory that's hosting the WCF/SOAP adapter. What are the credentials for the app pool?
Both credentials must match and have permission to use the DNS lookup from CAS.
check the webconfig for wss_minimal or wss_medium trust levels. If you have windows sharepoint services installed, it may be blocking your WCF service. Good luck.
Hello did you ever solve this? I've got the same problem. Publishing a simple wcf with biztalk 2006 trying to browse it in IIS. And get the same error as you. The pequliar part is that System.Net version 18.104.22.168 does with public key "b77 etc" dows not exists in GAC, only 22.214.171.124 so my first thought is that IIS is using the wrong framwork sould be 126.96.36.199. Hm I'll test this
change this in web.config