Part 2 of my "Reloaded-Series"! In the orginal post here TCPBinding seemed to be the solution. But it is not the best and in some cases just not usable. This only applies to large requests! Sabrina and Philippe, both colleagues in the current project, discovered something far better and much more interesting... What happnes here is DOS-attack-prevention by IIS! Fortunately this did not apply to us that much, sitting behind the DMZ and a far way from the outside world... Solution: Change the allowed ......
A WCF Service we call from BizTalk using WCF BasicHTTP usually works fine but all of a sudden it started returning 401 errors for some calls while others continued working as expected so it could not have been a "real" 401. The difference was the size of the message. One parameter of the service is a rather complex object. In the cases we got a 401 it got quite big (containing a lot of customer-data), say 5 MB. So we turned on tracking. The messages we traced out where about 20MB. Not too big for ......
Two posts on one day? Is he on his holidays? Yes! We had a lot of trouble with this error: ...Error Description: System.ServiceModel.Communi... An error (The request was aborted: The request was canceled.) occurred while transmitting data over the HTTP channel.... You find a few posts about it in the www but the answers are somewhat conflicting and not very nice. No, I will not tell you the answer in this post, because we still do not really have it, but I want to show you how to perform ......
A WCF Service I provided took a very simple data contract as parameter (containing one string and one int...) and had a very simple task to do. A .NET 3.5 client was created using the VS2008 feature "Add Service Reference". Everything worked as expected. Then a slight change came in: The client was expected to run on machines with .NET 2.0 only. So we set the Target Framework to .NET 2.0, removed the references to System.ServiceModel, System.Runtime.Serialization and the ServiceReference and created ......
It happens once in a while (to me at least): You get an XML schema and your task is to create a WCF service that accepts this data as parameter or uses it as return value. So you generate a class from the schema using xsd.exe (like "xsd XMLSchema1.xsd /c /l:CS /n:mipsen.schemas"). You create your ServiceContract and implementation (adding ServiceKnownType to avoid funny behaviour concerning the schema-generated class), create the web.config and svc-file and host your service (in IIS, for example). ......