Author: Admin

Can it get worse?

Doing a dc.SubmitChanges() causes App Pool to blow-up, and thus no response to BizTalk from the WebService.

What if you need to remove all the empty nodes in an XML document? It’ easy with this small subroutine. This might be useful to set fields to NULL when they have no value, especially when communicating between BizTalk and a WCF web service. You might often get serialization errors when, for example, a date/time field has an empty-string value. Better to pass no element to the web service (i.e. NULL) than a field with a bad value.

Serialization/Deserialization of .NET type “CHAR” (in my case, between WCF and BizTalk)

Nasty error:
The message could not be processed. This is most likely because the action
‘http://YourService/IYourInterface/YourMethod’
is incorrect or because the message contains an invalid or expired security context token
or because there is a mismatch between bindings. The security context token
would be invalid if the service aborted the channel due to inactivity.
To prevent the service from aborting idle sessions prematurely
increase the Receive timeout on the service endpoint’s binding…

This one can really drive you crazy if you don’t know the secret – click Article Title above to find out…

In my specific case, I was calling a WCF service that used LINQ to retrieve data from a database and return as a LIST of LINQ objects. When I ran 85 records, it would run, but when I ran 90 it would not, so I knew the issue was size related.

Sometimes, you might need to run a full WCF trace (on both the IIS web service, and the client).
The XML in this article will do that and discuss how to view it.

Rules (with static C# routines, such as PolicyChaining, or C# code that adds nodes to the XML), are working fine on XP but not on 2003 (or working on machine and not another). For example, we have a condition of 1=1, which should always fire, but if a static C# routine is found in the actions, then the rules does not fire.

System.Net.WebException: Unable to connect to remote server System.\et.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:80

BizTalk Server 2006 is not available or configured. Verify BizTalk Server 2006 on server xxxxx using management database BizTalkMgmtDb is accessible and configured with a compatible version.