nettcpbinding

问题 I'm getting the following error when hosting WCF Net.Tcp service on windows 8.1 machine where I'm in the administrators group: The service endpoint failed to listen on the URI 'net.tcp://localhost:9001/dataservice' because access was denied. Verify that the current user is granted access in the appropriate allowAccounts section of SMSvcHost.exe.config. I even added the user to the config as suggested: <?xml version="1.0" encoding="utf-8"?> <!-- The configuration file for SMSvcHost.exe -->

问题 I'm getting the following error when hosting WCF Net.Tcp service on windows 8.1 machine where I'm in the administrators group: The service endpoint failed to listen on the URI 'net.tcp://localhost:9001/dataservice' because access was denied. Verify that the current user is granted access in the appropriate allowAccounts section of SMSvcHost.exe.config. I even added the user to the config as suggested: <?xml version="1.0" encoding="utf-8"?> <!-- The configuration file for SMSvcHost.exe -->

问题 First of all, sorry, i'm not fluent. I'm trying to figure out why my WCF services stop working when we have an environment with high calls/second rate. I'm not sure that just increasing timeout will solve the issue. We have 2 webservices: The first is hosted on IIS 7.5, Windows Server 2008 R2 Enterprise SP1 x64, with AppFabric (and WAS) Second, hosted on Windows Service, Windows 2003 R2 SP1 x86 Both webservices have minimum configuration: No authentication, No trasaction, Without special

问题 First of all, sorry, i'm not fluent. I'm trying to figure out why my WCF services stop working when we have an environment with high calls/second rate. I'm not sure that just increasing timeout will solve the issue. We have 2 webservices: The first is hosted on IIS 7.5, Windows Server 2008 R2 Enterprise SP1 x64, with AppFabric (and WAS) Second, hosted on Windows Service, Windows 2003 R2 SP1 x86 Both webservices have minimum configuration: No authentication, No trasaction, Without special

问题 First of all, sorry, i'm not fluent. I'm trying to figure out why my WCF services stop working when we have an environment with high calls/second rate. I'm not sure that just increasing timeout will solve the issue. We have 2 webservices: The first is hosted on IIS 7.5, Windows Server 2008 R2 Enterprise SP1 x64, with AppFabric (and WAS) Second, hosted on Windows Service, Windows 2003 R2 SP1 x86 Both webservices have minimum configuration: No authentication, No trasaction, Without special

问题 We have a WCF service ( NetTcpBinding ) that sits behind a load balancer. I've read that in order to avoid "stickyniss" I have lower the LeaseTime the channels get in the channel pool. I've only found samples how to set this value using the config file, but I would like to set it programmaticaly, any pointers? 回答1: You can access the LeaseTimeout property via the TcpTransportBindingElement , through the ConnectionPoolSettings property: TcpTransportBindingElement tcpBE = new

问题 I am trying to figure out why my NetTcpBinding Service is not maintaining state, as expected. (Perhaps I did it wrong) I have a WCF service with the following structure(simplified): Message Contract [MessageContract] public class StreamMetaData { [MessageHeader] public string Info {get; set;} [MessageBodyMember] public Stream Data { get; set; } } Contract ServiceContract(SessionMode = SessionMode.Allowed)] public interface IMyService { [OperationContract] void Init(StreamMetaData metaData);

问题 This question already has answers here : what is the global.asax Application_Start equivalent when using WAS in IIS7 (2 answers) Closed 5 years ago . I have a WCF application that requires some app initialization code to fire when the app starts. Currently the code sits in my Application_Start method in global.asax.cs: protected void Application_Start(object sender, EventArgs e) { // Whatever.. } However, my WCF app has both http (asp.net) and TCP (netTcpBinding) endpoints, depending on what

问题 Our server is WCF based and it is hosted by IIS. We use nettcp as our binding. The app is working but we still have one thing unclear to us: Since we are not specifing a port # in our configuration, what is the default port that WCF/IIS uses? In production environment, do we need to manually open a port in IIS for WCF/NetTcp? 回答1: The default port is 808. You can learn more about it here: How to: Configure a Windows Communication Foundation Service to Use Port Sharing. Make sure you open port

问题 I have a standalone WCF service running on a server behind a firewall. It currently uses wsDualHttpBinding as the service utilizes callbacks. The client works fine in a LAN environment. We have opened the firewall to allow traffic on a custom port and so the discovery of the service now works from outside LAN. Due to the nature of wsDualHttpBinding this obviously cannot work if the client is behind a firewall of its own. So naturally, netTcpBinding comes to mind which should solve the