In recent days the Cumulative Update #2 has been released with several improvements
and fixes.
(The team have done an amazing job addressing previous issues/fixes with currently
*no* open issues!!! WELL DONE GUYS)
As you may well know by know – BizTalk is made by people who care for Integrators
(us) who care. BizTalk has always been a quality product in the past and in my opinion
will be in the future.
Here’s some details if CU2 that was passed onto me
——————————————-
Hi,
It is a pleasure to announce the release of CU2 for BizTalk Server 2010 on
behalf of the BPD Sustained Engineering group. With this CU, we have addressed
all known customer issues from all branches of BizTalk (i.e. applicable to BizTalk
2010) and also available in multiple locales.
This CU includes few serviceability improvements along with product updates based
on customer requests. Some of the notable updates in this CU are:
-
Transparent CU Setup: Provides info on number of fixes applicable
to feature during installation -
Enhanced EPM debug Tracing: Helps the support team isolate specific
failures in a large volume scenario -
BizTalk Host Instances not coming back-on-line after SQL being off-line:
Allows to restart the BizTalk service automatically when SQL connectivity is restored -
BAM Archive checks & Logging before dropping tables from BAMPI: Prevents
possible data loss scenarios when archiving fails unexpectedly and also allows for
a user configurable setting on the rate of archiving. -
Applications stop responding or crash when System Center Operations Manager
monitors BizTalk Server applications: Issue was caused by a race condition
in one of our internal class and has been fixed in this release.
|
Fixes Per Feature Area |
Blog Post by: Mick Badran