BizTalk Server Team Blog - All Comments

re: BizTalk Server 2010 R2

Steef-Jan Wiggers — Fri, 09 Dec 2011 13:57:36 GMT

Thanks for outline on new BizTalk Server 2010 R2 release.

re: BizTalk Server 2010 R2

Drilon Blakaj — Thu, 08 Dec 2011 13:58:55 GMT

We, who work with integration welcome R2 but customers will appreciate it even more. Glad to se investments wich of course leads to improvements. I'm seeing forward to the future developement of this great product wich is a pillar of many successfully companies.

re: HIPAA 5010 Errata support now available for BizTalk Server 2009

Tord G.Nordahl — Tue, 11 Oct 2011 13:43:25 GMT

I had the same problem as dlindhurst, thanks for the solution to the problem dlindhurst!!

re: Improved Productivity with BizTalk Server 2010 Mapper

Steef-Jan Wiggers — Sat, 08 Oct 2011 19:49:33 GMT

Great enhance and will improve productivity of developer when he/she creates a map.

re: BizTalk Server 2010 AppFabric Connect for Services

Steef-Jan Wiggers — Sat, 08 Oct 2011 19:43:45 GMT

Excellent post and very useful for dutch article I wrote on this topic.

re: BizTalk Server 2010 AppFabric Connect for Services

Steef-Jan Wiggers — Sat, 08 Oct 2011 19:43:08 GMT

Excellent post.

re: HIPAA 5010 Errata support now available for BizTalk Server 2009

dlindhurst — Fri, 19 Aug 2011 21:30:03 GMT

I was able to find a solution to my problem listed above. It turned out to be related to message tracking being enabled on some receive ports that I was unaware were configured as such. A large number of tracking instances had been added to the TrackingData_x_x tables in the msgboxdb. I ran the bts_CleanupMsgbox stored proc to clean the msgboxdb and everything seems to be running smoothly now.

re: HIPAA 5010 Errata support now available for BizTalk Server 2009

ckress-vbstuff — Wed, 30 Mar 2011 13:53:27 GMT

Is there any timeline for Hipaa Errata 5010 TR3 update for Biztalk 2010?

Thanks

re: HIPAA 5010 Errata support now available for BizTalk Server 2009

dlindhurst — Tue, 29 Mar 2011 15:14:18 GMT

After installing the hotfix on my local development machine, everything seems to be working perfectly. However, after installing it to a shared Dev/QA server things seem to be misbehaving.

The server in question is running BizTalk 2009 on Windows Server 2003 R2 SP2 on a VMWare box with AMD processors. The BizTalk databases are located on a remote SQL 2008 server, also running in a VMWare environment.

After installing the hotfix on the server, I noticed a spike in processor usage by a specific host instance on the server dedicated to tracking. The processor spikes to 100% for 3-5 minutes before crashing. When the host instance crashes, I get the following errors repeatedly:

Error 1 : Faulting application btsntsvc.exe, version 3.8.368.0, stamp 49b1dadf, faulting module kernel32.dll, version 5.2.3790.4480, stamp 49c51f0a, debug? 0, fault address 0x0000bef7.

Error 2: Reading error. Exception information: Critical error encountered. SQLServer: SQL2K8\BIZTALK, Database: BizTalkMsgBoxDb.Exception of type 'System.OutOfMemoryException' was thrown..

Error 3: Execute batch error. Exception information: Critical error encountered. SQLServer: SQL2K8\BIZTALK, Database: BizTalkDTADb.Exception of type 'System.OutOfMemoryException' was thrown..

Does anyone have any idea how I can fix this?

Thanks in advance for your help.

re: BizTalk Server 2010 released for manufacturing!!!

Rohit.Sharma — Thu, 13 Jan 2011 15:36:35 GMT

Has there been any improvements to the Orchestration engine?

There are few common scenarios requiring the implementation of following:

A loop having parallel shape with one branch having Receive Shape following the correlation and the other shape having timer to terminate the orchestration.

And this is a well known scenario creating Zombie messages since the release of BizTalk server 2004. Of course it is not possible to address each and every scenario but has product team every try to address this particular scenario.

From developer point of view one possible solution that would be to introduce a new shape for orchestration which can be used just after the timer to kill the instance subscription (may be based on the correlation) so that no new message can’t be added to the queue and if any has already been added (Mean there are some unconsumed messages in the queue) then this shape should throw some exception which developer can handle by knowing that there are still some messages which need to be consumed.