Microsoft KB Archive/284196

= INFO: BizTalk Server 2000 Readme.htm Part 3 of 3 =

Article ID: 284196

Article Last Modified on 10/17/2003

-

APPLIES TO


 * Microsoft BizTalk Server 2000 Standard Edition

-



This article was previously published under Q284196



SUMMARY
This article contains information from the BizTalk Server 2000 Readme.htm



MORE INFORMATION
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.

Connecting to Microsoft SQL Server fails on a computer that does not have SQL Server installed
Problem: Installing BizTalk Server on a computer without Microsoft SQL Server installed and trying to setup a BizTalk Server database on a remote SQL Server machine that is running a different default language version of SQL Server might result in an error. The message &quot;Cannot open database requested in login, Database Name. Login fails&quot; might appear while running the BizTalk Server Database wizard.

Solution: To prevent this problem, create a sample user DSN before installing BizTalk Server.

 On the Start menu, point to Settings and click Control Panel. Double-click Administrative Tools. Double-click Data Sources (ODBC).

The ODBC Data Source Administrator console appears.

 Select the User DSN tab. Click Add.

The Create New Data Source dialog box opens.

 Select SQL Server in the Name list and click Finish. Complete the Create a New Data Source to SQL Server wizard and create a sample user DSN.</li></ol>

Incorrect behavior in BizTalk Editor when using Korean IME
Problem: If you are using the IME to enter Korean characters for record or field names in BizTalk Editor, BizTalk Editor enables duplicate names even though the correct error message box appears when you try to rename a record or field to an existing name. BizTalk Editor also enables entering invalid record or field names when using the Korean IME that would otherwise not be allowed.

Solution: Delete the invalid record or field before continuing.

Math functoids do not work when using a comma to express a decimal number
Problem: Many locales use a comma as the decimal symbol. A number that uses a comma as the decimal symbol will fail validation using Microsoft XML (MSXML) Parser because MSXML expects a period ( . ) to be used as the decimal symbol.

Solution: Change the decimal symbol from a comma to a period in the system local settings.

<ol> On the Start menu, point to Settings and click Control Panel.</li> Double-click Regional Options.

The Regional Options console appears.

</li> Click the Numbers tab.</li> In the Decimal symbol list box, type: .. </li> Click Apply and click OK.</li></ol>

Connecting to databases created by a different language version of BizTalk Server
Issue: BizTalk Server cannot connect to databases created by a different language version of BizTalk Server 2000.

XML elements and/or attributes of Number data type might not be tracked correctly in some foreign locales
Problem: Depending on the system locale, a numeric value in XML data might be misinterpreted by BizTalk Server when logged as an integer tracking field in the Tracking database. For example, in a German locale an XML Number value of 4.0 is logged as 40 in the Tracking database because the decimal point (.) is misinterpreted as the digit grouping symbol.

Solution: There are two workarounds for this problem. First, if you know in advance that the element/attribute value stores a decimal number, you can change the XML element/attribute data type to Real (r4) or Double Real (r8). Second, you can configure the document definition or channel to log an element/attribute with a Number data type as Real instead of Integer.

Unable to export XLANG schedule drawing correctly
Problem: XLANG schedule drawings that use non-ASCII characters in the name of ports, messages, and/or fields may 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.

Using the keyboard to convert Korean characters to Chinese characters causes BizTalk Editor to fail
Problem: Converting Korean characters to Chinese characters by using the CHINESE key on a Korean keyboard causes BizTalk Editor to fail.

Solution: You can enter Chinese character directly (for example, copying a Chinese character from Notepad) into BizTalk Editor.

Using non-ASCII data in the BizTalk Server 2000 Tutorial
Problem: The BizTalk Server 2000 Tutorial does not work with non-ASCII data.

Solution: Change the code for the scripting component (PORequestApproval.wsc) to use the XML DOM for to write data.

BizTalk Servers in a group of servers must operate in the same language
Issue: BizTalk Servers that operate in different languages cannot belong to one server group. BizTalk Server groups are language-specific.

Message names and field names with non-ASCII characters will not work in script expressions
Issue: 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 VBScript Engine that processes the rules will fail to process non-ASCII characters.

Working with long date and time formats
Problem: Using long date and time formats might introduce truncations in BizTalk Document Tracking because the date and time selection control only supports short formats.

Solution: If you encounter any problem with date and time format, you can change the formats used by your computer in the Control Panel by clicking Regional Options.

Instance validation fails when using a comma to express a decimal number
Problem: If a comma is used instead of a period ( . ) when expressing a decimal number in a document instance, instance validation might fail. This happens because the parser converts the document instance into an XML document and then uses the XML Document Object Model (DOM) to validate the XML document against the document specification. The XML DOM does not allow a comma to be used as a decimal point. For more information, go to the MSDN Online Library (msdn.microsoft.com/library/default.asp) and search for XML Data Types Reference.

