BizTalk 2006

Failed to Serialize the Message Part

Bryan Corazza — Thu, 31 Aug 2006 20:57:00 GMT

Recently I ran into an issue with the SOAP adapter giving me the error 'Failed to Serialize the Message Part 'Foo'' ever so often. If I sent 20k messages through I was maybe getting about 100 messages suspended for this error. Now I spend about an hour looking at the messages that failed and I realized the problem really had 'nothing' to do with BizTalk and it was a serialization issue. I basically took the messages that failed and attempted to de-serialize them using a utility in .NET which is what the SOAP adapter is doing once the message is sent there. Needless to say I was getting the same message but this time I could see what field was causing the issue. It was a datetime type and it was blank.

So if your receiving this message please try to de-serialize the into a .NET type and see if you're getting the same error. There is something either missing or wrong about the data in your message. I just wish that the error message returning from BizTalk was a little more helpful here, like explaining what field is having the problem. Unfortunately I think that's a .NET issue and not a BizTalk one.

Using SSO with the SAP adapter and in general

Bryan Corazza — Sat, 29 Jul 2006 14:02:00 GMT

Here's my article on SSO. Now I have been a huge DotNetRocks fan forever. I love this show and their others (Mondays and Hanselminutes). I actually just created an application that crawls their sites for new torrents and downloads them. Might be posting that soon as I know a lot of developers that don't want to try to find all the old shows. Also if your a big torrent fan, like I am, get your hands on uTorrent, one of the first torrent clients built in C#. (gotta love it)

-B

More BizTalk Samples, oh my...

Bryan Corazza — Wed, 05 Jul 2006 13:05:00 GMT

Seems like they are making up for the fact that the samples for BizTalk 2004 weren't that great and some never worked at all without massive changes. Here are the new pile of great samples for BizTalk 2006. Thanks Luke. Happy downloading. Now I just need to find the time to look at these. Here's the full sample site from Microsoft.

-B

How to configure IIS for a BizTalk 2006 HTTP Receive Location

Bryan Corazza — Tue, 30 May 2006 19:47:00 GMT

First thing you need to do is to make sure that IIS's security is not going to be blocking your calls to the BTSHTTPReceive.dll. To do this goto your IIS manager and click on the Web Service Extension node and right click it and 'Add a new Web Service Extension'. Now browse to the location of BTSHTTPReceive.dll (by default installation its in <drive>:\Program Files\Microsoft BizTalk Server 2006\HttpReceive\ folder). Also remember to check the 'Set extension status to Allowed' checkbox. It is also a good idea to create a new application pool for your application to run in. When creating one make sure that the user account used is a member of the BizTalk Isolated Hosts group and the IIS_WPG group.

Now your going to create a new virtual directory in IIS under Default Web Site. Make sure you link the location of BTSHTTPReceive.dll in the content directory. Also make sure you use the new application pool you just setup. Make sure that both Read and Execute permissions are selected, and that Execute permissions are set to Scripts and Executables. After this you should be all set to start setting up your HTTP Receive Location within BizTalk Explorer. Enjoy.

-B

BizTalk 2006 Sample Released

Bryan Corazza — Thu, 25 May 2006 22:53:00 GMT

There's nothing like more samples for BizTalk. Get them here. They include using SSO as a configuration store, atomic transactions for COM+, collerating message within orchestration instances, etc. Enjoy.

-B

BizTalk Strong Name Generator Add-in

Bryan Corazza — Sun, 23 Apr 2006 19:09:00 GMT

I just installed and used this utility and I must say that I'm a HUGE fan of saving time (it is money!). Go here to download it. This add-in will add a menu item under your tools menu so once your BizTalk project is highlighted you can create an *.snk file.

To install the add-in, just compile the add-in project and add the *.add-in file and assembly into your Addin folder (Ex. C:\Documents and Settings\\My Documents\Visual Studio 2005\Addins\ ) and open VS2005 and goto your Add-in Manager and add it. This works for VS2005 and BTS2006.

Great job Jon and Carlos.

-B

New Blog from the BizTalk Product Team

Bryan Corazza — Thu, 23 Mar 2006 04:00:00 GMT

Here's the new blog from the BizTalk Product Team. Seems that BizTalk 2006 RTM is right around the corner here. Cannot wait for that as I am in the middle of the design phase at a large client and we are designing around 2006 and I was getting nervous that come May (start of construction phase) it still wasn't released. But I can finally sleep at night. We are also looking at using SQL Server 2005 Service Broker with BizTalk 2006 to replace an older MSMQ solution between two systems, and I'll be blogging about this in the near future. Currently we are building a POC for this at the client. I'll keep you posted.

-B

BizTalk 2006 Documentation

Bryan Corazza — Sat, 04 Feb 2006 16:34:00 GMT

I thought this was a great idea to put the documentation into CHM format for easy accessiblility and navigation. This is still for the beta 2 that is currently out and is the last public beta before the RC is released. There are some topics that are still missing however its still a pretty good read, especially on a long flight.

Here's it is.

-B

BizTalk 2006 Interchange Processing (Recoverable that is...)

Bryan Corazza — Tue, 24 Jan 2006 01:05:00 GMT

In testing out the new BizTalk 2006 feature of having Recoverable Interchange Processing I ran across settings in the pipeline component that also have to set up correctly in order for recoverable processing to work properly. You'll get a compilation error (Saying its unsupported) if you set Recoverable interchange processing to True and also have Validate document structure set to True. It seems that once recoverable interchange processing is turned on, the disassembler component splits up each message within the enveloping separately thus making the validation of the entire document impossible. Messages that are picked out of the interchange but are not successfully processed are placed in the suspend queue. However, unlike BTS 2004, we ARE able to continue processing the rest of the messages independently of the others within the same interchange. One thing that I've heard to look out for is when you are trying this with a flat file disassembler, when it is setup to ignore the header, and thus the header-less message is sent to the suspend queue (for various reasons) and this message is guaranteed to NOT be resumable as it no longer has a header to help properly identify it once it is re-processed. I haven't tested this out yet, just something I've read about.

My bud Stephen Thomas put up a good sample for this. There are mulitple samples on his site, so download them all and go to town. Enjoy.

Get it here.

-B

bye bye BizTalk, 2002 that is.

Bryan Corazza — Thu, 19 Jan 2006 20:30:00 GMT

My BizTalk 2002 project is finally winding down and needless to stay I'm excited. It was a very successful project but at the same time it was very frustrating to be tied down to old technology. Our team spent weeks upon weeks developing solutions that newer versions of BTS already fixed out of the box, it was a good exercise in self control. Its a great time to get back into BizTalk 2004-06 and WF. I just saw that the WinFX January CTP was released. Get it here. There seems to be significant changes from Beta 1 to 2 so grab up those bits and play around.

On another note, just some new BizTalk 2006 webcasts to wet your whistle.

Implementing End-to-End Sequential Processing in BizTalk Server 2006

High Availability, Fault Tolerance and Scalability with BizTalk Server 2006

Enjoy.

-B