With any new product to market, there are always hidden features waiting to cause you trouble. Unfortunately, this usually happens right before a demonstration or the night before a system goes live.Without quality assurance, things would be exponentially worse, but nothing or no one is perfect. The key to maintaining a successful implementation is your prowess at troubleshooting problems and taking the appropriate actions to accommodate these anomalies. By structuring these updates into timed releases, with the ability to provide hot fixes if necessary, a client or trade partner can plan to keep systems up for maximum availability.
BizTalk 2000 has already logged some items into Microsoft's online knowledge base, and appears to have some features working just a little under par.The release of BizTalk Server 2000 Service Pack 1, as with all service packs, is acknowledgment that this software is a work in progress. This chapter is based on personal experiences and hours of scouring online knowledge bases and newsgroups to bring together, at this time, a complete listing of major problems.We will also provide some interesting information on configuration settings that might assist you in your design and implementation of BizTalk 2000.
This section is designed to help the BizTalk developer address and avoid problems that arise during development. It cannot be a complete list of all troubles, of course, but is instead a discussion of some of the most common or most critical situations that you as a developer are likely to encounter. Ideally, the information provided here will help you troubleshoot your application before spending hours in the help files, the knowledge bases, and the newsgroups.
Was this article helpful?