Category: Support

Find out which timeout is causing your transmission failure

One of the more common BizTalk connection problems to end systems is a timeout. Maybe you are dealing with an unexpected spike in data, or perhaps your connection is just a bit lethargic today. No problem, just extend the timeout, right? Errm… which one? If you look at the port bindings, you can see there… Continue reading Find out which timeout is causing your transmission failure

BizTalkDTADb tracking database

BizTalk administrators often rely on tracking data, which shows you past events that happened in BizTalk. Querying this information through the BizTalk Administration Console can be quite slow if you have a large tracking database, and also has a learning curve before you can construct the right queries. Fortunately, many of these queries just return… Continue reading BizTalkDTADb tracking database

System.ArgumentNullException: Value cannot be null. Parameter name: key

Many of the in-built BizTalk adapters used WCF, including connections to Microsoft SQL Server, Oracle databases, and web services. BizTalk is very strict about supplying a SOAP Action header, and if you forget to specify it in the send port, you will get this particularly unhelpful error: System.ArgumentNullException: Value cannot be null. Parameter name: key

ORA-01013: user requested cancel of current operation

If you’re using BizTalk to connect to an Oracle database via a WCF-Custom port, you might encounter a suspended message with this error. It’s a simple Oracle timeout error, but it’s not always obvious where/how to extend the timeout. ORA-01013: user requested cancel of current operation