Solution: Use a period when expressing decimal numbers in a document instance.

Unicode limitation of the ActiveX controls used in BizTalk Document Tracking
Issue: The date and time selection control, the list view, and the tree view cannot display Unicode characters. Therefore, mixed language support is limited. For example, if an English computer accesses a BizTalk Server with BizTalk Document Tracking Web pages and data that include a Double Byte Character Set (DBCS), the characters are displayed as question marks (?) in the English client.

Channel names with non-ASCII characters will not work in URL query strings
Issue: In BizTalk Orchestration Designer, if non-ASCII characters are included in the channel names defined in the BizTalk Messaging Binding Wizard for non-activation receive, submitting documents with HTTP may not succeed. The channel names are being passed in the query string part of the URLs and non-ASCII characters are not supported in the query strings.

Unicode WebDAV limitations
Problem: Files can only be saved in Unicode encodings in the WebDAV repository. However, the WebDAV repository cannot store files with names in different codepages and WebDAV does not support Unicode characters in file names.

Solution: Make sure that your system locale is set to your language. For example, international users who install this release of BizTalk Server 2000 on an English Windows 2000 computer and want to name files with characters that are not supported in the Latin I code page (Windows 1252), must change the system locale to their user locale.

Yen symbol or Won symbol appears as backslash in Output pane after instance validation
Problem: If you create a document instance containing a Japanese Yen symbol or Korean Won symbol while your system locale is set to Japanese or Korean, when that document instance is successfully validated against the corresponding specification, the Yen symbol or Won symbol appears as a backslash in the Output pane of BizTalk Editor.

Solution: To view the Yen symbol or Won symbol rather than a backslash, you can view the source of the Output pane.


 * 1) In the Output pane that displays a backslash rather than the Yen symbol or Won symbol, right-click anywhere within the pane, and then click View Source.
 * 2) In the Notepad instance, on the Format menu, click Font.
 * 3) In the Font dialog box, in the Font area, click Tahoma, and then click OK.

The monetary symbols should appear as expected.

No scripts available to manage the persistence database used by BizTalk Orchestration Services
Issue: There are no scripts available to manage old XLANG schedule instances along with other utilities to manage the persistence database used by BizTalk Orchestration Services.

Microsoft SQL Server set to use Binary Sort Order
Issue: If SQL Server is set to use Binary Sort Order, then case sensitivity is respected in channel names, EDI property sets, and so on.

Failed to connect to a second Named instance of Microsoft SQL Server
Problem: During BizTalk Server 2000 setup, there is a failure to connect to a second Named instance of SQL Server. BizTalk Messaging Management database administrative objects do not work with NamedPipes for a second instance of SQL Server, therefore TCP/IP is required.

Solution: Run SQL Server setup and select &quot;Connectivity Only.&quot; After SQL Server components are installed, complete the following steps.
 * 1) On the Start menu, point to Programs, point to Microsoft SQL Server, and select Client Network Utility. The SQL Server Client Network Utility console appears.
 * 2) Choose TCP/IP as the first enabled protocol in the Enabled protocols by order: area.
 * 3) Click OK.

BizTalk Server 2000 Beta upgrade
Problem: It is not possible to upgrade an existing installation of BizTalk Server 2000 Beta to an installation of the released version.

Solution: Before you can install the BizTalk Server 2000 released version, you must remove the BizTalk Server 2000 Beta and remove the Microsoft SQL Server databases that were created during the installation of the Beta. To remove existing databases:
 * 1) On the Start menu, point to Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
 * 2) Expand Microsoft SQL Servers, expand SQL Server Group, and then expand the server that contains the databases that you want to delete.
 * 3) Expand the Databases folder.
 * 4) Right-click each of the databases that were created during the installation of BizTalk Server 2000 Beta, and then click Delete.

Local file transport appends to existing file
Issue: For the File transport type, the default transport-component setting is to append new files to an existing file in the specified directory. In the case of reliable messaging, if an acknowledgment is not received the document is resent, based on the number of retries. The repeated document is appended to the existing document.

EDI interchanges containing multiple groups cause BizTalk Server to stop responding
Problem: For EDI, both X12 and EDIFACT, submitting interchanges to BizTalk Server that contain more than a single functional group will cause the server to stop responding, if &quot;generate receipt&quot; is checked for the affected channels in the BizTalk Messaging configuration.

Solution: Submit single group interchanges.

Cancellation of the setup wizard displays an erroneous error message
Problem: Cancellation of setup during the database creation stage of the database creation wizard will cause a setup error.

Solution: Click OK to close the error message box. The cancellation process will proceed as expected.

