© 2001 Microsoft Corporation. All rights reserved.
Welcome to Microsoft BizTalk Server 2002. This Readme file contains important, late-breaking information about BizTalk Server 2002 that might not be included in the online documentation (BizTalk Server 2002 Help).
Caution
Important
The following are known issues for this release of BizTalk Server 2002.
After installing BizTalk Server, reboot the computer. If you do not reboot, and you submit a document using the HTTP receive function, you might receive internal server errors indicating that inetinfo.exe is unable to locate a dynamic-link library (DLL).
If a data source name (DSN) of any kind (user, system, or file) is created with Microsoft SQL Server authentication, the password is not saved in the DSN and the XLANG Scheduler Engine will not be able to use that DSN for persistence. BizTalk Server 2002 requires Windows Authentication to access SQL Server.
Problem: If you perform a custom installation of BizTalk Server and select only BizTalk Messaging Manager, the BizTalk Server setup process does not register two DLLs that are required for BizTalk Messaging Manager to function properly.
Solution: To correct this, you must register MSCSCore.dll and MSCSResource.dll. These files can be found in the following directory: \Program Files\Common Files\Microsoft Shared\Enterprise Servers\Commerce.
In BizTalk Server 2002 Help, the "Custom Installation" topic states:
BizTalk Messaging Manager will not run unless the World Wide Web Publishing Service is running.
However, if you performed a custom installation to install BizTalk Messaging Manager as a standalone client on a computer, the World Wide Web Publishing Service does not need to be installed on the same computer for BizTalk Messaging Manager to function.
For example, if you install BizTalk Messaging Manager on a laptop for the purpose of checking your BizTalk Server installation remotely, you do not need Internet Information Services (IIS) installed on the laptop for BizTalk Messaging Manager to function.
When you upgrade to BizTalk Server 2002, the account check Test button verifies only the password on the account. It does not verify administrative privileges. The logged on user must be a member of the BizTalk Server 2000 Administrators group to successfully upgrade to BizTalk Server 2002. If the user is not in the BizTalk Server 2000 Administrators group, the BizTalk Server 2000 installation is no longer valid and the upgrade process will result in errors.
Problem: When adding a remote server of a different BizTalk Messaging Management database to the local BizTalk Messaging Management database, the logged on user is required to:
If these requirements have not been met, the BizTalk Server Administration console and the methods exposed by the Windows Management Instrumentation (WMI) layer will randomly fail with the following error message:
Formatting the error message failed. The following error code was returned: HRESULT = 0x80040e4d
Solution: To correct the problem, either run the Windows XP-specific Managed Object Format (MOF) .exe file (mofcomp.exe) from \Program Files\Microsoft BizTalk Server\Setup\InterchangeProvSchemaXP.mof or reinstall BizTalk Server 2002.
This XLANG Scheduler registry key is required for the XLANG Scheduler Engine to run properly.
The following registry key and value data must be added after you install BizTalk Server:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\1.0\XLANG Scheduler]
"GrpMgrCacheSize"=dword:ffffffff
BizTalk Server 2002 requires Microsoft XML Parser (MSXML) version 3.0 with Service Pack 1 (SP1) or later. This release of BizTalk Server 2002 automatically installs MSXML 3.0 SP1. Using BizTalk Server 2002 with a different version of MSXML is not supported. If you already have MSXML 4.0 installed and a side-by-side installation with MSXML 3.0 is necessary, then you must uninstall MSXML 4.0 before installing BizTalk Server 2002, and then reinstall MSXML 4.0 after BizTalk Server has been installed.
| Back to Top |
BizTalk Server 2002 can be set up on Microsoft Windows XP for development of applications. However, there are known issues with some run-time components of BizTalk Server 2002 on Windows XP. These issues will be addressed in upcoming BizTalk Server Service Packs. For more information about system requirements for BizTalk Server 2002, see "Installing BizTalk Server 2002" in BizTalk Server 2002 Help or in the Installation Guide located in the following directory on the BizTalk Server installation CD: \Program Files\Microsoft BizTalk Server\Documentation.
The keystroke procedures that are documented in BizTalk Server 2002 Help were written for use with Windows 2000. The keystrokes might differ for Windows XP.
Problem: If you install BizTalk Server 2002 on Windows 2000, and then upgrade your operating system to Windows XP, when you try to shut down running XLANG schedules, the shutdown might not work properly. In addition, XLANG schedules that use the Transaction shape or that contain receive actions might not work properly, because the transaction isolation levels in the COM+ applications are set to Serialized by default in Windows XP.
Solution: To correct the problem, make the following changes:
The Component Services console appears.
The XLANG Scheduler Persistence Helper Properties console appears.
The BizTalk Server Interchange Application Properties console appears.
The BizTalk Server Internal Utilities Properties console appears.
Important
The btm2bto Properties console appears.
In Windows XP, if you start several XLANG group managers and then shut down the XLANG Scheduler application from the COM+ Explorer, when you restart XLANG Scheduler and attempt to do a controlled shutdown on all applications, it shuts down only XLANG Scheduler. A controlled shutdown does not work in Windows XP.
Problem: Under Windows XP, the Learn BizTalk tutorial might fail to write output documents to C:\LearnBizTalk\Output.
Solution: To correct this, perform the following operations before running the tutorial:
The Output Properties dialog box appears.
The Select User or Group dialog box appears.
Your user account is added to the list of group or user names.
Now, you need to modify the advanced channel properties for the Channel to Contoso and the Channel to Northwind Invoice channels.
The Channel Property Wizard opens.
The Override Messaging Port Defaults dialog box appears.
The BizTalk Component Properties dialog box appears.
Important
Problem: If BizTalk Server is installed on Windows XP Professional, and you are using a remote SQL Server, you might receive the following error when trying to configure a file data source name (DSN) by using the XLANG tab:
General error: Invalid file dsn 'D:\Program Files\Common Files\ODBC\Data Sources\XLANG Scheduler.dsn'
The error occurs regardless of whether the DSN is valid.
Solution: To resolve this, you need to configure the DSN by using the Microsoft SQL Server DSN Configuration.
The ODBC Data Source Administrator dialog box appears.
The Microsoft SQL Server DSN Configuration Wizard opens.
Problem: If you upgrade from Windows 2000 Professional to Windows XP after installing BizTalk Server 2002, you need to recompile the Managed Object Format (MOF) file. This problem is evident when you configure a BizTalk Server receive function in an environment running Windows XP, and the drop-down list for the Server on which the receive function will run box does not show a list of servers.
Solution: To correct the problem, either run the Windows XP-specific MOF .exe file (mofcomp.exe) from \Program Files\Microsoft BizTalk Server\Setup\InterchangeProvSchemaXP.mof or reinstall BizTalk Server 2002.
| Back to Top |
Problem: The Microsoft Visual Basic project file, BTSAppInt.vbp, cannot be compiled because it lacks a reference to the Microsoft Message Queue object library.
Solution: Add a reference to the library by following these steps:
You can now compile the project.
Problem: The User's Guide does not indicate that you need to install the Microsoft XML Parser (MSXML) version 3.0 Software Development Kit (SDK) to run the sample. The sample requires the files msxml2.h and msxml2.lib to build properly.
Solution: Install the MSXML 3.0 SDK and include the directory path of the MSXML 3.0 library in the project to successfully build the sample.
Problem: Several files, btsaic.idl, btsaic.h, and bts_sdk_guids.h, are not included in the \Program Files\Microsoft BizTalk Server\SDK\Messaging Samples\BTSAppIntegration\VC\ATL folder on the BizTalk Server installation drive, so the sample build fails with the following error message:
midl : command line error MIDL1001 : Cannot open input file btsaic.idl
Error executing midl.exe.
AtlBTSComp.dll - 1 error(s), 0 warning(s)
Solution: Add an additional include path in the Microsoft Visual C++ sample project to \Program Files\Microsoft BizTalk Server\SDK\Include on the BizTalk Server installation drive.
Problem: When you run the SubmitDoc.cmd file that is provided with the BizTalk Framework Correlation sample, it generates an error in the Event Log.
Solution: Before running the SubmitDoc.cmd file, remove the read-only attribute from the NewAppInst.xml file located in the \Program Files\Microsoft BizTalk Server\SDK\XLANG Samples\Integrating BizTalk Services\BTF Correlation\SetupFiles directory.
Problem: The sample directory does not include a built dynamic-link library (DLL), so you must build the Visual Basic project. When the Visual Basic project is built, a new CLSID is generated, so the provided file (VBCustPreProcessor.reg) does not register the custom preprocessor with BizTalk Server. Note that the VBCustPreProcessor.reg file included in the sample directory is not mentioned in the "Custom Preprocessor in Visual Basic" topic in the BizTalk Server 2002 SDK, but it must be run to register the custom preprocessor with BizTalk Server.
Solution: The VBCustPreProcessor.reg file currently reads:
[HKEY_CLASSES_ROOT\CLSID\{BB5416D7-2340-4DCC-8EE6-41B69244A380}\Implemented Categories\{20E8080F-F624-4401-A203-9D99CF18A6D9}]
Update the CLSID value in VBCustPreProcessor.reg, {BB5416D7-2340-4DCC-8EE6-41B69244A380}, with the CLSID of the custom preprocessor that you built. Then, run the updated VBCustPreProcessor.reg. Now, BizTalk Server will be able to recognize the preprocessor. Additional information is available in BizTalk Server 2002 Help, in the topic "Registering Custom Components."
Problem One: A typographical error in step 2 of the User's Guide section indicates an incorrect dynamic-link library (DLL) name.
Solution: Step 2, located in the User's Guide section of the "Custom Preprocessor in Visual C++" topic in the BizTalk Server 2002 SDK, should read:
2. Register CustomPreProcessor.dll by using regsvr32.
Problem Two: The User's Guide does not indicate that you need to install the MSXML 3.0 SDK and update a header file reference to run the sample.
Solution: Install the MSXML 3.0 SDK and include the directory path of the MSXML 3.0 library in the project to successfully build the sample. Also, update the reference to "Msxml.h" in PreProcessor.cpp to "msxml2.h".
Problem: The sample build fails because the required project references are missing.
Solution: Add the following references to the project, and then build the sample:
Problem One: After creating a Visual C++ Microsoft Win32 console application project and adding the source (DistributionList.cpp) and header (DistributionList.h) files from the sample directory, the build fails due to missing header files.
Solution: Add an additional include path in the Visual C++ project to \Program Files\Microsoft BizTalk Server\SDK\Include on the BizTalk Server installation drive.
Problem Two: The sample build fails with compile errors.
Solution: To fix the compile errors, go to line 429 of DistributionList.cpp and modify the following line:
Change:
if (0 == _wcsicmp((LPCTSTR)var.bstrVal, (LPCTSTR)bstrAppName))To:
if (0 == _wcsicmp(var.bstrVal, bstrAppName))Then, go to line 506 and modify the following line:
Change:
if (0 == _wcsicmp((LPCTSTR)var.bstrVal, (LPCTSTR)bstrAliasName))To:
if (0 == _wcsicmp(var.bstrVal, bstrAliasName))At this point, build the project and run the sample.
When you are installing Certificate Services, as outlined in this sample, note that it can be installed only on Windows 2000 Server.
You can click Add/Remove Programs on the Control Panel to install Certificate Services 2.0 in Microsoft Windows 2000 Server. Once the Add/Remove Programs application is running, click Add/Remove Windows Components to install or uninstall Certificate Services. For more information about Certificate Services, go to the MSDN Online Library Web site (msdn.microsoft.com/library/default.asp) and search on "Certificate Services."
Problem One: The E-Procurement sample fails when a SQL Server is not available on the local host.
Problem Two: The E-Procurement sample fails when more than one BizTalk Server is a member of the current BizTalk Server group.
Solution for both: You must update all the SQL Server connection strings that use "localhost" to match the name of the remote SQL Server. These connection strings are located in the Visual Basic project files SuppCorrelation.vbp and Correlation.vbp. After changing these connection strings, you must recompile the projects. Note that this must be changed before registering these dynamic-link libraries (DLLs) on each BizTalk Server in the BizTalk Server group, if applicable.
Problem One: The E-Procurement sample that is included in the BizTalk Server 2002 SDK, and documented in BizTalk Server 2002 Help, includes an unnecessary procedure for fixing the Event Collection Rule group.
Solution: The procedure for fixing the Event Collection Rule group can be ignored.
Problem Two: In the E-Procurement sample documentation, the procedure for creating the MOM Alert Processing Rule, "Create the MOM rule," requires modifications.
Solution: Step 1 in the "Create the MOM rule" procedure should be:
1. In the MOM Administrator Console, expand Rules, expand Processing_Rule_Groups, expand Microsoft BizTalk Server, expand Microsoft BizTalk Server 2002 Enterprise Edition, and then expand Samples.
Problem: The E-Procurement sample document "Create the MOM Rule" contains a procedure titled "Creating the MOM Alert Processing Rule," which refers to property page titles that have been changed.
Solution: Follow the steps of this procedure as indicated, noting that the actual name of the property page might differ from the instructions. The property page titles described in this procedure are now prefixed with "Threshold Processing Rule Properties."
Problem: An automation error is generated when you run the sample.
Solution: Go to the Data page of the XLANG schedule and modify the data type of the Constants message from int to string.
Problem: The note in the "HTML pages" area of the "Personalized Queues" sample topic indicates that a hard-coded file path to the folder C:\winnt\system32 exists in the file RunMe.wsf, and that this path might need to be modified.
Solution: The script has been updated to use the correct folder. You can ignore this note.
Problem: The description of the Refresh Messaging Manager sample does not provide enough information.
Solution: The full description of this sample is provided here:
This sample enables you to refresh BizTalk Messaging Configuration objects in BizTalk Messaging Manager, such as document definitions, envelopes, and channels. It might be helpful to use this sample application to refresh all objects after you have made many changes or additions to the BizTalk Messaging Management database, either by using BizTalk Messaging Manager or by using the BizTalk Messaging Configuration object model. Without this sample application, you would need to manually refresh each object type by clicking the Search Now button for each of the object types in BizTalk Messaging Manager.
Problem: An error might occur when running a script that creates a BizTalk Server receive function, depending on the configuration of your computer.
Solution: If an error occurs while running a script that creates a receive function, edit the script file and search for the name of the processing server used for the receive function. The code might look similar to the following:
object.ProcessingServer = "localhost"The string "localhost" must be replaced with the actual name of the computer. After this change is made, save the script and run it again. Note that you must delete the BizTalk Messaging objects previously created by the script before running it again.
Problem: The XLANG schedule, RemoteQueue.skx, generates an error.
Solution: Use the following steps to recompile and run the XLANG schedule:
The XLANG Correlation directory, located on the root of the BizTalk Server installation CD, includes an XLANG Correlation sample, demonstrating the improved correlation technique in BizTalk Server 2002. For more information, see the readme.txt file in the XLANG Correlation directory.
Problem: In the XLANG Interfaces sample, the option "sked hosts OtherMachine" is supposed to list the host applications on the remote computer, OtherMachine. This option does not work because there is a missing Connect statement between lines 158 and 160 in the Sked.vbs file located at \Program Files\Microsoft BizTalk Server\SDK\XLANG Samples\PublicInterfaces.
Solution: To correct the problem, add the following statement to Sked.vbs between lines 158 and 160:
if args.Count>1 then
Catalog.Connect(args(1)) 'Connect to remote machine.
end ifProblem: While working with the BizTalk Server 2002 tutorials and samples, you might encounter various errors when BizTalk Server attempts to post data to an HTTP location. The tutorials and samples were written to function with anonymous access where security would not be a problem. In an environment where the Web servers have been secured, the tutorials and samples might not function properly. These errors are most likely related to security constraints with Internet Information Services (IIS). The security constraints should NOT be removed to make the BizTalk Server 2002 tutorials and samples function properly.
Solution: To allow the tutorials and samples that use IIS to function properly in a secured environment, the following steps should be taken:
IIS security is such that users must be granted permission to the folders where the Web pages reside and to the locations where the Web pages will be writing data. In these cases, the user account must be granted file permission to the tutorial and sample folders.
IIS directory security is, by default, configured to allow anonymous access first. If anonymous access works when attempting to access the Web page, IIS will not authenticate the user. For the purposes of executing the code in the Web pages, the user created in step 1 must be authenticated. Turning off anonymous access for the virtual directory created in the tutorial or sample will force the user to be authenticated and allow the Web pages in the tutorial or sample to execute correctly.
In most cases, when the BizTalk Server 2002 tutorials or samples post data to an HTTP location, the posting is done using a BizTalk Server messaging port. The BizTalk Server messaging port allows the user to specify the HTTP location, but not the credentials needed to access the HTTP location. That information is specified in the advanced properties of the channel.
The following steps are needed to modify the advanced properties of the channel:
The Advanced Properties dialog box appears.
For more specific details about the BizTalk Server tutorials and samples, see BizTalk Server 2002 Help.
Important
Problem: To successfully complete the BizTalk Server 2002 Tutorial, you must install BizTalk Server 2002 and all its dependencies. If you do not have Microsoft Visio 2002 installed, you will not be able to run ExecuteTutorial.exe without errors. ExecuteTutorial.exe is dependent on fm20.dll, which is installed with Visio 2002.
Solution: Start BizTalk Document Tracking before you run the tutorial. For more information, see "Open BizTalk Document Tracking for the first time" in BizTalk Server 2002 Help.
| Back to Top |
Problem: When an organization name consists of numbers only, the BizTalk Document Tracking Web application will produce a run-time error as soon as it starts. After dismissing the error, most elements on the user interface (UI) will be disabled, causing the Web application to become unusable.
Solution: Do not use only numbers for organization names.
Problem: When adding a remote BizTalk Server to a group, you might be prompted with a dialog box indicating that this server belongs to another BizTalk Messaging Management (InterchangeBTM) database, and asking if it is okay to continue. If you click Yes, you will receive the following error message:
A new instance of the WMI class "MicrosoftBizTalkServer_MgmtDB" cannot be created in the BizTalk Server WMI provider: BizTalk Server failed to access the "InterchangeBTM" database on the '<server name>' server with the database connection information.
Solution: Log on to the server that needs to be added to the group, and add the server from there, rather than remotely. This procedure requires the user to be a member of the BizTalk Server Administrators group.
When you use Microsoft Application Center 2000 to deploy applications that contain BizTalk Server resources, both the source and the target cluster must use the same BizTalk Server repository. If there is a proxy server between the source and target clusters, then access to the BizTalk Server repository is through a proxy server for either the source or the target cluster. This also applies to using BizTalk Messaging Manager when the BizTalk Server repository is behind a proxy server.
Problem: If the proxy settings are not configured using Proxycfg.exe, you will receive error messages when interacting with the BizTalk Server repository.
Solution: Both Application Center and BizTalk Messaging Manager rely on ServerXMLHTTP to access the BizTalk Server repository. ServerXMLHTTP requires the proxy settings be configured using Proxycfg.exe, rather than Microsoft Internet Explorer proxy configurations. For more information about using Proxycfg.exe, go to the Microsoft Product Support Services Web site (support.microsoft.com/directory/) and search the Knowledge Base for the article "Proxy Configuration Utility Must Be Run for ServerXMLHTTP to work" (article number Q289481).
Problem: To submit a document from a remote client, you must install the application proxy using the export from a COM+ application. When uninstalling the application proxy on a remote computer, the following error message appears:
Error registering COM+ application. Contact your system personnel or administrator.
Solution: Before uninstalling the application proxy, complete the following steps:
The Component Services console appears.
The BizTalk Server Interchange Application Properties console appears.
When scale out is required, create a virtual Application Center server (Application Center cluster, not Windows Clustering) and add this virtual server to the BizTalk Server group. Each individual server in the Application Center cluster will have a virtual directory pointing to BizTalkHTTPReceive.dll. This configuration enables you to create only one receive function for the virtual server for a particular virtual directory. Without a virtual server on an Application Center cluster, you would need to create a receive function for each server/virtual directory combination.
To scale up Message Queuing (also known as MSMQ), use transactional queues (local queues on BizTalk Server, rather than remote queues, must be used for transactional queues to receive) and a fast disk I/O channel. Private queues do not need to query Microsoft Active Directory; however, a public message queue must query Active Directory. Therefore, reading data from and writing data to local message queues results in better performance. Non-transactional local queues can be used to achieve better performance. However, non-transactional local queues do not provide the same reliability offered by transactional queues.
Problem: When you save a large XML schema to the WebDAV repository by using BizTalk Editor or BizTalk Mapper, BizTalk Editor or BizTalk Mapper might appear to hang or time out if Internet Explorer 6.0 is installed on your WebDAV computer.
Solution: If this occurs, use the file system to save the XML schema to the WebDAV repository.
Problem: SQL Server can generate "Unspecified Error" and "Timeout" error messages when the following conditions apply:
These errors cause running schedules to fail when attempting to persist to the database.
Solution: To resolve this problem and increase the transaction timeout, the timeout values for Microsoft ActiveX Data Objects (ADO) connections and commands should be increased. Executing the following code in a .reg file adds the appropriate registry keys to the registry and also sets the timeout values to 300 seconds, overriding the 60-second default:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\1.0\XLANG Scheduler]
"ADOConnectionTimeout"=dword:0000012c
"ADOCommandTimeout"=dword:0000012cThe following entries are typically seen in the Event Log when these "Unspecified Error" and "Timeout" error messages occur:
event log:
Error1
The state of the XLANG schedule instance could not be saved to the database. Detailed information is provided in the following message.
Module name: mymodule
Module ID: {EE8FB9FA-AB64-492A-A127-56A1EFDB2C50}
Instance ID: {6B48FF17-791B-474F-8EE2-AD35FF8E5A30}
Database error(s):
Error Code = 0x8004e007 : You made a method call on a COM+ component that has a transaction that has already committed or aborted.
XLANG Scheduler Engine Internals Information:
File: d:\bts\private\sked\src\runtime\persistence\persist.cpp
Line: 261
Error 2:
An error was encountered while attempting to persist an XLANG schedule instance. Detailed information is provided in the following message.
Error source: Field
name: __Correlation__
HRESULT: 0x80040e14
Module name: mymodule
Module ID: {EE8FB9FA-AB64-492A-A127-56A1EFDB2C65}
Instance ID: {6FE02E74-7FE2-401B-93F3-EC208636257B}
Error Code = 0x80040e14 :There are known issues with BizTalk Server and SQL Server Shared Memory network libraries. When you run BizTalk Server 2002 in a production environment where BizTalk Server is on the same computer as the SQL Server it is connecting to, it is recommended that you disable the Shared Memory protocol in the SQL Client Network Utility.
If you intend to use Secure Sockets Layer (SSL) to connect your BizTalk Server installation to a remote SQL Server installation, you must perform the following steps to ensure you do not encounter a memory leak during operation:
Problem: If you install BizTalk Server 2002 on a computer that has an existing installation of Microsoft Commerce Server 2000, the Analysis module user interface in Commerce Server might not function properly.
Solution: To resolve the problem, re-register the msolap80.dll file, which is located in the Program Files\Common Files\System\Ole DB directory.
Problem: When you are compiling an XLANG schedule, and Microsoft Visual Studio .NET is installed on your computer, BizTalk Orchestration Designer might display the Just-In-Time (JIT) Debugging dialog box stating that an exception 'Runtime Error' has occurred in the script. You are asked if you want to debug using the selected debugger option. If you choose No in the JIT debugger options, the schedule should compile.
The run-time errors occur if the expression in the Decision shape is referring to message instances. To correct this, disable JIT debugging for scripts. With Visual Studio .NET, JIT debugging is enabled by default.
Solution: Follow these steps to disable the JIT debugging for the script:
The Options dialog box appears.
Problem: Due to directory service replication latency, a newly created queue cannot be used before replication is done. If the schedule tries to send a message or run a schedule using a newly created public queue, such as the public instance queue, the schedule might fail with the following error in XLANGMON:
MQ_ERROR_QUEUE_NOT_FOUND 0xC00E0003L
Solution: To resolve the problem, wait for replication to complete. In some instances, this can take up to 10 minutes.
BizTalk Messaging cannot generate X12 output correctly if the field delimiter specified in the messaging port is either a carriage return (CR / 0x0a) or a line feed (LF / 0x0d). This will be fixed in an upcoming service pack.
BizTalk Server 2002 improves correlation to a running XLANG instance by using a single static message queue for all XLANG schedule instances. Note that there are two methods of correlation:
Now, the XML message will be placed in the message queue with the GUID as the message label and will correlate with the XLANG schedule.
| Back to Top |
Problem: BIZTALK_CONFIGDATA_TYPE should be documented with a value of 3 instead of 2. The definition for BIZTALK_CONFIGDATA_TYPE reads:
[2] Configures the encoding type on the messaging port.
Solution: The definition for BIZTALK_CONFIGDATA_TYPE should read:
[3] Configures the encoding type on the messaging port.
In BizTalk Server 2002 Help, in the "BizTalk Server 2002 Administration" section, there is a procedure about how to configure disk caching. This procedure, "Configure disk caching," is not necessary in BizTalk Server 2002.
In the "Understanding Interchange Record Results" topic, the description in the table should refer to an interchange instead of a document. The first sentence in the Description column of the Error row should read:
Specifies whether there are any errors associated with the interchange. Possible error messages are:
In the "Understanding Document-Instance Record Results" topic, the description in the table should refer to a document instead of an interchange. The first sentence in the Description column of the Error row should read:
Specifies whether there are any errors associated with the document. Possible error messages are:
In BizTalk Server 2002 Help, under the topic "Supporting the Tracking Database with Parser and Serializer Components," the second description in the Outbound document table contains an incorrect reference to H7. This description should refer to HL7, as follows:
This is the code for document syntax, such as XML, X12, EDIFACT, HL7, and so on.
| Back to Top |
The functoids provided in BizTalk Mapper are written in Microsoft Visual Basic Scripting Edition (VBScript). Therefore, when you are manipulating data types like numbers, date/time, and currency, the data will be formatted based on the locale settings of your operating system. However, the data should keep the data type formats defined in XML. For example, if the locale is set to German or French, the decimal separator will be changed from a period (.) (used in XML) to a comma (,). If you are processing locale-dependent data types, you need to write custom scripts using the Scripting functoid to handle the locale conversion appropriately. For more information, refer to the Microsoft Knowledge Base Web site (support.microsoft.com/).
The international issues outlined in BizTalk Server 2002 Help, under the topic "About Microsoft Operations Manager," will be addressed in MOM Service Pack 1.
In BizTalk Orchestration Designer, message names and field names defined in the XML Communication Wizard and the Method Communication Wizard can contain only ASCII characters if the names are used in rules. The Microsoft Visual Basic Scripting Edition (VBScript) engine that processes the rules will fail to process non-ASCII characters.
Problem: XLANG schedule drawings that use non-ASCII characters in the name of ports, messages, and/or fields might not export correctly in a different system locale setting from the one in which the XLANG schedule drawing was created.
Solution: Install the locale in which the XLANG drawing was created as the system default, and then make the .skx file from the XLANG schedule drawing.
| Back to Top |
The WebServices directory, located on the root of the BizTalk Server installation CD, includes the BizTalk Web Service samples as well as the SOAP Toolkit and SOAP Toolkit samples. These samples include the following:
Notes
| Back to Top |