A few interesting Microsoft Knowledge Base hotfixes for BizTalk Server 2006 were recently added and worthy of sharing.
- FIX: The Log Shipping feature may not restore database backup files in BizTalk Server 2006. Really?!? Seems kinda important. I love hotfix titles that are all nonchalant, but upon consideration, are pretty freaky. The article says that the only way Log Shipping can restore the databases is if there is already a complete set of backups, and, none of the backups are corrupt. I can only assume (since it isn’t stated anywhere) that this hotfix allows Log Shipping to restore any available backups, even if some are missing or corrupt.
- FIX: A receive location that uses the file adapter does not retry when a network failure occurs in BizTalk Server 2006. Apparently even if a receive location is set up to retry on network failure, that behavior isn’t consistent and the receive location may become instantly disabled. Good times.
- FIX: The per-instance configuration setting does not affect message processing on a computer that is running BizTalk Server 2006. If you have a request-response receive location, the per-instance pipeline settings on the send (response) pipeline aren’t applied, even though you can see the settings.
- Four properties have been added to the ErrorReport namespace context of BizTalk Server 2006 R2. We’ll end on a positive note. If you’d like a few new “ErrorReport” subscription values (ErrorReport.FailureTime, ErrorReport.FailureAdapter, ErrorReport.FailureMessageID, ErrorReport.FailureInstanceID), and are running BizTalk Server 2006 R2, this is the update for you.
Technorati Tags: BizTalk