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 are often several timeouts. Without knowing the details of how the adapter works, it may be unclear which one you need.
Here’s how you figure it out.
Continue reading “Find out which timeout is causing your transmission failure”
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 data from BizTalkDTADb, the BizTalk tracking database, which isn’t too hard to understand for yourself. Here are some ways to write your own queries to get the tracking information you need.
Continue reading “BizTalkDTADb tracking database”
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
Continue reading “System.ArgumentNullException: Value cannot be null. Parameter name: key”
If a BizTalk process is connecting to a database and it takes a very long time (more than about 10 minutes), you might encounter this error:
System.Transactions.TransactionException: The operation is not valid for the state of the transaction. ---> System.TimeoutException: Transaction Timeout
Continue reading “System.Transactions.TransactionException: The operation is not valid for the state of the transaction. —> System.TimeoutException: Transaction Timeout”
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
Continue reading “ORA-01013: user requested cancel of current operation”