-
-
Here’s another thing we bumped into recently that took a lot of time to find and fix.
In a project in which I’m sideways involved a BizTalk generated WebService was deployed using a setup project. These projects by default include all dependencies, which are all BizTalk assemblies. Deployed this way, our webservice did not work, without any error logged in either the HAT or the event log. We did see that BizTalk was involved by incomplete messages in the HAT. Turned out that when we removed all dependency assemblies from the bin folder of the webservice it worked great. We choose to remove dependencies from the setup project and that fixed it.
-
-
I have written a custom adapter over two years ago that worked a charm back then. Recently I had to use it again in a little project. It worked, but not when an error occurred on transmission. In that case it failed with the following errors in the eventlog:
“The Messaging Engine encountered an error while suspending one or more messages”
and
“The Messaging Engine encountered an error while deleting one or more messages”
After attaching the Visual Studio debugger to the BizTalk Host process and setting breakpoints on all Exceptions, I saw it failed on a closed stream. As clean as I am, my adapter closed and disposed everything inclused the stream I got from GetOriginalDataStream. And that is not allowed. After I fixed that, everything worked great!
-
-
I haven’t written anything here for a long time, but since I installed Vista and Office 2007, I should also try the blogging service. I know, I know, half the world tried. In fact, I did too, but didn’t get it to work because of a bug that is supposed to be fixed. In the meantime I was involved in two nasty BizTalk issues, which I will blog about later on.