<system.serviceModel>

  <serviceHostingEnvironment>

    <serviceActivations>

     <add relativeAddress="Service1.svc" service="configlessWCF.Service1"/>

    </serviceActivations>

  </serviceHostingEnvironment>

</system.serviceModel>

Hope this helps.

According to MSDN documentation, the MaxReceiveMessageSize is something that prevents a DOS attack, and it should still apply in the streaming case to the entire message size.

https://msdn.microsoft.com/en-us/library/system.servicemodel.channels.transportbindingelement.maxreceivedmessagesize.aspx

The error message you sometimes get looks like something like this.

Unhandled Exception: System.ServiceModel.CommunicationException: The maximum message size quota for incoming messages (1) has been exceeded. To increase the quo
ta, use the MaxReceivedMessageSize property on the appropriate binding element.
---> System.ServiceModel.QuotaExceededException: The maximum message size quota for incoming messages (1) has been exceeded. To increase the quota, use the MaxR
eceivedMessageSize property on the appropriate binding element.

There are a lot of timeouts in WCF. let us summarize it here.

Timeouts on binding

These are the most well known timeouts. SendTimeout, ReceiveTimeout, OpenTimeout and CloseTimeout. They can be set easily either through config or code on the Binding. The default value for those are 1 minute. 

E.g in code

Binding binding = new NetTcpBinding(SecurityMode.Transport)

SendTimeout = TimeSpan.FromMinutes(10),

ReceiveTimeout = TimeSpan.FromMinutes(10),

OpenTimeout = TimeSpan.FromMinutes(10),

CloseTimeout = TimeSpan.FromMinutes(10),

You will see some timeout exception such as

Unhandled Exception: System.TimeoutException: The open operation did not complete within the allotted timeout of 00:00:00.0010000. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: Open timed out after 00:00:00 while establishing a transport session to net.tcp://localhost:8080/FileService. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: Connecting to via net.tcp://localhost:8080/FileService timed out after 00:00:00. Connection attempts were made to 0 of 2 available addresses (). Check the RemoteAddress of yourchannel and verify that the DNS records for this endpoint correspond to valid IP Addresses. The time allotted to this operation may have been a portion of a longer timeout. 

Timeouts on ServiceHost

ServiceHost has OpenTimeout and CloseTimeout. Default for OpenTimeout is 1 minute, and default for CloseTimeout is 10 seconds.

ServiceHost host = new ServiceHost(typeof(FileService), new Uri("https://localhost:8443/FileService"));

host.OpenTimeout = TimeSpan.FromMinutes(5);

host.CloseTimeout = TimeSpan.FromMinutes(5);

Timeouts on client side channel

This is somewhat not as well known as the previous ones. There is an OperationTimeout, which you can set it by casting the channel to IContextChannel. You can do it through code. The default for this is also 1 minute.

IFileService channel = ChannelFactory<IFileService>.CreateChannel(binding, new EndpointAddress("https://localhost:8443/FileService"));

IClientChannel contextChannel = channel as IClientChannel;

contextChannel.OperationTimeout = TimeSpan.FromMinutes(10);

This is the exception you will get if you are hitting this operation timeout.

Unhandled Exception: System.TimeoutException: The request channel timed out attempting to send after 00:00:00.0100000. Increase the timeout value passed to the
call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.T
imeoutException: The HTTP request to 'https://localhost:8443/FileService' has exceeded the allotted timeout of 00:00:00. The time allotted to this operation may
 have been a portion of a longer timeout.

There is another not so well known timeout on tcp transport, called ChannelInitializationTimeout, and its default value is 5 seconds.

            BindingElementCollection be = binding.CreateBindingElements();

            TcpTransportBindingElement tcpBe = be.Find<TcpTransportBindingElement>();

            tcpBe.ChannelInitializationTimeout = TimeSpan.FromMinutes(1);

            CustomBinding customBinding = new CustomBinding(be);

Exception related to ChannelInitializationTimeout could look like:

Unhandled Exception: System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or
a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:00:59.9257860'. ---> System.Net.Socke
ts.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)
   --- End of inner exception stack trace ---

Timeouts in ASPNET

If you are web hosted, you should consider hitting timeouts set by ASPNET. There are shutdown timeout, just like the service host close timeout, default is 90 seconds. ExecutionTimeout, just like our operation timeout, default is 110 seconds.

<configuration>
  <system.web>
  <httpRuntime maxRequestLength="4000"
    enable = "True"
    requestLengthDiskThreshold="512
    shutdownTimeout="90"
    executionTimeout="110"
    versionHeader="1.1.4128"/>
  </system.web>
</configuration>

For more details on the ASPNET related timeout, please read https://msdn.microsoft.com/en-us/library/e1f13641.aspx

 [ServiceContract]

[AspNetCompatibilityRequirements(RequirementsMode = AspNetCompatibilityRequirementsMode.Allowed)]

[ServiceBehavior(InstanceContextMode = InstanceContextMode.PerCall)]

public class EchoService

[WebGet(UriTemplate="test/")]

public string Echo()

{

return "hello";

}

[OperationContract] 

void Test(string fileName, Stream fileContent);

If this is not a REST endpoint, you can work around this issue by using MessageContract wrapping the multiple parameters into one class.

If this is a REST endpoint, this programming model is actually supported because REST has its own formatter which handles multiple parameters correctly. However, if you continue to see this issue, then please make sure your WebHttpBehavior is set up correctly. Possible reason for not having that behavior set up correctly could be:

1. You are using a custom behavior, and its endpoint does not have the correct the contract name matching with the WCF contract;

2. You are not using WebEndpoint or WebServiceHost;

You can also workaround this issue by choosing Buffered option in the TransferMode on the binding. But that seems to be defeating the whole purpose of the Streaming.

Here is the solution:

Right click on the window you want on the taskbar, select move, hit any arrow button, move your mouse.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005 or above, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections..

You are not alone. There are a lot of solutions out on the web, the best i can find is this:

https://sequelserver.blogspot.com/2007/06/under-default-settings-sql-server-does.html

However, the error i am getting is actually because i have installed the full version of SQL without the SQL Express. However, my sql command was actually calling

sqlcmd -S localhost \sqlexpress -E -b –d databaseName -i sqlScriptPath

instead you need to call

 Right click on mouse, click Personalize->Display Settings ->Advanced Settings ... -> Monitor -> Properties -> Driver -> Update Driver ..., automatic updating should usually work.

 Then you should find the 1920 X 1200 as the highest resolution, select that and you should see everything clearly.

So this might be the reason. check the binding you have and make sure the negotiateServiceCredential has the same value. By default, it is true.

Reason? The server will use this flag to try to build the primary token resolver which is being used to resolve those key info clause. If that flag is ture, then the server will load the server certificate into the primary token resolver, so it will fail to resolve the key info if client sends one.

So where is that flag? Here is an example where this could be located:

<wsHttpBinding>

<binding ...>

algorithmSuite="Default" establishSecurityContext="true" />

</security>

</binding>

</wsHttpBinding>

 Hope this helps!

https://www.microsoft.com/china/technet/teched/speakers/default.mspx