SAP DCOM compatibility requirements
Issue: To use the SAP application integration component (AIC) shipped with the released version of BizTalk Server 2000, you must have version 4.6B of the SAP BAPI DCOM connector on your system.

WebDAV does not work after installing pre-release versions of Microsoft Office 10
Issue: Using pre-release versions of Microsoft Office on the same computer as BizTalk Server 2000 is not recommended.

Uninstalling the application proxy for the BizTalk Server Interchange Application on a remote client displays an error
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 error message &quot;Error registering COM+ application. Contact your system personal or administrator&quot; appears.

Solution: Before uninstalling the application proxy, complete the following steps:
 * 1) On the Start menu, point to Settings, click Control Panel, double-click Administrative Tools, and double-click Component Services.

The Component Services console opens.
 * 1) Expand Component Services, expand Computers, expand My Computer, expand COM+ Applications, right-click BizTalk Server Interchange Application, and click Properties.

The BizTalk Server Interchange Application Properties console opens.
 * 1) Click the Advanced tab.
 * 2) In the Permission area, clear the Disable deletion and Disable changes check boxes.
 * 3) Click OK.

Server clustering and BizTalk Server 2000
Issue: For information about server clustering and BizTalk Server 2000, go to the Microsoft BizTalk Server Web site (http://www.microsoft.com/biztalk/default.asp) and search for &quot;clustering&quot;.

Update to Setting Up HTTP Sample.doc for Using the HTTP Transport Sample
Problem: The XLANG HTTP transport sample readme file, Setting Up HTTP Sample.doc, should specify how to enable anonymous access for the resource.

Solution: In the section &quot;Creating the Purchaser Web Site&quot; in Setting Up HTTP Sample.doc, the following needs to be done after the BizTalkSample virtual directory is created: view the properties of the newly created virtual directory, click the Directory Security tab, and enable anonymous access for the virtual directory.

Unsupported SAP AIC sample
Issue: AIComp.dll is an unsupported sample that provides a guideline for BizTalk Server Integration with SAP by means of AICs (application integration components). AIComp.dll is a sample SAP AIC that implements the IPipelineComponent and IPipelineComponentAdmin interfaces. AIComp.dll wraps the SAP DCOM Connector, which provides input access to SAP by allowing the delivery of SAP iDoc messages. IDOC.dll is the DLL that is created from the SAP DCOM connector. iDoc.dll and AIComp.dll are build compatible; therefore, AIComp.dll must be recompiled with every new build/version of IDoc.dll.

Permission denied errors occur when accessing the BizTalk Server Administration Microsoft Management Console (MMC), BizTalk Messaging Manager, or the BizTalk Messaging Configuration object model
Problem: BizTalk Server 2000 Setup adds the local group BUILTIN\Administrators to the BizTalk Server Administrators group. However, a user that belongs to the Administrators group but does not belong explicitly to the BizTalk Server Administrators group will encounter permission denied errors when accessing the BizTalk Server Administration MMC, BizTalk Messaging Manager, or the BizTalk Messaging Configuration object model.

Solution: Use the Computer Management console to add individual users explicitly to the BizTalk Server Administrators group.

Upgrading from the Evaluation or Standard Edition to the Enterprise Edition of BizTalk Server
Issue: To upgrade to the Enterprise Edition of BizTalk Server, complete the following steps:
 * 1) Uninstall the Evaluation or Standard Edition of BizTalk Server. Note that any receive functions that are configured will be lost; in addition, any configuration changes made to the BizTalk Server COM+ packages will be lost during the uninstallation. Do not delete the BizTalk Server Configuration, Shared Queue, and Tracking SQL Server databases.
 * 2) Install the Enterprise Edition of BizTalk Server. During BizTalk Server setup, select the previously created BizTalk Server Configuration, Shared Queue and Tracking SQL Server databases.
 * 3) Recreate the receive functions and make any changes to the BizTalk Server COM+ packages, if required.

Installing or uninstalling BizTalk Server fails to add or remove BizTalk Server COM+ applications
Problem: When the Microsoft Distributed Transaction Coordinator (MSDTC) is stopped, installing or uninstalling BizTalk Server fails to add or remove BizTalk Server COM+ applications.

Solution: Ensure that the MSDTC service is running before installing or uninstalling BizTalk Server COM+ applications.

BizTalk Server parsers do not recognize Julian dates
Problem: BizTalk Server's parsers do not recognize the Julian date format in an incoming document instance. A Julian date format includes three digits that indicate the day (DDD). Although it is possible to create specifications in BizTalk Editor that use the Julian date format, this capability is provided for use only with custom parsers that can recognize document instances using the Julian date format.

Solution: Do not use the Julian date format in a specification or a document instance unless you are employing a custom parser that recognizes the Julian date format.

''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 © 1999–2000 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.''

<div class="references_section">