Yossi Dahan [BizTalk]

Google
 

Friday, April 28, 2006

"Unexpected end of document. This is not a new document. The dissassembly is incomplete. " and BAM

It took me a short while to figure out, so I thought it's worth posting this as it might be useful for someone else out there..

I'm using BAM to track messaging properties through using TPE.

I've made a mistake in the tracking of one of the properties I used in the send port (type mismatch)

This had casued the messaging process to fail and the following error appeared in the even tlog - "Unexpected end of document. This is not a new document. The dissassembly is incomplete. "

Not a very clear error, but anyway...

Strangely enough if I'm doing the same mistake, but using the property from the receive port (rather then the send port) a BAM error is logged in the event log but the process compleyes ok.

This caused me to start thinking - do I want my process to stop if tracking failed? well - that depends in the process, sometimes I do, sometimes I don't. I wonder if this is configurable somewhere... Anyway - at least is should be consistend, shouldn't it?

0 Comments:

Post a Comment

<< Home