NOTE: Following are the contents of the Readme file as it shipped with the product listed above. It has not been edited by the Microsoft Developer Support Knowledge Base editing team.
This readme contains important, late-breaking information about this release of Microsoft BizTalk Server 2000.
Caution
For critical information about installing BizTalk Server 2000 and updating required components, see Installing BizTalk Server 2000 and Updating BizTalk Server 2000 and Windows 2000 Components in this readme.
Important
Prior to installing BizTalk Server, it is strongly recommended that you review this readme as well as the Microsoft BizTalk Server 2000 Installation Guide. The installation guide provides detailed instructions for installing BizTalk Server on a single computer. You can find the installation guide in the following directory on the BizTalk Server installation drive: \Program Files\Microsoft BizTalk Server\Documentation.
A comprehensive set of BizTalk Server 2000 documentation is provided with this product. To use the documentation after you install BizTalk Server, click Start, point to Programs, point to Microsoft BizTalk Server 2000, and then click BizTalk Server Documentation.
Known Issues for the BizTalk Server 2000 Release
The following are known issues for this release of BizTalk Server 2000. To view the known issues, click one of the following headings to expand the topics.
Installing BizTalk Server 2000
Microsoft SQL Server requirements when installing BizTalk Server 2000 on Microsoft Windows 2000 Server or Advanced Server
Issue: BizTalk Server 2000 can be installed on Microsoft Windows 2000 Server or Windows 2000 Advanced Server, with the NTFS file system. Microsoft Internet Explorer 5.0 (or later) and Microsoft Visio 2000 SR-1 are required. In addition the computer installed with BizTalk Server 2000 must have read/write access to a server(s) installed with Microsoft SQL Server 7.0 (SP2 or later) or Microsoft SQL Server 2000 under one of the following conditions:
SQL Server must be installed on the same computer as BizTalk Server 2000.
Or
The computer that runs BizTalk Server 2000 must have read/write access to a remote computer(s) running SQL Server.
Microsoft SQL Server requirements when installing BizTalk Server 2000 on Microsoft Windows 2000 Professional
Issue: BizTalk Server 2000 can be installed on Windows 2000 Professional (or later), with the NTFS file system. Internet Explorer 5.0 (or later) and Visio 2000 SR-1 are required. Additionally, the computer that runs BizTalk Server 2000 must have read/write access to a server(s) running Microsoft SQL Server 7.0 (SP2 or later) or SQL Server 2000.
Updating BizTalk Server 2000 and Windows 2000 Components
Updating Windows 2000 components for BizTalk Server 2000
Issue: Several Windows 2000 components must be updated to ensure the stability and correct functionality of BizTalk Server 2000. An updated list of required and suggested updates is available on the Microsoft BizTalk Server 2000 Web site (www.microsoft.com/biztalk/). You can download the updates directly from the location given on the Web site, or call Microsoft Product Support Services (PSS) and request them. Requesting updates from PSS is a free call.
BizTalk Messaging Services
Processing SMIME signed and/or encrypted messages generates errors
Issue: While processing SMIME signed and/or encrypted messages within BizTalk Messaging Services, errors such as "The parameter is incorrect" and "Decryption Failed" might appear.
The BizTalk Server service does not shut down when the server is out of memory
Problem: If the server on which BizTalk Server is installed runs out of memory, the BizTalk Server service still attempts to process documents. All documents are placed on the Suspended queue.
Solution: Restart the BizTalk Server service.
Errors that are caused by a custom script might not be displayed in the Event Viewer
Issue: Some errors returned by Microsoft XML (MSXML) Parser within a custom script function may not be passed to the server. Errors associated with a document in the Suspended queue may not reflect the error returned in the script.
Large Data Segments in an IDOC document are not posted to an SAP system
Problem: When large Data Segments are used in an IDOC document that is routed to an SAP system for processing, some of the data may not be processed. This may be caused by a timeout value configured on the SAP system.
Solution: Try changing the timeout value on the SAP system.
Document specifications, envelope specifications, and maps are stored in two locations
Issue: If a specification or map is modified with BizTalk Editor or BizTalk Mapper and then saved to the repository, the specification or map must be reloaded into the BizTalk Messaging Manager so the server can recognize the changes and the database content can be updated.
Encountering memory failures when running BizTalk Messaging Manager on a per-user installation of BizTalk Server 2000
Problem: If BizTalk Server 2000 is installed for an individual user (by clicking the Only for me option during installation), when running BizTalk Messaging Manager, you will encounter an insufficient memory error.
Solution: On the BizTalk Server 2000 CD, follow the instructions in the Support/SetupCurrentUser folder.
Message Queuing receive function does not accept a pass-through submission
Problem: Message Queuing receive functions shut down and the following error message is displayed: Change this receive function to accept pass-through submissions or remove the pass-through document from the queue.
Solution: The receive function is not configured to accept pass-through submissions; however, the receive function received a document that was sent as a pass-through submission. Write an application that examines the queue for the
AppSpecific property of messages in the queue to determine which document came through as a pass-through submission. Remove the document and restart the receive function.
BizTalk Orchestration Services
Visual Basic components are not available for binding in the COM Component Binding Wizard
Problem: When a Microsoft Visual Basic component is being debugged, it is not listed in the COM Component Binding Wizard in the BizTalk Orchestration Designer.
Solution: You must bind the port to the COM component when Visual Basic is not in debug mode.
Testing for the outcome of a transaction
Issue: To test for transaction outcome you should use a message created in the transaction on-failure process. You should not test for transaction outcome by testing for the existence of a message used in the transaction. In the case of failure, you should not use any messages that the transaction may have modified except in that transaction on-failure process.
Standard toolbar is not visible after starting BizTalk Orchestration Designer
Problem: When starting BizTalk Orchestration Designer, the standard toolbar might not be visible because settings from a previous session have not been saved.
Solution: You must manually select the standard toolbar in Microsoft Visio.
- On the File menu, select Exit to close BizTalk Orchestration Designer.
- On the Start menu, point to Programs and click Microsoft Visio.
- On the View menu, point to Toolbars and click Standard.
- On the File menu, select Exit to close Visio.
- On the Start menu, point to Programs, point to Microsoft BizTalk Server 2000, and then click BizTalk Orchestration Designer.
The toolbar appears.
XLANG schedule drawings created in the beta release of BizTalk Server 2000 are not compatible with drawings created in the released version
Issue: XLANG schedule drawings (.skv files) that are created by using BizTalk Orchestration Designer in the beta release of BizTalk Server 2000 are not compatible with the format used by the released version of BizTalk Server 2000.
Limitation in COM+ Bring Your Own Transaction (BYOT) functionality
Problem: COM+ Bring Your Own Transaction (BYOT) functionality enables a component to be created with, or to inherit, an external transaction. Due to a limitation in BYOT functionality, you will encounter unexpected behavior if COM+ hasn't been initialized in the process where BYOT is to be used.
If a BYOT component is imported into a COM+ application, it will fail to launch traditional COM components. BYOT functionality is provided by a component called Byot.ByotServerEx, which is registered as a traditional COM component, not a COM+ application.
Solution: When using BYOT functionality with COM components for the XLANG Scheduler Engine, you must create a wrapper component that is written and installed into a COM+ application. All method calls to the component will be forwarded from the wrapper component. Documentation in the MSDN Library offers an alternate work around, which is to wrap the Byot.ByotServerEx into a COM+ application. This will, however, create unexpected behavior when trying to reference traditional COM components.
Remove the PDC evaluation copy of Microsoft Visio 2000 prior to installing Visio 2000 Standard Edition (SR-1)
Issue: The 2000 Professional Developers Conference (PDC) CD-ROM included an evaluation copy of Microsoft Visio 2000 Standard Edition. This version of Visio 2000 must be removed. Unexpected behavior will result if you upgrade the evaluation version to Visio 2000 Standard Edition (SR-1). The Visio32.exe installed by Visio 2000 Standard Edition has a file version of 6.0.0.2072 and timestamp of February 07, 2000. The Visio32.exe installed by the evaluation copy provided at the PDC has a file version of 6.0.0.2072, and a timestamp of April 25, 2000. Other than the time stamp, there is no discernible difference between the two releases.
Visual Basic AIC components might suspend operation or generate an access violation inside MSVBVM60.DLL when called under stress from BizTalk Server
Problem: A Visual Basic AIC component might suspend operation or generate an access violation if a Visual Basic ActiveX DLL is hosted in a multi-threaded environment, such as Microsoft Internet Information Services, Microsoft Transaction Services, or BizTalk Server and the
Retain In Memory project setting is not enabled.
Solution: Ensure that all Visual Basic components set the
Unattended Execution and
Retain In Memory project settings. For more information on this problem and how to implement this change, see the
241896�
article on the Microsoft Knowledge Base site.
Messages created in a while loop appear with empty fields after the end of the while loop
Problem: Testing for the existence of messages (by using the system field, MessageName.[__Exists__]) after a while loop always evaluates to TRUE. This problem occurs when the path taken in the while loop does not create the message because of the decision branch taken or a transaction abort.
Solution: Do not test for the existence of messages after the while loop. Instead, to check for flow control, use a stateful component to note the path taken in the while loop and use this information in the stateful component outside the loop.
All messages of the same type on the same port must match exactly
Problem: A compilation error occurs indicating that the XLANG schedule drawing contains conflicting specification representations.
Solution: When you use the XML Communication Wizard, make sure all messages of the same type on the same port match exactly. This includes field names, message types, and XPath queries. The location of the specification must also be the same. On the
Message Specification Information page of the XML Communication Wizard, make sure that the
Validate messages against the specification check box is selected consistently.
BizTalk Orchestration Services Code Samples
Issue: Sample files are located in the XLANG Samples folder in the Microsoft BizTalk Server installation drive. Browse to \Program Files\Microsoft BizTalk Server\SDK\XLANG Samples on the installation drive to find the sample files. This is only a relative path. Depending on your installation of BizTalk Server 2000, you might have to modify this path.
The following samples are available in the BizTalk Server 2000 SDK.
Collapse this tableExpand this table
| Sample folder name | Readme file | Description |
|---|
| ASP | ReadMe.htm | CreditCheck. This sample demonstrates how to call a schedule from ASP script, passing in data and getting back the result. |
| Dispatcher | ReadMe.htm | Dispatcher. This sample demonstrates a dispatcher application that sends and receives documents on behalf of a client application. |
| Dynamic Binding\COM | ReadMe.htm | Scramble. This sample demonstrates how to bind dynamically to a COM component. |
| Dynamic Binding\Queue | ReadMe.htm | QueueBind. This sample demonstrates how to bind dynamically to a message queue. |
| Integrating BizTalk Services\BTF Correlation | Readme.doc | Stateful Conversation. This sample illustrates the use of BizTalk Framework 2.0 and BizTalk Orchestration Services to accomplish stateful interoperability between two applications. |
| Integrating BizTalk Services\http | Setting Up HTTP Sample.doc | Using the HTTP Transport. In this sample, there are three organizations: purchaser, supplier, and inventory. The purchaser submits a purchase order to the supplier. The supplier then forwards this order to its inventory organization, and the inventory organization sends back an acknowledgement to a dynamic port set up by the supplier. |
| Integrating BizTalk Services\non-http | Setting Up Non-HTTP sample.doc | Using a Non-HTTP Transport. In this sample, there are three organizations: expense requestor, finance, and marketing. The expense requestor organization submits an expense request to the finance organization. The finance organization forwards this request document to the marketing organization. The marketing organization sends back an expense reply to a per-instance queue set up by the finance organization. This reply indicates whether or not the expense was approved. |
| Iteration | ReadMe.htm | LineItems. This sample demonstrates how to iterate through a list of items and process each item independently. |
| Loop | ReadMe.htm | Retry. This sample demonstrates how to use the While shape to retry a business process a limited number of times. |
| NestedTxns | ReadMe.htm | Nested Transactions. This sample illustrates three concepts: Nested Transactions, Aborting a Transaction, and Compensation. |
| Personalized Queues | ReadMe.htm | Very Long-Lived, Per-Instance Queue. This sample uses a shared queue and per-instance queues. |
| PublicInterfaces | ReadMe.htm | XLANG Public Interfaces. This sample demonstrates how to use the XLANG Public Interfaces to enumerate and manage the running schedule instances, and the XLANG host applications. |
| QueueListener | ReadMe.htm | QueueListener. This sample demonstrates how to continuously monitor a queue for data, and start another XLANG schedule when new data is available. |
| Transaction Abort | Abort handler sample.htm | Abort Handler. This sample demonstrates how to handle an exception. |
| WorkFlowAudit | readme.txt | WorkFlowAudit Component. This sample contains one interface, IUserEvent. |
| WorkFlowAuditClient | readme.txt | WorkFlowAuditClient. After you register the component in this sample, run the WorkflowAuditClient.exe application. |
| XML Translation | ReadMe.htm | Loopback. This sample demonstrates the use of SubmitSync to perform an XML transformation. |
Cannot open BizTalk Orchestration Designer
Problem: One or more of the files in the VBA folder have not been properly registered or have become corrupt. This problem can result from uninstalling Microsoft Office.
Solution: If Microsoft Office 2000 is not installed:
- Insert the Microsoft Office 2000 CD into the disk drive.
- Open Windows Explorer and browse to d:\Install\BIN\SP\VBA (where 'd' is the letter of your CD drive).
- Right-click Vba6.msi, and click Install.
If Microsoft Office 2000 is installed:
- Open Microsoft Access.
- Create a blank database.
- Save the database.
- Close Microsoft Access
Internet Explorer cannot open certain XLANG schedule files
Problem: Some XLANG schedule files (.skx files), especially schedules that use constant values, cannot be viewed using Internet Explorer 5.5 or earlier versions.
Solution: Use a text editor such as Microsoft Notepad to view the XLANG schedule file.
Non-XML string data is truncated when an XLANG schedule receives data from BizTalk Messaging Services
Issue: When non-XML text documents are received by an XLANG schedule from a port that is implemented by Message Queuing or BizTalk Messaging, carriage-return (CR) characters are removed from the document when it is received by the schedule. This is problematic when a MIME-encoded message is sent to a schedule that must later send or use the data elsewhere. In this case, the document sent out by the schedule does not contain the CR characters and does not appear to be a valid MIME-encoded document.
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, people and events depicted herein are fictitious and no association with any real company, organization, product, person, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
Copyright 19992000 Microsoft Corporation. All rights reserved.
Microsoft, ActiveX, BizTalk, MSDN, MS-DOS, Visio, Visual Basic, Visual Studio, Windows, and Windows NT, are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.