- This topic has 1 reply, 1 voice, and was last updated 9 years, 3 months ago by
.
-
Posts
-
-
Hello,
We’ve had Biztalk working successfully for quite some time, but recently ran into some problems. We have a simple setup using Summit to bring HL7 messages in, transform them in Biztalk and sent them back out through Summit. Last week, Biztalk continued accepting messages normally, but was not sending them back out. Looking in the HAT, it shows that the messages were received, but then showed Unparsed Interchange instead of the outgoing port/schema. This was not happening consistently, more at random. We do process more than 100,000 messages daily through Biztalk and it’s never been a problem before. We did upgrade to 64bit several months ago because we ran into throttling problems, but that seemed to be resolved with the upgrade. Our server has 8 CPUs and 16GB of RAM, running Windows Server 2003 R2 64 bit.
Another thing – we didn’t have any idea this was going on until we started getting messages from other departments alerting us to the fact that they weren’t getting messages they expected. None of our alerting was triggered by these issues. It’s like Biztalk just swallows them up. Resending has not worked either.
Can anyone assist? Has anyone else ever seen this problem?
Thank you in advance,
April
-
April,
I’m sure that you have checked this, but do you have any warning or error events in the Event Log, or suspended (resumable or non-resumable) messages in BizTalk?
This could also be a edge-case bug that only manifests itself in the 64-bit version. Alternatively, are there any logs you can use in the Summit package that might shed any light on this?
Nick.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.