| 27012 | You may receive an out-of-memory error message, Event ID 7031 or Event ID 5410 messages, or Event ID 4786 error messages, or you may experience similar symptoms in BizTalk Server |
| 27013 | Event ID: 324 when you use the HTTPS transport to send multiple messages in BizTalk Server 2002: An error was encountered while parsing the response from the HTTP server |
| 27014 | Error message when you use the LoadByName method in a custom application to update the certificates for lots of channels in BizTalk Server 2002 with Service Pack 1: Ran out of memory |
| 27015 | When you use some BizTalk Mapper numeric functoids to calculate noninteger values, your results may not be correct or they may not be as precise as expected. For example, if you multiply 20815.2000 by 1.00 , you may receive 208152000 for the... |
| 27016 | Documents that are being sent from BizTalk Messaging to BizTalk Orchestration can become stranded in the private MSMQ queue that temporarily houses these documents in the event of a catastrophic failure such as a power outage. When these documents... |
| 27017 | The XML output of the map translation may contain additional control characters that enclose the constant value in BizTalk Server 2002 or in BizTalk Server 2000 |
| 27018 | You receive a The server encountered a transport error while processing the messaging port error message when you try to send a document by using the HTTP transport in BizTalk Server 2000 and in BizTalk Server 2002 |
| 27019 | Describes a problem that occurs when a call to the Channel.Save method or to the Document.Save method does not save the MapReference property or the Reference property. Describes a resolution to the problem. |
| 27020 | After you install BizTalk Server 2002 Service Pack 1 (SP1), BizTalk Messaging Service does not start and you receive error messages similar to the following in the application log: Event Type: Error Event Source: BizTalk Server Event Category:... |
| 27021 | Describes a problem that occurs if you configure the BizTalk Server SendLocalFile transport component to use a specific user name and password. Paged pool memory usage continuously increases on the server. |
| 27022 | Describes a problem that occurs when BizTalk Server consumes additional memory resources and handles every time that an orchestration instance is rehydrated. The resources are not reclaimed until the dehydrated orchestration instance is completed. |
| 27023 | Fixes a problem in BizTalk Server 2002 SP1 that occurs when the interchanges in the Retry queue are not processed from 00:00 to 1:00. |
| 27024 | Fixes a problem where BizTalk Server 2002 997 functional acknowledgement transaction receipts have control numbers in a different order than the order that the control numbers in the original document. |
| 27025 | Fixes a problem that occurs when you receive a binary document by using Message Queuing. The document is not processed and an Event ID: 324 message is logged in the Application log in BizTalk Server 2002. |
| 27026 | Fixes a problem that occurs when the BizTalk Server 2002 Parser for RosettaNet incorrectly treats a document as ANSI instead of Unicode. |
| 27027 | Fixes a problem that may occur if a BizTalk Server 2002-based server is configured with more than 64 file receive functions, more than 64 Message Queuing receive functions, or both. |
| 27028 | Explains how the Rnmsgtoackall.xml map incorrectly maps the GlobalBusinessIdentifier elements for 3C3 PIP Document type definitions (DTDs) and for 3C4 PIP DTDs. This article also explains how to obtain the hotfix for this problem. |
| 27029 | Explains how to use input methods and Get methods to create pages to help configure a BizTalk Server pipeline Application Integration Component (AIC). |
| 27030 | Describes how to use SQL Adapter to disassemble a result set in Microsoft BizTalk Server 2002. |
| 27031 | Describes a problem that occurs when BizTalk Server 2002 stops processing documents after a [DBNETLIB][ConnectionWrite(send()).] error occurs. |
| 27032 | Describes a problem that occurs when you modify the Authorization information field in a BizTalk Server 2002 channel. |
| 27033 | Describes a problem that occurs when the BizTalk Messaging Service randomly stops responding, and you receive error messages. Includes a hotfix to resolve the problem. |
| 27034 | Describes a problem that may occur in the BizTalk 2002 Adapter for FTP when heap corruption occurs in non-pass-through scenarios. |
| 27035 | Describes a fix for a problem that occurs when you use a .NET class in the Business Rule Composer. You receive an error message. |
| 27036 | Describes a fix for a problem that occurs when you try to receive an IDOC by using the BizTalk Adapter 2.0 for mySAP Business Suite in BizTalk Server 2004. The receipt is not successful. |
| 27037 | Describes a fix for a problem that occurs when you use the BizTalk Adapter for mySAP Business Suite. DBSC characters in an IDOC that is sent to a SAP system become corrupted. |
| 27038 | Describes an error message that you may receive when you use the BizTalk Server 2004 Configuration Wizard. |
| 27039 | Service packs are the means by which Microsoft distributes bug fixes. Service packs keep a product current. Service packs include updates and may include system administration tools, drivers, and additional components, which are conveniently bundled... |
| 27040 | Describes a suspended message event log entry that you receive after you have configured a send port to use the HTTP adapter for BizTalk Server 2004. |
| 27041 | Describes data duplication or loss that may occur if use the BizTalk Server 2004 FTP adapter. Discusses the configuration changes that we recommend that you make to avoid this behavior. |
| 27042 | Fixes a problem where the BizTalk Server 2004 HTTP Adapter pre-appends the byte order mark (BOM) to output messages that are encoded with a Unicode character set. |
| 27043 | Discusses an issue in BizTalk Server 2004 where a promoted property that has a default value set does not show up as a context property when the document is received. |
| 27044 | Explains that you may not be able to add more than one inbound connection to a script functoid in BizTalk Mapper. |
| 27045 | Describes an error message that you may receive during the host creation step of the Microsoft BizTalk Server 2004 Configuration Wizard. |
| 27046 | Discusses an error that can occur if you have created a receive location that uses the File transport type to monitor a local directory and if multiple BizTalk Servers are members of the receive handler host instance for this receive location. |
| 27047 | Fixes a problem in the BizTalk Server Accelerator for HIPAA 2.0 where an interchange with multiple transaction sets is partially accepted and the subdocuments are suspended. |
| 27048 | Explains the limitations of using .NET custom parsers with the COM+ based architecture of BizTalk Server 2002. |
| 27049 | Fixes an error message that you may receive when you set the value of both the ElementFormDefault property and the AttributeFormsDefault property to Qualified in BizTalk Server 2004. |
| 27050 | Describes steps that are missing from the Enterprise Application Integration tutorial in the BizTalk Server 2004 Documentation. |
| 27051 | Explains how to resolve an issue that may occur if the database instance name is not specified during installation or if the database instance name has been modified or changed manually after installation. |
| 27052 | Describes a problem where you cannot successfully enlist a dynamic send port in BizTalk Server 2004 after you register the BizTalk Server Message Queuing Adapter (MSMQT). |
| 27053 | Describes an error message that you receive in the BizTalk Server 2004 Explorer when you create a send port that uses the Electronic Data Interchange (EDI) Transport type. |
| 27054 | Lists the variant type (VT) attributes and corresponding VT values in a BizTalk Server 2004 binding file. |
| 27055 | Describes a workaround for a configuration failure of Microsoft BizTalk Server 2004 on a Microsoft Windows XP-based computer. |
| 27056 | Fixes a problem where you receive an error message in Document Tracking and Administration (DTA) when you run DTA reports through the user interface of BizTalk Server 2002. |
| 27057 | Describes an SSO Server failed. The RPC server is unavailable Enterprise Single Sign-On Service (SSO) error message that you receive in BizTalk Server 2004 when you try to modify the receive location or the send port. |
| 27058 | Fixes a problem that occurs where you receive an Internal Error error message and the SnlReceiver application does not work when you process a SWIFTNet message by using the BizTalk Accelerator for Financial Services. |
| 27059 | Explains why the BizTalk Explorer for BizTalk Server 2004 may not be available in Visual Studio. |
| 27060 | This article discusses how to change timeout value for a query in BizTalk Health and Activity Tracking |
| 27061 | Describes an error message that you receive when you try to examine any Send or Receive Ports in BizTalk Server 2004. This problem occurs when the BizTalk Server Administration Console connects to the wrong Enterprise Single Sign-On (SSO) server. |
| 27062 | Fixes a problem where error message details are not entered in the event log when pipeline failures for a Receive Location occur in BizTalk Server 2004. |
| 27063 | Describe a problem that occurs when you parse a complex flat file in BizTalk Server 2004 with the parser_optimization property set to the default value of speed. |
| 27064 | Fixes a problem where context properties of messages are not saved in the Message Box database and are lost in BizTalk Server 2004. |
| 27065 | Discusses a problem where creating a map that accepts multiple input message schemas that belong to the same namespace does not work in BizTalk Server 2004. |
| 27066 | Describes a 0x8007000e error message that you may receive when you use Microsoft BizTalk Server 2002. |
| 27067 | Describes an error message that you receive when you try to install BizTalk Server 2004 on a computer that is running SQL Server 2000 (64 bit). To resolve this problem, upgrade the MDAC. |
| 27068 | Discuses the Cannot Resolve Schema Location Attribute. An error occurred at (3,4) error message that you may receive when schemas are Imported or Included across different projects in BizTalk Server 2004. |
| 27069 | This article discusses how to remove a non-functional computer from a BizTalk Server 2004 group. |
| 27070 | Describes an error message that you may receive when you configure the Business Activity Messaging and SharePoint Portal Server site in the BizTalk Server 2004 Configuration Wizard. |
| 27071 | Fixes a problem where an exception handler captures one exception two times when an exception occurs in a BizTalk Server 2004 orchestration. |
| 27072 | Discusses the Unexpected end of stream error message that you receive when you parse a message by using a migrated schema in BizTalk Server 2004. |
| 27073 | Discusses a problem that occurs when you use the BizTalk Server 2004 SEED deployment tool if the package name has GB18030 Ext A. characters. |
| 27074 | Fixes a problem in BizTalk Server 2004 where some incorrect data is generated in the output instance when you test a map by using sample XML data as input in Visual Studio .NET. |
| 27075 | Explains how to cluster the Enterprise Single Sign-On (SSO) master secret server for use with a BizTalk Server 2004 group. |
| 27076 | Describes a problem that can occur when the TrackedMessages_Copy_BizTalkMsgBoxDb SQL Server Agent job runs in BizTalk Server 2004. Explains how to fix the problem. |
| 27077 | Describes the loss of claims that you may notice when you process a transaction with the BizTalk Server Accelerator for HIPAA 2.0. The article discusses where the claims are located. |
| 27078 | Discusses a problem where you cannot save messages that are larger than 18 MB from the Orchestration Debugger in BizTalk Server 2004. |
| 27079 | Discusses a problem where more than one OutResendT message may exist in the BizTalk Server 2004 Health and Activity Tracking (HAT) tool for each instance of the Message Queuing Adapter (MSMQT). |
| 27080 | Adds new functionality to BizTalk Server 2004 through an API set to work with messages and three new context properties. |
| 27081 | Fixes a problem where the BizTalk Server Accelerator for HIPAA 2.0 may incorrectly determine the HL segment structure in a document. |
| 27082 | Explains why you may receive a Failure occurred in parsing the remote folder listing error message when you use the BizTalk Server 2004 FTP Adapter. |
| 27083 | Describes a behavior in BizTalk Server 2004 where some messages may be duplicated in the Business Activity Services (BAS) Inbox and you receive a warning message in the event log. |
| 27084 | Fixes a problem in BizTalk Server 2002 where rejected HIPPA transactions are not listed in the AK904 element of the 997 receipt. |
| 27085 | Describes a problem that occurs when messages that are sent to the receive location are not suspended after you publish an orchestration as a Web service and the receive location is disabled. Includes a resolution for the problem. |
| 27086 | Explains how to change the Enterprise Single Sign-On (SSO) service account that is configured to run on the master secret server in BizTalk Server 2004. |
| 27087 | Discusses the Failed to generate the master secret (0x80070005) error message that you may receive when you install BizTalk Server 2004. |
| 27088 | Fixes a problem in BizTalk Server 2004 where you receive a Specified cast is not valid error message if you use a rule set in the Rules Composer or if you use a rule set with an orchestration after you install the .NET Framework 1.1 SP1. |
| 27089 | Fixes a problem where empty domain.FreeFormText elements are incorrectly generated for BizTalk Server Accelerator for RosettaNet version 2.0 messages in BizTalk Server 2002. |
| 27090 | Describes a bug in BizTalk Server 2004 where the ActivityModelDesigner API-provided default step parameters are not validated when you call the SaveActivityModelToSystem method. |
| 27091 | Fixes a problem in BizTalk Server 2004 where the orchestration stops responding and you must restart the BizTalk Server Host because an exception was not handled. |
| 27092 | Fixes a problem where you receive an HRESULT 0x80131500 error message in BizTalk Server 2004 Explorer or a Failed to execute SQL Statement error message in Visual Studio .NET 2003 if execution of the SQL statement takes too long. |
| 27093 | Fixes a problem in BizTalk Server 2004 where you receive a schemaLocation could not be resolved compiler error message when you import schemas from assemblies that have redundant imports. |
| 27094 | Discusses a documentation error for the Before Put FTP command and the After PUT FTP command in the online documentation for BizTalk Server Adapter for FTP. |
| 27095 | Discusses a workaround for a bug where deleted fields appear in the Promote Properties dialog box in Microsoft BizTalk Server 2004. |
| 27096 | Discusses multiple error messages that you receive in the BizTalk Server 2004 Event Viewer when a large file takes longer to download than the polling interval. |
| 27097 | Describes why the BizTalk Server Accelerator for HIPAA 2.0 may generate a 997 functional acknowledgment receipt that does not contain an AK4 segment. |
| 27098 | Discusses group inheritance for agreements in BizTalk Server 2004. |
| 27099 | Discusses a problem where you cannot validate an instance file with two positional records in the same schema that is generated by BizTalk Server 2002 or later. |
| 27100 | Discusses a Schema Cannot Be Found error message that you receive when you use a new schema in BizTalk Server 2004. |
| 27101 | Fixes the ProprietaryDocumentIdentifier element in the negative acknowledgement in the BizTalk Server Accelerator for RosettaNet 2.0. |
| 27102 | Discusses behavior in BizTalk Server where partners reject some messages that are sent by the BizTalk Accelerator for RosettaNet version 2.0. |
| 27103 | Discusses the run-time exception that you receive when the Copy Processing Instructions (PIs) property is set for multipart transform maps in BizTalk Server 2004. |
| 27104 | Discusses an error message that you receive when you delete a MessageBox database in the BizTalk Administration console in BizTalk Server 2004. |
| 27105 | Describes a problem that occurs when you configure BizTalk Server 2004 by using the BizTalk Server 2004 Configuration Wizard and you may receive an error message. |
| 27106 | Discusses a problem in BizTalk Server 2004 where you cannot open a list of saved queries in Health and Activity Tracking (HAT). |
| 27107 | Describes an Address Should be Unique error message that you may receive when you create a receive location in BizTalk Explorer. |
| 27108 | Discusses an AppDomain can not be unloaded error message that you receive when you deploy an assembly in BizTalk Server 2004. |
| 27109 | Explains that the BizTalk Framework (BTF) document type is not supported with the BizTalk Message Queuing Adapter (MSMQT) in BizTalk Server 2004. |
| 27110 | Fixes a problem that causes the BizTalkServerIsolatedHostQ table to be filled when a BizTalk Server tries to recover a lost database connection. |
| 27111 | Describes why the BizTalk Rules database is not created when you install BizTalk Server 2004 Administration Tools. |
| 27112 | Explains that the Hub Side SEED Wizard deployment tool does not package custom pipeline components in BizTalk Server 2004. |
| 27113 | This article describes how to configure multiple BizTalk Messaging Channels to launch or interface with the same BizTalk Orchestration Schedule, even though each channel uses different outbound document definitions. |
| 27114 | Provides information about integrating large security systems to improve operational efficiencies and reduce deployment cost in new LOB computing solutions. Tells how to offer single sign-on to existing programs and how to synchronize user passwords. |
| 27115 | Fixes a problem in BizTalk Server 2004 where you may not pick up files when you use the Electronic Data Interchange (EDI) Adapter and you specify the Uniform Naming Convention (UNC) path for the receive handler location. |
| 27116 | Fixes the disabled receive locations that occur during the BizTalkMsgBoxDb database failover. |
| 27117 | Fixes a problem where the BizTalk Server 2004 XML Mapper Database Lookup functoid/Value Extractor functoid produces inconsistent results when it tests a map with many Database functoids. |
| 27118 | Fixes a problem where BizTalk Server 2002 fails when the user credentials in a file receive function do not have Administrator rights. |
| 27119 | Adds the transactional feature in the Business Activity Monitoring (BAM) API in BizTalk Server 2004. |
| 27120 | Fixes a memory leak in Visual Studio .NET that occurs when you deploy a project that contains a schema with a number of roots and then you try to edit or create Send or Receive ports. |
| 27121 | Explains that if your installation of BizTalk Server 2004 requires more than one computer, you must specify domain groups and user accounts in the BizTalk Server Configuration Wizard. |
| 27122 | Fixes a problem in BizTalk Server 2004 where the SQL Adapter generates a System.OutOfMemory exception when it polls a large-sized message (about 205 MB). |
| 27123 | Fixes a problem in the SQL Adapter in BizTalk Server 2004 where you may receive a 0x80040e14 error message when the sync block of an updategram does not contain a white space. |
| 27124 | Explains why the BizTalk Server Message Queuing Adapter (MSMQT) fails with no error message when you send a message to @DIRECT=OS:NoSuchMachine\private$\NoSuchQueue1. |
| 27125 | Fixes a problem in BizTalk Server 2004 where you may receive an error message when you use the BizTalk 2004 Mapper to test a map. |
| 27126 | Explains why you cannot resume messages from BizTalk Server 2004 Health and Activity Tracking after Internet Information Services (IIS) is stopped and then is restarted. |
| 27127 | Explains why you cannot start the Enterprise Single Sign-On Service or the BizTalk Server Application Service after you install Windows XP Service Pack 2 (SP2) on a computer that is running BizTalk Server 2004. |
| 27128 | Fixes a problem where BizTalk Server generates a garbage file and the file is suspended when BizTalk Server tries to process a SMIME-encoded flat file. |
| 27129 | Fixes a problem where BizTalk Server 2004 cannot accept BizTalk Framework (BTF) receipts that BizTalk Server 2004 generates itself in Coordinated Universal Time (Greenwich Mean Time) + X time zones. |
| 27130 | Fixes the BizTalk Server EDI Adapter so that it can work with any EDI document types. |
| 27131 | Explains a condition where you receive a Login failed for user error message in the BizTalk Server 2004 Configuration Wizard when the wizard tries to create databases even if the user has the appropriate rights. |
| 27132 | Fixes a bug in BizTalk Server where a BizTalk Server serializer outputs delimiters in incorrect positions. |
| 27133 | Fixes a problem in BizTalk Server 2004 where you receive a NullReferenceException exception when you configure custom reference numbering of a send port. |
| 27134 | Describes a problem that occurs because the appID column of the xref_IDXRefData table is limited to 50 characters. Includes a hotfix that you can apply to extend the appID column from 50 characters to 255 characters. |
| 27135 | Fixes a bug in BizTalk Server 2004 where you receive an error message when you generate a native EDI instance. |
| 27136 | Fixes a problem in BizTalk Server 2004 where the whole Electronic Data Interchange (EDI) interchange is suspended if any subdocuments fail validation. |
| 27137 | Fixes a problem in BizTalk Server 2002 where error handling for the BizTalk Scriptor Application Integration Component (AIC) no longer functions correctly after you apply BizTalk Server 2002 Service Pack 1. |
| 27138 | Fixes a resource usage problem that occurs when you add a large schema in BizTalk Server 2004. The schema is automatically opened in Visual Studio .NET and this may cause BizTalk Server to stop responding for a while. |
| 27139 | Adds a new property that is named Openness to the global property schema in BizTalk Server 2004. |
| 27140 | Fixes a problem in BizTalk Server 2004 where any change to an Electronic Data Interchange (EDI) schema does not take effect. |
| 27141 | Describes why the Enterprise Single Sign-On component is not removed after you remove BizTalk Server 2004. |
| 27142 | Fixes a Health and Activity Tracking (HAT) problem where HAT does not reflect the completed status of a business process. |
| 27143 | Fixes BizTalk Server 2004 to improve performance by optimizing the internal processing of XPaths. |
| 27144 | Fixes a bug where outbound maps are not applied in a request-response receive port. |
| 27145 | Updates BizTalk Server 2004 so that the user can add custom HTTP headers and modify standard HTTP headers in HTTP request and response. |
| 27146 | Discusses how the Document Target Namespace and Response Root Element Name parameters are used in a BizTalk Server 2004 static one-way port that uses a transport type of SQL. |
| 27147 | Describes an Orchestration enlistment error message that you may receive when you enlist an orchestration to BizTalk Server 2004. |
| 27148 | Explains how a functoid that has been renamed from the Toolbox in the BizTalk Mapper will not retain its new name when it is placed on the BizTalk Mapper grid. |
| 27149 | Describes the behavior of BizTalk Server 2004 when it does not generate an error message for a functoid with an incorrect parameter value. |
| 27150 | Discusses how deploying an orchestration can cause documents that are in the location that is monitored by the orchestration's Receive location to be suspended. |
| 27151 | Discuss a problem that occurs when you rename schemas, but the new names do not appear in the BizTalk Type Picker dialog box. |
| 27152 | Describes an error message that you receive when you perform a query in the BizTalk Server HAT tool. |
| 27153 | Discusses why nothing occurs when you click the Go to Definition menu command for a Message in the Orchestration view of a BizTalk project. |
| 27154 | Explains why you cannot receive a file in an orchestration by using a pass-through pipeline in Microsoft BizTalk Server 2004. |
| 27155 | Fixes a problem in BizTalk Server 2004 when you try to match a character set name to its WebName property. |
| 27156 | Explains that you may have various unexpected problems when you try to use BizTalk Server 2004 on a virtual machine. Microsoft does not support this configuration. |
| 27157 | Describes a problem that occurs when you try to start a BizTalk Server host instance from the BizTalk administration console. |
| 27158 | Describes how to fix a problem that occurs when a user publishes an assembly from a computer that is running BizTalk Server 2004 and Microsoft Windows Server 2003. |
| 27160 | Describes a problem that occurs when the SQL Adapter repeatedly tries to process a bad message. Includes a hotfix that you can install to resolve this problem. |
| 27161 | Describes a problem that occurs when you try to process an XML document that is larger than 4 GB. BizTalk Server 2004 creates an integer overflow exception in the application log of the BizTalk Server computer. |
| 27162 | Describes a problem that occurs after you deploy a BizTalk Server 2004 project to additional Web servers. Includes a resolution that you can use to resolve the problem. |
| 27163 | Describes a problem that occurs when you catch a System.Web.Services.Protocols.SOAPException exception and you cannot see the headers or the body in the HTTP failure response. Includes a hotfix that you can use to resolve the problem. |
| 27164 | Describes a problem that may occur when you install a version of the .NET Framework that is later than version 1.1 on a computer that is running BizTalk Server 2004. |
| 27165 | Describes a problem that occurs when the 997 functional acknowledgment receipts incorrectly report that all transactions are accepted. Includes a hotfix to resolve the problem. |
| 27166 | Describes a problem that occurs when you receive a schema validation error when you have all optional children under a positional tagged element. Includes a hotfix that you can use to resolve the problem. |
| 27167 | Describes the operating systems that are supported by the FTP Adapter for BizTalk Server 2004. |
| 27168 | Discusses an error message that you receive in BizTalk Server 2004 Setup that occurs because BizTalk Server 2004 does not permit multiple components to share the same database. |
| 27169 | Fixes a problem where BizTalk Server 2004 rejects old-format reliable messaging receipts from BizTalk Server 2000 and from BizTalk Server 2002. |
| 27170 | Explains possible causes and resolutions for the Reading error. Exception information: TDDS failed to read from source database. SQLServer: SQLSERVER, Database: BizTalkMsgBoxDb. error message on a server that is running BizTalk Server 2004. |
| 27171 | Explains that an in-process BizTalk Server host may indicate Status unavailable in the BizTalk Administrator when you administer a remote BizTalk Server host. |
| 27172 | Fixes a memory leak that occurs when you open and you close maps in Visual Studio. |
| 27173 | Fixes an problem in BizTalk Server 2004 where you cannot override the HTTP Adapter properties within a send port. |
| 27174 | Explains an issue where assemblies with a common name in a common namespace may not be available for selection in a BizTalk Server 2004 project in Visual Studio .NET 2003. |
| 27175 | Fixes a problem in BizTalk Server 2004 so that you can disable chunked encoding in HTTP transport. |
| 27176 | Fixes a problem in the BizTalk Server 2004 HTTP Adapter where you cannot set HTTP headers on the response from a HTTP receive request from an Orchestration. |
| 27177 | Fixes a problem where BizTalk Server throws a PersistenceException exception when it tries to persist the state of an orchestration instance to the database. |
| 27178 | Fixes a problem where the BizTalk Server 2004 MIME/SMIME Decoder in a receive pipeline does not decrypt an incoming message. |
| 27179 | Discusses a problem that occurs when you delete the BizTalk 2004 Server database before you run the configFramework.exe /u command (unconfigure mode). Describes a workaround for this problem. |
| 27180 | Fixes an issue where the HAT UI becomes unresponsive if BizTalk Server is processing a lot of data. |
| 27181 | Fixes a compilation error that may occur while you are compiling large maps. |
| 27182 | Describes an error that may occur if you use BizTalk Server 2004 MSMQT to send data that a BizTalk Server 2000 or 2002 Message Queuing receive function retrieves and the data contains a byte order mark (BOM). Describes two resolutions for this problem. |
| 27183 | Discusses why this error occurs when the element type definition in the Web reference contains a period (.) character. Explains how to resolve this error. |
| 27184 | Fixes a problem where BizTalk Server rejects the response when you use content-based routing with a request-response port. |
| 27186 | Fixes a problem in the BPEL Import Wizard that causes it to quit unexpectedly when it reaches the last step. |
| 27187 | Fixes the problem of BizTalk Server Accelerator for RosettaNet permitting an unsigned message to successfully process even when the agreement is expecting a signed message (RNIF1.1). |
| 27188 | Fixes an issue where BizTalk Server 2002 cannot accept the reliable receipt from BizTalk Server 2004 because of the XML declaration and encoding. |
| 27189 | Fixes a problem with the Message Box backup SQL scripts that report failure incorrectly. |
| 27190 | Explains that you will receive an error message if you try to validate a flat file document when the first node is named X12_EnvelopeHeader on a computer that is running the BizTalk Server Accelerator for HIPAA 2.0. |
| 27191 | Discusses the issue of BizTalk Server 2004 not generating a warning when you use a special character as a wrap character that is not permitted as a wrap character. |
| 27192 | Fixes an issue where the BizTalk Server Accelerator for HIPAA generates a 997 receipt that reports an incorrect duplicate transaction ID. |
| 27193 | Fixes a problem where element reference resolution fails due to multiple imports with a same namespace. |
| 27194 | Fixes an issue where the generated 997 receipt reports the wrong element as having been in error in the original document. |
| 27195 | When you try to use Microsoft Office InfoPath 2003 to submit XML data to a Microsoft BizTalk 2002 Server application, the following problems may occur: When you create an InfoPath 2003 Form template that integrates with BizTalk Server 2002, and you... |
| 27196 | Discusses the SOAP port and the authentication types that are available in BizTalk Server 2004. |
| 27197 | Discusses why duplicate entries appear in the Certificate dialog box in BizTalk Server 2004. The fields that appear in the Signature Certificate list do not provide sufficient information to select a public key certificate. |
| 27198 | Describes the error messages that you may receive when you test a map with Input or Output set to Native in BizTalk Server 2004. |
| 27199 | Fixes a problem where BizTalk Server repeatedly restarts itself when the SQL log file for the InterchangeDTA database is full. |
| 27200 | A Microsoft BizTalk Server 2002 HTTP receive function may leak memory in the Microsoft Internet Information Services (IIS) process that is supporting the HTTP receive functions. These processes include the DLLHOST process and the Inetinfo process.... |
| 27201 | Fixes an issue with high CPU utilization when a timed scope is not throwing the timeout exception in BizTalk Server 2004. |
| 27202 | Describes the problems that are fixed in BizTalk Server 2004 Rollup Package 2004. |
| 27203 | Explains the steps to remove the BizTalk Server 2004 Rollup Package 1 that is mentioned in Knowledge Base article 837168. |
| 27204 | Explains that the BizTalk Server 2004 Configuration Wizard can fail if you specify the user account or the group to be used for the SSO Administrator with a nomenclature that specifies the domain name as the fully qualified domain name. |
| 27205 | Explains that the Backup BizTalk Server SQL Server Job that is created by BizTalk Server 2004 Setup fails if the adm_OtherBackupDatabases table does not exist. |
| 27206 | Explains that the Interchange.Submit method and the Interchange.SubmitSync method are not supported in BizTalk Server if the calls to these methods are made from a custom preprocessor. |
| 27208 | Fixes a problem that you may experience while generating X12 977 receipts in BizTalk Server 2002. |
| 27209 | Provides a hotfix that permits you to set where you want the xsl:for-each statement. |
| 27210 | Fixes a problem where the Update facts function causes the wrong rules to be evaluated again. |
| 27211 | Explains that when you use the ActiveXMessageFormatter object to send a byte array to a Microsoft Message Queuing Server (MSMQ) receive function, BizTalk Server may generate an error message. |
| 27212 | Discusses a problem where you receive a permission denied error message when installing the Claims Processing sample of BizTalk Server Accelerator for HIPPAA 2.0. Describes how to resolve this problem. |
| 27213 | Fixes a bug where TS835W1__PLB_ProviderAdjustment segments are lost when the HIPAA 835 document splitting schema (835_v2_wpc_multiple.xml) is used as document definition. |
| 27214 | This hotfix adds a new functoid that allows for deletion of an ID that was created with the CrossReferencing APIs. |
| 27215 | Fixes slow performance issue when you use CrossReference APIs by adding performance optimizations. |
| 27216 | Explains that you receive a Compile error in hidden module: ConnectionInfo error message when you try to open the Business Activity Monitoring (BAM) Excel workbook. |
| 27217 | Fixes the problem of slow performance by adding optimizations to maps that use logical functoids. |
| 27218 | Describes an issue that may occur if the Message Queuing service is already installed when you configure BizTalk Server 2004. Describes a workaround for this issue. |
| 27219 | In Microsoft BizTalk Server 2004, when you use the Microsoft Windows Management Instrumentation (WMI) classes MSBTS_DeploymentService API to deploy large assemblies in BizTalk Server 2004, you may receive an error message that is similar to the... |
| 27220 | Discusses why you receive a Terminate request could not be sent for the specified instance error message when you try to end a running service instance by using the MSBTS_HostQueue.TerminateServiceInstancesByID method. |
| 27221 | Fixes an unhandled exception that may occur in the flat file parser when BizTalk Server 2004 is under heavy stress. |
| 27222 | Fixes the problem that trailing spaces are not recognized by the BizTalk Server Accelerator for HIPAA as part of the minimum length. |
| 27223 | Fixes a problem that occurs when you use the same condition two times in a rule set, one time with the NOT operator and one time without the NOT operator. |
| 27224 | Fixes a bug that causes the HTTP adapter to fail to send messages larger than 48 KB if there is a proxy. |
| 27225 | Provides a hotfix to correct the expression error A service or property can only be accessed on the current service. |
| 27226 | Discusses an error that occurs when you try to configure a database with a name that is more than 123 characters in length. |
| 27227 | Microsoft BizTalk Server 2004 includes a new component named the Business Rules Engine (BRE). You can use BRE to dynamically add, edit, and delete business rules that are being applied to the business processes. |
| 27228 | Explains that the SQL Server 2000 update 831950 must be installed on the computer or computers where SQL Server 2000 is installed and where the BizTalk Server databases are housed. |
| 27229 | Explains that profiles created with the Tracking Profile Editor (TPE) cannot be configured to track string messages. Tracking profiles depend on information in XML schemas for tracking messages. String messages do not use schemas. |
| 27230 | Explains why this error occurs and provides links to many language versions of the rollup packages that you can install to fix this problem. |
| 27231 | Explains why duplicate path entries appear in the PATH system environment variable after you reinstall BizTalk Server 2004. Explains how to remove the duplicate path entries. |
| 27232 | Discusses a session timeout error when viewing receipts in the Document Tracking interface. Explains how to obtain the hotfix that corrects the problem. |
| 27233 | Explains that an error may occur when the BizTalk Server Configuration Wizard is installing databases for a component that requires SQL Server Analysis Services. Explains how to resolve this problem. |
| 27234 | Describes an issue where the BizTalk Server repair operation does not re-create the DefaultReceiveLocation folder. If this folder is removed, Business Activity Services does not work correctly and you must reinstall BizTalk Server. |
| 27235 | Describes how all BizTalk project assemblies in the directories referenced by a package are deployed when you install a hub SEED package on a spoke. Explains a workaround for this problem. |
| 27236 | Describes an issue where performance counters from a earlier pre-release build of BizTalk Server 2004 may not be completely removed when you remove BizTalk. |
| 27237 | Describes a limitation where you cannot configure send handlers or receive handlers for the MSMQT adapter on any host except the host that the adapter was activated on. |
| 27238 | Explains that error events are not logged when the BTSSvc service is denied access to a folder bound to a Receive Location folder if permissions are changed for the folder after the BTSSvc service is started. |
| 27239 | Explains that the BizTalk Server Application Service must be stopped and then restarted after a modified schema is redeployed. |
| 27240 | Discusses an error message that you receive after you create a new MessageBox in the BizTalk Server 2004 Administration MMC snap-in with the Disable new message publication option enabled and then you try to delete the MessageBox immediately. |
| 27241 | Describes a problem where the Orchestration Designer does not prevent you from assigning the same transaction identifier to the Compensation property value of multiple Compensation shapes. Explains a workaround for this problem. |
| 27242 | Explains that the registry values that contain the locations of the rule store are not updated when you reinstall BizTalk Server. Therefore, the rule store location may be incorrect. Explains how to fix this problem. |
| 27243 | Describes a problem where BPEL Import Wizard creates an .odx file with a message type that is set to system.string when you import a WSDL file that contains a data type of xsd:integer. Explains how to work around this problem. |
| 27245 | This article discusses methods that you can use to resubmit some suspended items in the Microsoft BizTalk Administrator MMC. Typically, the administrator performs the resubmission after the initial problem has been fixed. Note Not all suspended items... |
| 27246 | When you try to use BizTalk Server Accelerator for Health Insurance Portability and Accountability Act (HIPAA) to process a X12_4010_820 flat file that is larger than 6 megabytes (MB), the program stops responding (hangs) and the following error is... |
| 27247 | BizTalk Server Accelerator for HIPAA stops responding and generates the following error in the Application log in Event Viewer when it processes large (6 MB) 837P flat files: An error occurred in BizTalk Server. Details: ------------------------------... |
| 27248 | Explains how to install the BizTalk Adapter Trace Utility and enable tracing in BizTalk Server 2004. Trace files can be useful tools for debugging problems in BizTalk Server 2004. |
| 27249 | Microsoft BizTalk Server may generate unexpected output when it is serializing an XML file from a delimited flat file. For example, some of elements that are designated as optional may not be created although they exist in the flat file input. |
| 27250 | Explains that the BizTalk Message Queuing Configuration options that you specify the first time that you run the Configuration Framework Wizard cannot be changed unless you remove and reinstall BizTalk Server 2004. |
| 27251 | If an XLANG schedule is marked as Treat the XLANG schedule as a COM+ component , activation fails in BizTalk Messaging and you receive the following error message: Distributed transaction completed. Either enlist this session in a new transaction or... |
| 27252 | Explains how to resolve the error 'Activeview.columnaxis' is null or not an object that occurs when you use BizTalk Server 2004 Health and Activity Tracking (HAT). |
| 27253 | If you set Microsoft BizTalk Mapper to generate an XML declaration in the outbound document, the document may be encoded as UTF-8, although the XML declaration indicates that the document is encoded as UTF-16. |
| 27254 | Describes why Party Resolution does not succeed if BizTalk Server is on a different computer from the one that is running SQL Server and that hosts the BizTalk Server databases in a Workgroup environment. Explains how to resolve this problem. |
| 27255 | Explains that, to change the Authentication trusted setting for a BizTalk Server Host, the user account must be a member of the db_owner role for all the BizTalk Server MessageBox databases. Also explains how to change this setting. |
| 27256 | Explains that if you try to run a BizTalk Server 2004 Orchestration that contains rules, you may receive an error message if you installed the Rules Engine separately from the BizTalk Engine. |
| 27257 | BizTalk Server 2004 connects systems, people, and trading partners through manageable business processes and transport adapters. Hear about MSMQT adapter technical features, differences between MSMQ and MSMQT, answers to frequently asked questions. |
| 27258 | This article applies to the release candidate of Microsoft BizTalk Server 2004. This article discusses known issues that you may experience when you use Microsoft BizTalk Server 2004. |
| 27259 | The BizTalk Server XLANG Scheduler COM+ application does not start, and the XLANG tab is missing from the XLANG Scheduler COM+ application properties page. The following event is logged in the application event log: A COM+ service (such as Queued... |
| 27260 | When you use the BizTalk Messaging Manager, you may receive an error message that is similar to the following: Error 0x8007000E: Ran out of memory. |
| 27261 | If you select the Disassemble Result Set option, and then you request many records, the SQL request does not succeed and you receive the following event error message in the application log file of your computer that is running Microsoft BizTalk... |
| 27262 | You may not see a performance improvement when you add more processors to a BizTalk system that processes large flat file documents. However, adding more processors may improve performance when you process the same number of smaller documents. |
| 27263 | By default, the transaction isolation level for all Microsoft BizTalk Server COM+ components is set to Serialized if you install Microsoft BizTalk Server 2002 on a computer that is running Microsoft Windows Server 2000. However, the transaction... |
| 27264 | The table in the More Information section of this article describes the versions and the editions of Microsoft SQL Server that can handle the database tables for the different versions and editions of Microsoft BizTalk Server. |
| 27265 | Microsoft BizTalk Server 2002 may not correctly recognize a graceful close from a HTTP 1.0 client (a close_notify alert) that is connecting over HTTPS. This problem may occur after you install BizTalk Server 2002 Service Pack 1. When this problem... |
| 27266 | If you install Microsoft BizTalk Server 2002 Service Pack 1, or if you apply any BizTalk hotfix that was released before BizTalk Server 2002 Service Pack 1, the X12_EnvelopeHeader may be missing and may not be viewable in the BizTalk Editor and in the... |
| 27267 | If you run a query on the Microsoft BizTalk Server Tracking Web site, the query generates a Query Results page. This Query Results page contains line items that represent the interchanges and the documents that the query returns. If you click the... |
| 27268 | When you try to use Microsoft Outlook Express to open a message that was encrypted with Microsoft BizTalk Server, you may receive one of the following messages from Outlook Express: Message could not be displayed Outlook Express encountered an... |
| 27269 | When you submit XML documents with an XML processing instruction, the processing instruction is stripped. For example: (?xml version='1.0'?) |
| 27270 | In any BizTalk tool, when you select About on the Help menu, the version number does not include the sub-build version number. For example, build x.xx.xxxx. 01 appears as version x.xx.xxxx. 00. |
| 27271 | If your HIPAA message has an ampersand (&), an angle bracket ( or ), an apostrophe ('), or a quotation mark ('') special character in the ISA02__AuthorizationInformation field, Microsoft BizTalk Server Accelerator for HIPAA cannot process the... |
| 27272 | This article describes how to move your Microsoft BizTalk Server 2002 databases from one computer that is running Microsoft SQL Server to another computer that is running SQL Server. |
| 27273 | After you install Microsoft BizTalk Server 2002 Service Pack 1 (SP1), you may receive one of the following error messages from BizTalk Server when it tries to process a signed RosettaNet message: Message 1 An error occurred in BizTalk Server. Details:... |
| 27274 | This article is a listing of article numbers for bugs that were fixed in BizTalk Server 2002 Service Pack 1 (SP1). Click the Content ID number that precedes the title of the bug to view the article. about how to obtain the latest service pack for... |
| 27275 | The ConvertMoneyStringToNumber method of the DataFunctions_4_0 component (included with Commerce Server 2000 and BizTalk Server 2000) returns values in the base monetary unit for a given locale. Therefore, if a value is given in dollars,... |
| 27276 | When you run Microsoft BizTalk Server in an environment that uses transactional receive functions and non-transactional receive functions, you may receive the following error messages in the event log for the non-transactional receive functions: Event... |
| 27277 | The Microsoft BizTalk Accelerator for Financial Services Rollup corrects the problems that are described in the following Microsoft Knowledge Base articles: 319290 HIPAA Properties Lost When You Save Schema in BizTalk Editor 319290 HIPAA Properties... |
| 27278 | When you configure a BizTalk Server Messaging Port to use the HTTPS transport, the Messaging Port fails to process documents and an error similar to the following occurs in the BizTalk Server application log: Event Type: Error Event Source: BizTalk... |
| 27279 | When you expand a BizTalk Server group in the BizTalk Server Administrator, there may be no server instances visible even though BizTalk servers exist in the group. This problem only occurs when you run the BizTalk Server Administrator on the Windows... |
| 27280 | When you try to view files from Web Distributed Authoring Version (WebDAV) in BizTalk Editor or BizTalk Mapper, you may receive the following error message: No BizTalk Server repository was found on http://localhost/BizTalkServerRepository/DocSpecs.... |
| 27281 | When you use the BizTalk Messaging Manager to manage a remote BizTalk Server, you may experience one of the following symptoms: When the wizard creates a new configuration object, such as a port, it does not complete when you click Finish . It just... |
| 27282 | BizTalk Server is unable to process documents in the Work queue, and the following error message is displayed in the Application log of the BizTalk computer: Event Type: Error Event Source: BizTalk Server Event Category: Document Processing Event ID:... |
| 27283 | If you use the HTTP transport to post a document to a Microsoft BizTalk Server HTTP receive function, the post fails and an error that is similar to the following is written to your BizTalk Server application log: Event Type: Error Event Source:... |
| 27284 | This article provides information on the bugs that are fixed by BizTalk Server 2000 service packs. Service packs are cumulative, so bugs that are fixed in one service pack are also fixed in subsequent service packs. For example, the bugs that are... |
| 27285 | When you execute the Dta_purge_old_records stored procedure to archive or remove your tracking database, you may experience exclusive table locks. These table locks cause table locking problems with other processes that are trying to access the... |
| 27286 | When you run the COM Binding Wizard in the BizTalk Server Orchestration Designer, you may receive the following error message: Concepteur d'Orchestration BizTalk Probleme dans modMain.GlueContainedShapeToContainerConnectionPoint Numero d'erreur:... |
| 27287 | If you have configured the BizTalk Server Messaging service to start under a different user or start manually instead of automatically, these configurations are lost when you install BizTalk Server 2000 SP1. This can cause problems when the configured... |
| 27288 | After you install BizTalk Server 2000 Service Pack 1 (SP1), X12 documents fail validation. |
| 27289 | An installation of Microsoft BizTalk Server on a Microsoft Windows 2000 Terminal Server or a Microsoft Windows Server 2003 Terminal Server that is running in Application mode may not perform as expected. |
| 27290 | After you execute the BizTalk Tracking database stored procedure DTA_PURGE_OLD_RECORDS with an nPurgeType of timestamp and an nPurgeValue of hours , the following error message may occur in SQL Query Analyzer: Server: Msg 535, Level 16, State 1,... |
| 27291 | The Advanced button in the Advanced Configuration dialog box of the BizTalk Messaging Manager Channel Wizard allows you to access the properties for the primary transport component of the Messaging Port by clicking the Properties button. When the... |
| 27292 | Microsoft BizTalk Server 2000 does not support the development or the use of any components that are written in Microsoft Visual Studio .NET. |
| 27293 | During the BizTalk Messaging Management Database portion of BizTalk Server Setup, you may receive the following error message: An error occurred while attempting to create the BizTalk Messaging Management database. The specified SQL server might not... |
| 27294 | This article explains how to create a simple Application Integration Component (AIC) for BizTalk Server by using Visual Basic .NET. This AIC writes the information about the document that it is processing to the BizTalk Server Temp folder, which, by... |
| 27295 | When you exchange binary data by using a custom C# preprocessor or postprocessor with the BizTalk Adapter for MQSeries, you may notice that your custom processor does not manage the data correctly. |
| 27296 | When you try to view files from Web Distributed Authoring Version (WebDAV) in Microsoft BizTalk Server BizTalk Editor or BizTalk Mapper, you may receive the following error message: No BizTalk Server repository was found on http:// BizTalkServer ... |
| 27297 | When you use the Database Value Extractor functoid in a map to extract a date field, your document may fail validation against the outbound document definition. BizTalk Server may log the following validation error in the event log: Event Source:... |
| 27298 | Certain BizTalk Messaging Manager objects, including Document Definitions , Envelopes , and Channels , must be mapped to specifications that are stored in the Web Distributed Authoring and Versioning (WebDAV) repository. If the WebDAV repository... |
| 27299 | BizTalk Server 2000 may not correctly verify a digital signature and decrypt an S/MIME encoded file. When this problem occurs, the message is immediately placed into the Suspended queue. |
| 27300 | When you attempt to run the BTConfAssistant sample that is included in BizTalk Server 2000, the following error message occurs: Run-time error '429': ActiveX component can't create component |
| 27301 | BizTalk Server has added the ability for the BizTalk messaging engine to prioritize the processing of messages from the work queue. After you install the fix that is described in this article, you can set a priority level between 1 and 10 on a... |
| 27302 | When BizTalk Server 2000 is running under a high load condition, the following error may be generated in the Application event log: Event Type: Error Event Source: COM+ Event Category: SVC Event ID: 4194 Date: 6/13/2001 Time: 1:34:47 AM User: N/A... |
| 27303 | When you use both a logical functoid and a normal link as input to a destination record, the BizTalk Mapper may generate incorrect XSLT code. For example, you may expect output that is similar to the following, in which the attribute for an element is... |
| 27304 | When you use the Simple Mail Transfer Protocol (SMTP) to transmit a document to an Open Destination messaging port in BizTalk Server, the subject of the resultant e-mail message is the Interchange tracking ID and cannot be modified. |
| 27305 | The selection of messages from the Retry queue in BizTalk Server 2002 may cause some messages to not be processed for a long time (which is also known as starvation). If these unprocessed messages are related to messages on which the running XLANG... |
| 27306 | When you do a Controlled Shutdown from the XLANG Scheduler COM+ application, some schedules that have a WHILE loop may not dehydrate. In some instances, the XLANG Scheduler application may stop responding (hang). |
| 27307 | If you configure a BizTalk Map to use the Database Lookup functoid to connect to an Oracle Database, the following error may occur when you attempt to test the map: ORA-00903: invalid table name Also, the Database Lookup functoid will fail to retrieve... |
| 27308 | After you install Microsoft BizTalk Server 2002 Service Pack 1 (SP1), you may notice that BizTalk Server document tracking no longer tracks file name attributes for files that it has received from a file receive function. |
| 27309 | When you configure Microsoft BizTalk Server 2000 with four or more worker threads, a Key Exclusive lock may occur on the BizTalk SQL Server database, InterchangeBTM. This lock does not occur if the number of worker threads is set to 1. No associated... |
| 27310 | Service packs are the means by which Microsoft distributes bug fixes. Service packs keep a product current. Service packs include updates and may include system administration tools, drivers, and additional components, which are conveniently bundled... |
| 27311 | To send a Japanese IDOC from a computer that is running the English version of Microsoft Windows 2000 to a SAP system, you must use the following configuration: Configure the SAP system to run codepage 8000. Add the system environment variable... |
| 27312 | This article contains information from the BizTalk Server 2000 Readme.htm |
| 27313 | This article contains information from the BizTalk Server 2000 Readme.htm file. |
| 27314 | This article contains information from the BizTalk Server 2000 Readme.htm |
| 27315 | When you try to use the Document Tracking Activity user interface, you may receive the following error message: Windows has detected that this computer does not have Office Web Components installed. These components must be installed prior to setup. |
| 27316 | The BizTalk Mapper may compile maps incorrectly if a record connected to the Iteration functoid has a max occurrence of 1 and its parent node has a max occurrence of * . The Iteration functoid should count the iterations of the record that it is... |
| 27317 | When you create a BizTalk messaging port to an XLANG application, the option for data encryption is disabled. |
| 27318 | When you try to create or edit items in the BizTalk Messaging Manager, you may receive the following error message: BizTalk Messaging Manager Error The organization could not be saved. Error 0xC0C0129C: This object cannot be saved or removed because... |
| 27319 | The BizTalk Orchestration Designer is a design-time tool that allows users to diagram and implement business processes. The business process typically includes the handling of business documents, and the business documents can include XML or non-XML... |
| 27320 | When you attempt to use a MAILTO: SMTP address that contains a query string with an open destination port, the following error message may occur: The server rejected one or more recipient addresses. The server response was: 501 5.5.4 Invalid Address... |
| 27321 | When you modify a port that you have saved previously, and you specify a Custom envelope for the port, when you attempt to save the port, the following error message occurs: The message port could not be saved. Error 0xC0C012CB: If the envelope format... |
| 27322 | When you attempt to set the date format in the Custom Date/Time Format property in the BizTalk Editor, you cannot use a period (.) as a date separator. |
| 27323 | When you use the BizTalk Messaging Manager to create a new port with a port name that already exists, you are prompted with the following error message when you complete the wizard: The messaging port could not be saved. Error 0xC0C01244: The... |
| 27324 | When you install BizTalk Server 2000, the sort order on the Programs menu may change from the order that was set before installation. |
| 27325 | The multiply functoid used in the BizTalk Mapper does not return trailing zeros after a decimal point. For example, if a map takes two input fields, quantity and price, and outputs to another field, extended price, if the extended price is 25.50, the... |
| 27326 | When you test a map in the BizTalk Mapper, the following message may occur in the output window: The XML page cannot be displayed. Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.... |
| 27327 | When you receive a secure e-mail message from BizTalk Server 2000, your e-mail client may display the following error message: This document has an invalid digital signature. Open the message for more information. |
| 27328 | When you submit a large interchange, you may receive one or more of the following error messages: An error occurred in BizTalk Server. Details: ------------------------------ The database call failed and returned the following error string: String... |
| 27329 | BizTalk Server 2000 requires a minimum of 25 MB of free disk space on the system drive to install correctly. Insufficient disk space on the system drive may result in a runtime error during the BizTalk Server Setup file copy process. |
| 27330 | When you execute an Orchestration schedule, you may receive one or more of the following error messages in the Event Viewer: Event Type: Error Event Source: XLANG Scheduler Event Category: Engine Event ID: 12293 Description: The XLANG Scheduler Engine... |
| 27331 | If you configure a Messaging Port using the file transport and you do not specify a filename with the directory path, you may receive the following error message: An error occurred while opening the target file. The server encountered a transport... |
| 27332 | If you use Microsoft BizTalk Server Accelerator for RosettaNet 2.0, and you create a Partner Agreement, you may not receive an error message in the event log if the relationship is not set up correctly. For example, if you create a Partner Agreement... |
| 27333 | When Microsoft BizTalk Server Accelerator for HIPAA processes large (6 MB, for example) 4010A1 835 flat files, it stops responding, and you receive the following error message in the application log in the Event Viewer: An error occurred in BizTalk... |
| 27334 | Microsoft BizTalk Server 2002 Service Pack 1 includes an updated version of the script file BTS_Tracking_Archive_Purge_Script.sql for the InterchangeDTA database. However, this file is corrupted. You cannot load this file in Microsoft SQL Server. |
| 27335 | In the C# BTSInterchange sample that is included with the Microsoft BizTalk Server Toolkit for Microsoft .NET, the constructor that is in the BTSInterchange.cs file for the BTSInterchange object takes ten parameters. One of these parameters is the... |
| 27336 | You cannot secure a default installation of BizTalk Server because the BizTalk Server state engine does not validate its callers, and the BizTalk Server state engine default configuration must run under the context of an interactive user. This article... |
| 27337 | When you run the BizTalk Server 2000 Setup program, if the program stops responding (hangs) or fails (crashes), and you restart (reboot) your computer, the BizTalk Messaging Service may cause Windows 2000 to restart repeatedly. |
| 27338 | The current implementation of SendHTTPX does not support NTLM authentication. |
| 27339 | When you edit a channel, you may experience deadlock issues with BizTalk Server while the server is under stress. The following errors may be logged to the event log: An error occurred in BizTalk Server. Details: ------------------------------ The... |
| 27340 | When you attempt to save a document specification to a WebDAV repository on a remote computer, you may receive the following error message: Unspecified Error. |
| 27341 | When you reference SQL Server names or BizTalk Server names in the BizTalk Server environment, you must always use the NetBIOS computer name, or the following error messages may occur. In SQL Server, if a DNS name is entered for any of the SQL Server... |
| 27342 | BizTalk Server may not remove leading or trailing spaces from numeric fields when parsing flat file data. This means that space characters are included with the data in numeric fields. |
| 27343 | When navigating a WebDAV directory structure through the BizTalk Mapper or BizTalk Editor by using the Retrieve from: or Store to: dialog boxes, there are no visual cues to indicate where in the WebDAV directory structure you are. If the following... |
| 27344 | The BizTalk Mapper or BizTalk Editor Retrieve from WebDAV and Store to WebDAV dialog boxes revert to the default, large icon view even though you have previously configured them for a small icon view. |
| 27345 | You cannot create a port to an application in the BizTalk Messaging Manager when you use an application from an organization other than the default organization. Also, you cannot add applications to any organization other than the default organization... |
| 27346 | When you attempt to process a BizTalk Framework compliant self-routing business document, the following error message may occur in the BizTalk Server Application event log: An error occurred in BizTalk Server. Details: ------------------------------... |
| 27347 | During the installation of BizTalk Server 2000, the Orchestration Persistence database is installed by using a separate executable (XLANGsetupDB.exe). Because of this, the options used in the previous BizTalk Server database setup screens are not... |
| 27348 | When you install BizTalk Server 2000, you cannot use the Tab key to move to the Select an Existing BizTalk Server Group option in the Configure a BizTalk Server Group dialog box. |
| 27349 | When you uninstall BizTalk Server 2000 and the system prompts you to reboot (restart) your computer, if you reinstall the software without restarting the computer, the system continues to function normally until you restart it. After you restart your... |
| 27350 | When you create an XSL map in the BizTalk Mapper, you can add functoids without linking them to anything. These unused functoids are saved as part of the XSL map, even though they appear to be unused. This behavior is by design. |
| 27351 | When you use the BizTalk Editor to create records and fields for a file specification, you may receive the following error message: BizTalk Editor A field element or record with the name Record1 already exists in the tree. You cannot rename a field... |
| 27352 | Many locales use a decimal separator other than a period (.). For example, five and three quarters may be represented as 5,75 . When you attempt to use this format in BizTalk Server 2000, a document validation error may occur. |
| 27353 | To determine the version or service pack level of BizTalk Server that is currently installed, view the file properties for any of the DLLs in the BizTalk Server installation folder, and then compare the version number with the values in the chart that... |
| 27354 | In the BizTalk Mapper, when you click Options on the Tools menu and then click the Color tab, you cannot use the arrow keys to select a color from the the palette drop-down list. In addition, if you place the pointer over a color and press the ENTER... |
| 27355 | When you open a document specification with the BizTalk Editor that contains an invalid content type, you receive a dialog box that states the following: Content must be empty, eltOnly, textOnly, or mixed. However, BizTalk Editor does not... |
| 27356 | BizTalk Server may place an outbound document into the Suspended queue with the following error message: The BizTalk Framework timestamp receiptRequiredBy has expired. This document is no longer valid. |
| 27357 | When the user tries to start the BizTalk Server Administration MMC Snap-in, if the installation drive is full, the user may receive the following error message: Disk is Full Although memory is available, the BizTalk Server Administration MMC Snap-in... |
| 27358 | BizTalk Server may append random characters to a flat file output when no characters are needed or required. |
| 27359 | When you modify a file receive function in the Japanese version of BizTalk Server 2000, the following error message may occur when you click OK to close the Add a File Receive Function dialog box: ????????????BizTalk Server WMI ????????????... |
| 27360 | After you install BizTalk Server Service Pack 1 or BizTalk Server Service Pack (SP) 1a, you may notice decreased performance when you are using the File Transport. You may observe this decrease in performance regardless of whether the file path is... |
| 27361 | If a file receive function retrieves a file and places the document in the Work Queue, and then the power goes off before the file can be deleted from the file receive function polling location, when you restart the computer, the file receive function... |
| 27362 | If you fail over a clustered database that houses the tables that the BizTalk Messaging Service requires, the BizTalk Messaging Service may stop processing documents until you stop and restart the BizTalk Server Interchange Application COM+... |
| 27363 | In the BizTalk Editor, when you try to rename a Record or Field to the name of an existing Record or Field, the following error message appears: A field element or record with the name record1 already exists in the tree. You cannot rename a field to... |
| 27364 | When you use the XLANG Event monitor to monitor an XLANG schedule that has a port or action name with double-byte characters, the XLANG event history may return garbage characters in some of the event fields such as SourceEnter, SourceLeave, and... |
| 27365 | When a document with multiple transaction groups is submitted directly to a channel, the parser generates a receipt, which is sent back to the sender for the first transaction group only. Subsequent transaction groups may fail to generate receipts.... |
| 27366 | When you try to resubmit a document from the BizTalk Server Suspended Queue, the document may be processed incorrectly because of a mapping error, a validation error, or other types of errors. |
| 27367 | When you use the BTConfigAssistant SDK sample to load an XML representation of a BizTalk configuration, if the configuration contains multiple tracking fields set to Custom , the following error message may occur: One or more arguments are invalid.... |
| 27368 | BizTalk Server Parser and Serializer components or Custom Parser and Serializer components may fail to serialize output. BizTalk Server may fail to serialize data into its native format, if the data contains embedded nulls. The document being... |
| 27369 | When you use BizTalk Orchestration, your timed transactions may fail because the schedule is not rehydrated properly. |
| 27370 | BizTalk Server may not properly validate documents with text elements that do not adhere to the required minimum or maximum lengths. |
| 27373 | When you use SMTP as a Primary Transport, the default subject line that is sent with the message contains the interchange GUID. You can manually modify the subject line by opening the Channel that is bound to the port and overriding the properties by... |
| 27374 | You may experience lost or duplicate documents when you use BizTalk Server 2000 in a clustered environment. |
| 27375 | The IInterchange::Submit method in BizTalk Server 2000 does not provide a way for a user to retrieve a response document. The method call to IInterchange::Submit is an asynchronous call. However, if a response document is expected, the data is not... |
| 27376 | When you validate an XML instance or document against a schema, Date and Date Time fields are not checked for a valid number of days per month, other than ensuring that the numeric value in a Day field is not greater than 31. |
| 27377 | BizTalk Server uses receive functions to automate the retrieval of messages from Message Queuing (MSMQ) queues. When BizTalk Server attempts to retrieve messages from MSMQ queues, it attempts to handle the retrieval within a transaction to make sure... |
| 27378 | When you create a Port and specify an X12 envelope that has a hexadecimal 15 for the segment terminator, you receive the following error message when you click Finish to save the Port: An invalid character was found in text context. |
| 27379 | When you use the Index functoid in the BizTalk Mapper, the resulting XML output may be missing data or may reflect data that is not correctly generated. |
| 27380 | BizTalk Server may generate an error similar to one of the following errors when it processes SMIME signed or encrypted messages: Error 1 An error occurred in BizTalk Server. Details: ------------------------------ Security: Error occurred Malformed... |
| 27381 | BizTalk Messaging may generate an output document that contains unreadable, garbage characters from a MIME-encoded input document, which contains attachments with Japanese double-byte character set (DBCS) characters. |
| 27382 | When you open an XLANG schedule (.skv) file numerous times without closing the BizTalk Orchestration Designer, most of the BizTalk Orchestration Menu items are disabled (grayed out). |
| 27383 | When you open and close new drawings in the BizTalk Orchestration Designer, a memory leak may occur until you close the Orchestration Designer. |
| 27384 | When you install Microsoft BizTalk Accelerator for HIPAA 2.0 on a computer that is running Microsoft Windows Server 2003, you may receive the following error message: A method call to an object in a COM+ application was rejected because the caller is... |
| 27385 | In Visio, you experience performance degradation when performing any of the following: You close a property dialog box. You start BizTalk Orchestration Designer. You create a page. |
| 27386 | This article provides information about the Microsoft Baseline Security Analyzer tool (MBSA). This tool centrally scans Windows-based computers for common security misconfigurations and generates individual security reports for each computer that it... |
| 27387 | BizTalk Server Messaging Manager allows users to choose SMIME (Secure Multipurpose Internet Mail Extensions) encryption when they are creating a port. However, the user cannot adjust the SMIME encryption parameters needed to change the encryption... |
| 27388 | When you use an XSLT map with BizTalk Server 2000, the output data may contain empty records or fields. This can cause validation against the destination schema to fail. |
| 27389 | When BizTalk Server 2000 experiences a low memory or out of memory condition, it does not stop trying to process incoming documents, even though out of memory errors are logged in the event log. When this occurs, the documents are not processed, but... |
| 27390 | The BizTalk Messaging Manager design time application allows users to create ports and channels that describe how to process business documents. Ports and channels have properties that allow users to select certificates for the purpose of encrypting... |
| 27391 | The following error message may appear in the Application Event Log upon submitting XML data to BizTalk Server 2000: An error occurred in BizTalk Server. Details: The XML document has failed validation for the following reason: Error parsing '0.00' as... |
| 27392 | When you install BizTalk Server 2000, if a user chooses to cancel the setup process while the database setup wizard is running, an internal error message dialog displays. |
| 27393 | Under heavy loads, documents in the Work Queue are marked as in-process . When many documents are moved at the same time, documents are left in the Work Queue and marked as in-process instead of being moved to the Suspended Queue. There is no data... |
| 27394 | This article describes the functionality of the Expect Receipt and Generate Receipt properties on the Source Organization page of the Channel Wizard. |
| 27395 | In BizTalk Server 2000, users can set the times to perform final processing for documents that are destined for a specific port. This time interval is known as a Service Window. When BizTalk Server processes the data according to the Service Window,... |
| 27396 | When you are using BizTalk Messaging Manager remotely to access the advanced properties of a channel, you may receive the following error message: BizTalk Messaging Manager Error Unable to display configuration properties. Error 0x1FB: An exception... |
| 27397 | When you move your mouse pointer over a functoid in the BizTalk Mapper grid area, tool tips are not displayed. |
| 27398 | When you use an XLANG Scheduler that uses custom COM+ components and transactions, the Event Viewer may log one or more of the following events: Event ID: 12322 Event Source: XLANG Scheduler Event Description: The state of the schedule instance could... |
| 27399 | When you submit a flat file to BizTalk for processing, the message ends up in the Suspended Queue with an Error Description of Parsing Failure. When this occurs, one of the following error messages may be logged into the Application event log: Event... |
| 27400 | When you use the IInterchange interface SubmitSync method, you may receive the following error message: An error occurred in BizTalk Server. Details: The synchronous submission could not be completed because the channel matched a distribution list... |
| 27401 | If you enable tracking for an element or attribute as Integer data type on a BizTalk Server with a system locale that uses a non-period as the decimal point delimiter (for example, Korean), you may receive the following error in the BizTalk Server's... |
| 27402 | This article describes the methods used by BizTalk Server 2000 to determine the timeout values for database connection and command objects. |
| 27403 | When you use the BizTalk Configuration Object Model to retrieve an instance of a BizTalk.BizTalkConfig Management object, you may receive the following error code: BTS_E_NOOBJECT 0x1202 The object was not found. This error can occur even if you are... |
| 27404 | When a COM component is registered, and the Visual Basic source code of the component is being executed for debugging purposes, if you use the BizTalk Orchestration Designer to bind the component to a port, it may not appear in the list of components... |
| 27405 | When you attempt to shut down or start the XLANG Scheduler COM+ application, you may receive the following error message: Catalog Error You do not have permission to perform the requested action. If security is enabled on the System application of the... |
| 27406 | When you attempt to drag an Orchestration Drawing (*.skv) into an open window in the BizTalk Orchestration Designer, you may receive the following error message: BizTalk Orchestration Designer Insertion of OLE objects is not supported. |
| 27407 | When you modify a rule in a decision shape, the same rule in a different shape may also be modified without notification of the change. This can have adverse affects on your Orchestration Drawing. |
| 27408 | When you create or edit drawing in the BizTalk Orchestration Designer, you cannot copy or cut implementation shapes or ports. |
| 27409 | When you view the XLANG Scheduler COM+ Component properties through a Terminal Service Client session, the XLANG tab may be missing. |
| 27410 | When a child schedule completes, it does not receive a ScheduleDone event until its parent schedule has completed. |
| 27411 | The ALT + ENTER key combination does not display the properties for shapes in the BizTalk Orchestration Designer. |
| 27412 | When you use the BizTalk Orchestration Designer, if the application fails while you are creating a drawing, the changes are not saved automatically and are lost. |
| 27413 | When you compile a drawing in BizTalk Orchestration Designer, the estimated percent that is complete may jump from a very low percentage to Done. |
| 27414 | When you search for text in a BizTalk Orchestration drawing that does not exist, the following error message may occur: Visio has finished searching the page. |
| 27415 | When you delete a transaction shape from your BizTalk Orchestration drawing, all of the shapes that are contained in that transaction are also deleted. |
| 27416 | When you try to run a dynamic report in Commerce Server, you may experience memory errors or blank dynamic reports. |
| 27417 | You may experience one or both of the following problems: When you create a new application in Microsoft Application Center, if you click BizTalk resources , and then click Add , a list of high-level objects, such as BiztalkCustomCounters ,... |
| 27418 | When you try to put certain Unicode characters in your IBM MQSeries server by using the Microsoft BizTalk Adapter for MQSeries version 1.0, some of the characters are not converted correctly into ASCII. For example, a Unicode 0x85 (NEwLine) character... |
| 27419 | This step-by-step article describes how to create a simple preprocessor for BizTalk Server by using Visual Basic .NET. Create the Interop DLLs NOTE : In the following steps, you will run several commands from the Microsoft Visual Studio .NET command... |
| 27420 | This article details the steps that are required to create a BizTalk Server Application Integration Component (AIC) to parse XML data into a Microsoft SQL Server 2000 table. |
| 27421 | When you start Microsoft BizTalk Server Document Tracking, an error message box appears that is named VBScript: BizTalk Document Tracking Error . This error message box contains no text. It contains a warning icon and an OK button. When you click OK ,... |
| 27422 | When Microsoft BizTalk Server 2002 SP1 Setup has completed, you receive an error message that states that one of the post-install steps was not completed. When this problem occurs, you receive an error message that is similar to the following in the... |
| 27423 | During serialization, if an incoming field contains a null value, the output document may not contain the field. This was originally by design, but this behavior will change when you install Microsoft BizTalk Server 2002 Service Pack 1 (SP1) . You can... |
| 27424 | When BizTalk Server sends documents through the HTTP/HTTPS transport to an ASP page that is located on a Microsoft Internet Information Services (IIS) server, document delivery fails and the documents are placed in the suspended queue of the sending... |
| 27425 | When a user or process attempts to start an XLANG schedule from a remote Microsoft Terminal Server connection, BizTalk Server may return an error. The error message that is returned varies depending on how the user or process attempts to start the... |
| 27426 | When you try to use the Microsoft BizTalk Document Tracking interface, you may receive the following error message: VBScript: BizTalk Document Tracking This page is entered with invalid parameters When you click OK , you may receive the following... |
| 27427 | After you create a new trading partner relationship by using the Trading Partner Manager (TPM) in Microsoft BizTalk Accelerator for HIPAA 2.0, the interchange control version number of the envelope properties may not be populated with the correct... |
| 27428 | If you follow the instructions in the Microsoft BizTalk Server 2002 SP1 Readme.htm file to register the CDO System Library (Cdosys.dll), you may receive the following error message: DllRegisterServer in cdosys.dll failed. Return code was: 0x800704da... |
| 27429 | If Microsoft BizTalk Server 2002 loses its connection to the BizTalk Messaging Management database, BizTalk Server may put the interchanges that it is processing in the Suspended queue with a status of Channel Missing or Channel Removed. This... |
| 27430 | Microsoft distributes bug fixes in service packs. Service packs help keep a product current, and extend and update the functionality of your computer. Service packs include updates, and may include system administration tools, drivers, and additional... |
| 27431 | After a connection interruption between the computer that is running BizTalk Server and the computer that is running Microsoft SQL Server, you may receive the following error message when you call IInterchange::Submit() or IInterchange::SubmitSync() :... |
| 27432 | Each interchange in Microsoft BizTalk Server has its own transaction. A BizTalk Application Integration Component (AIC) can participate in this transaction through COM+ Service. When the AIC experiences an error, you can do one of the following:... |
| 27433 | A resource starvation issue may occur when you running multiple XLANG schedule instances that fail with a 0x8004e007 error. This problem may cause the database connection to be orphaned. XLANG uses Microsoft ActiveX Data Objects (ADO) for database... |
| 27434 | When you call the ADO Stream LoadFromFile method from a custom Microsoft BizTalk preprocessor to open the file that is provided in the vDataIn variable, you receive a cannot open file error message that states that the file is in use by another... |
| 27435 | When you install a hotfix on your computer that is running Microsoft BizTalk Server after you upgrade from BizTalk Server version 2000 to version 2002, you may receive the following error message: Server: Msg 1781, Level 16, State 1, Line 3 Column... |
| 27436 | The Work queue, Scheduled queue, Retry queue, and Suspended queue in the BizTalk Server Administration Microsoft Management Console (MMC) may show an incorrect number of items. For example, the Suspended queue should show the number of records in the... |
| 27437 | Microsoft BizTalk Accelerator for HIPAA version 1.0 may serialize some fields of your document when these fields do not exist in the inbound document. Also, the value for these incorrectly serialized fields is set to 0 . |
| 27438 | If you set up a BizTalk server as a receive-only server, and the computer that is running Microsoft SQL Server for the BizTalk server fails, the receive functions of BizTalk server may stop responding even after you restart the computer that is... |
| 27439 | When you view document specifications with the Microsoft BizTalk Server Editor New Document Specification dialog box, you may not be able to view all of the specifications that are available in a folder. |
| 27440 | When you try to test a map in the BizTalk Mapper by using a generated XML instance, you may receive the following error message: The XSL transformation that uses the test-instance document for the source specification failed. Reason: Microsoft... |
| 27441 | When you use Microsoft BizTalk Server 2002, the DateTime string that is returned when it is added to a messaging post (%datetime%) as part of the file name is not displayed in the same format as in BizTalk Server 2000. |
| 27442 | Microsoft BizTalk Server Reliable Messaging is a feature of the BizTalk Framework 2.0 protocol that supports guaranteed, one-time-only delivery of documents in heterogeneous environments across the Internet. In accordance with the BizTalk Framework... |
| 27443 | You can upgrade BizTalk Server to the latest version without uninstalling the previous version of BizTalk Server. To do so, use the following guidelines: Back up the BizTalk Server databases as a precautionary measure. In a default Microsoft BizTalk... |
| 27444 | During the BizTalk Server 2000 Service Pack 2 (SP2) installation, a dialog box with the following text is displayed: The feature you are trying to use is on a CD-ROM or other removable disk that is not available. Insert the 'Microsoft BizTalk Server... |
| 27445 | When you install BizTalk Server 2000, you may receive errors messages that are similar to the following: Error 1904. Module C:\Program Files\Microsoft BizTalk Server\INTERCHANGEPROV.dll failed to register. HRESULT = -2147024770. Error 1904.Module... |
| 27446 | One or more of the BizTalk Server Microsoft Message Queuing (MSMQ) receive functions may be disabled and the following error message may occur in the BizTalk Server Application log: Event Type: Error Event Source: BizTalk Server Event Category:... |
| 27447 | In the Microsoft BizTalk Server tutorial, PORequestApproval.wsc contains the following statement which expects an English date/time format: Line 47:BR/ 'Generate a Unique Number used to generate unique files using a maskBR/ strTimeNow =... |
| 27448 | If you try to start the ODBC Data Source Administrator for more than one XLANG Schedule host simultaneously from the same Microsoft Management Console (MMC) interface, the COM+ Explorer experiences a deadlock condition and it stops responding. |
| 27449 | If you leave a few drawings open in BizTalk Orchestration Designer, close Orchestration Designer, and try to start Orchestration Designer again immediately, you may receive the following error message: Microsoft Visio has encountered a problem and... |
| 27450 | When you are attempting to compile a BizTalk Orchestration Schedule, you may receive either of the following two messages: Just-In-Time Debugging Would you like to debug using the selected debugger? -or- Microsoft Development Environment An exception... |
| 27451 | In BizTalk Orchestration Designer, if you click Print on the File menu when no printer is installed, Orchestration Designer closes, and then you receive the following error message: Microsoft Visio has encountered a problem and needs to close. We are... |
| 27452 | If an XLANG schedule instance is suspended while it is waiting to receive a document from a Microsoft Message Queuing (MSMQ) message queue, it may block other running schedule instances from receiving messages from the same message queue. The XLANG... |
| 27453 | When you install Microsoft BizTalk Server, you may receive the follow error messages: Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or... |
| 27454 | If you set up a BizTalk server as a receive-only server, and the Microsoft SQL Server computer for the BizTalk server fails, the receive functions of BizTalk server may stop responding even after you restart the SQL server. |
| 27455 | If a BizTalk Server receive function preprocessor is written in Microsoft Visual Basic, when you use this receive function preproprocessor to process binary data, BizTalk Server truncates the SAFEARRAY output that is returned by one byte. This data... |
| 27456 | When you run the ThirdPartyApp.exe program, which is located in the Microsoft BizTalk Server\SDK\XLANG Samples\Integrating BizTalk Services\BTF Correlation\ThirdPartyApp folder, the following error message occurs if you click Reflect before you click... |
| 27457 | In the BizTalk Server 2000 Orchestration Designer, the text in the Constants and in the Messages objects may wrap incorrectly in the borders of the objects. NOTE : This problem only seems to occur in localized non-English versions of Microsoft BizTalk... |
| 27458 | When you try to duplicate a while shape with the French version of the BizTalk Server 2000 Orchestration Designer on a computer that has the French version of Microsoft Visio 2002 installed, the following error may occur: Probleme dans... |
| 27459 | When you try to duplicate a decision shape with the French version of the BizTalk Server 2000 Orchestration Designer on a computer that has the French version of Microsoft Visio 2002 installed, the following error message may occur: Probleme dans... |
| 27460 | When you try to add a constant to the data page of BizTalk Server 2000 Orchestration Designer on a computer that has the German version of Microsoft Visio 2002 installed, the following error may occur: Problem bei... |
| 27461 | When you run UndoCleanQueuesPatch.sql in Microsoft SQL Server Query Analyzer to uninstall the CleanQueues stored procedure patch, the following errors may occur: Server: Msg 111, Level 15, State 1, Line 5 'CREATE PROCEDURE' must be the first statement... |
| 27462 | When you use Microsoft Application Center to deploy BizTalk Server channels and ports that use certificates, the deployment fails if the certificates are not installed on the destination BizTalk Server computer prior to the Application Center... |
| 27463 | When you attempt to connect BizTalk Server to a clustered Microsoft SQL Server computer, the BizTalk Server Setup program and the BizTalk Messaging Service fail, and the following error message occurs: CIS_E_ADMIN_DBCONNECT - BizTalk Server failed to... |
| 27464 | The Microsoft BizTalk Server 2000 EDIFACT parser cannot convert DBCS characters correctly. If the BizTalk Server EDIFACT parser parses an EDIFACT document that contains DBCS characters, these characters translate as garbage characters. |
| 27465 | After you install the Microsoft XML 4.0 Beta on a computer running BizTalk Server 2000, the following behavior may occur in the BizTalk Editor or BizTalk Mapper: If you install the MSXML 4.0 Beta in replace mode, the BizTalk Editor and BizTalk Mapper... |
| 27466 | When you view the XML Representation window from the BTConfigAssistant SDK sample, and choose to save the data from the XML tab, it may save it as Microsoft Visual Basic Script data instead of XML data. |
| 27467 | You may experience lost messages in your BizTalk Server application when Microsoft SQL Server shuts down gracefully. |
| 27468 | When you submit a document for processing by Microsoft BizTalk Server, the document may not move out of the Work Items queue, and the following informational messages may appear in the Application log of the BizTalk Server: Event Type: Information... |
| 27469 | This article briefly describes the impact of using a Microsoft Visual Basic 6.0 component in the BizTalk Configuration Object Model, more specifically, the use of a Microsoft Visual Basic 6.0 component as an Application Integration Component (AIC).... |
| 27470 | The BizTalk Software Development Kit (SDK) XLANG Monitor sample (XLANGMon.exe) does not display any events for monitored schedules until you start a second instance of the XLANG Monitor. XLANG Monitor is located in the \Program Files\Microsoft BizTalk... |
| 27471 | When you try to open the CreditChecker Visual Basic sample that is included in BizTalk Server 2000, you may receive the following error: Disk is not ready: 'f:\programs\microsoft biztalk... |
| 27472 | When you use X12 documents with Microsoft BizTalk Server that use either Real (R) or Number (N) data types, your documents may fail data validation. The reason provided for validation failure may be similar to the following error message: Length is... |
| 27473 | When you use a custom Messaging Port encoding component with Microsoft BizTalk Server, you may notice that documents are both transmitted and sent to the Suspended Queue. Note This problem only occurs when you use non-transactional transports, such... |
| 27474 | Several SDK samples included with BizTalk Server 2000 contain syntax errors. The files can be modified manually to correct the problems. The following files in the Program Files\Microsoft BizTalk Server\SDK\Messaging Samples directory have a specific... |
| 27475 | When you change the computer name on a computer running BizTalk Server 2000, and you restart (reboot) the computer, error messages may occur. When you attempt to manually start the BizTalk Service in the Microsoft Management Console (MMC), the... |
| 27476 | When you are using Orchestration Designer to edit a script component binding in an existing Orchestration Schedule, you may receive one or both of the following error messages: Microsoft VBScript compilation error - path to file [25,3] Expected... |
| 27477 | When you configure a channel, you can select a client certificate to use for a HTTPS transport in the Advanced Configuration dialog box. The certificate should have Client Authentication as its intended purpose. Both Microsoft Client Authentication... |
| 27478 | When you attempt to delete a BizTalk Server from the BizTalk Server Group in the BizTalk Server Administration Microsoft Management Console (MMC) snap-in, you may receive the following error message: The server cannot be deleted because of a failure... |
| 27479 | If you submit a document to BizTalk Server for processing by using a BizTalk Messaging port with a primary transport of Microsoft Message Queue Services (MSMQ), the following error may occur in the Application log: Event Type: Error Event Source:... |
| 27480 | When you use a Microsoft Message Queue Server (MSMQ) receive function to receive data from a well-known queue, the following error message may occur: Event ID: 324 Source: BizTalk Server Category: Document Processing Description: An error occurred in... |
| 27481 | When you try to search for existing objects or to create new objects in the Microsoft BizTalk Messaging Manager, you may receive the following error message: The response document is not a valid document. This could be due to an invalid BizTalk Server... |
| 27482 | Your Microsoft BizTalk Server may send documents to the Suspended Queue without a matching entry in the Event Viewer. The error description for the document instance in the Suspended Queue is similar to the following: The document extracted from the... |
| 27483 | When you import a Microsoft BizTalk Framework 2.0-compliant schema into the BizTalk Editor, you may receive the following error messages: Generating warnings for Renamed Nodes and Specification Validation... Warning: The Order attribute of the... |
| 27484 | When you use a BizTalk Framework (BTF) 2.0 envelope with Microsoft BizTalk Server 2000, the sentAt and expiresAt tags use Greenwich Mean Time (GMT) time instead of local time. For example: prop:sentAt2000-10-09T08:00:23+00:00/prop:sentAt... |
| 27485 | If you install Microsoft BizTalk Server 2002, and then you select the option to join an existing BizTalk Server group that is running Microsoft BizTalk Server 2002 Service Pack 1 (SP1), the database setup does not succeed. When this behavior occurs,... |
| 27486 | The list below contains any articles that describe issues that may occur if you install Microsoft BizTalk Server 2002 Service Pack 1 (SP1): 825886 Data Loss May Occur When You Submit Signed or Encrypted Documents to BizTalk Server 2002 SP1 825886 Data... |
| 27487 | If a Microsoft BizTalk Server XLANG schedule receives a message, and then experiences an error condition and fails, you may notice that the message queue that it received the message from has been deleted and that the message no longer exists. |
| 27488 | When you generate an 0A1 Partner Interface Process (PIP) by using the Microsoft BizTalk Server Accelerator for RosettaNet version 2.0, the toRole element and the fromRole element are reversed. |
| 27490 | When you try to start the Japanese version of the BizTalk Editor, the BizTalk Mapper, or the BizTalk Orchestration Designer, the following error message is displayed: Thank you for evaluating Microsoft BizTalk Server 2000. The period for this... |
| 27491 | After a BizTalk Server cluster failover, sometimes the temporary private Microsoft Message Queuing queues that the XLANG Scheduler creates are not automatically deleted from the previously active node. |
| 27492 | The BizTalk Orchestration Designer may take an unusually long time to start. This problem occurs if Orchestration Designer is running on Microsoft Visio 2002. |
| 27493 | If you bind an XLANG port to a Microsoft Visual Basic COM component and you select the No instantiation option, the resulting compiled schedule may stop responding or hang when you run it, particularly if the schedule is dehydrated. |
| 27494 | When you attempt to import a Messaging Manager configuration by using the Microsoft BizTalk Server 2000 SDK sample BizTalkConfigAssistant, no configuration is imported. |
| 27495 | Several Microsoft Visual C++ sample projects in the \Microsoft BizTalk Server\SDK folder will not compile without generating errors. See the More Information section of this article for specific projects and error messages. |
| 27496 | You cannot use your keyboard to access or manipulate flowchart shapes when you use Microsoft BizTalk Server 2000 Orchestration Designer. |
| 27497 | The Orchestration Designer may generate the following error message when you use different functions in the Orchestration Designer: Microsoft Visual Basic Run-time Error '-2147417848 (0x80010108)': Method 'RequestFromVisio' of object '_Application'... |
| 27498 | When you use a localized version of Microsoft BizTalk Server, you may experience a corrupt display in the Orchestration Designer. For example, text strings are wrapped differently within the flowchart shapes than when the drawing was saved. |
| 27499 | In localized versions of the BizTalk Editor, the Microsoft Corporation hyperlink in the About BizTalk Editor dialog box links to an unlocalized Web site. |
| 27500 | Many organizations need to automate the installation process for BizTalk Server. This article provides a simple batch file that demonstrates how to use the silent installation features in Microsoft Installer. The BTSSilentInstall.exe file that is... |
| 27501 | When you run the PublicInterfaces sample, Sked.vbs, you may receive the following error: /remote server name path to sked.vbs(156, 5) Microsoft VBScript runtime error: The remote server machine does not exist or is unavailable |
| 27502 | At the BizTalk Server Setup Configure BizTalk Orchestration database screen, after you input your SQL server information and select Select an existing database , you may receive the following error message: [Microsoft][ODBC SQL Server Driver][SQL... |
| 27503 | When you invoke the Invalid Character Ranges dialog box for non-XML document specifications that are loaded into the Microsoft BizTalk Editor (from the View menu, click Invalid Character Map ), you cannot add, edit, or delete character ranges. When... |
| 27504 | When you are using the PublicInterfaces sample that is supplied with BizTalk Server 2000, you may receive the following error message: remote computer name XLANG Scheduler path to sked.vbs (157, 9) Microsoft VBScript runtime error: Invalid... |
| 27505 | The Readme file for the Credit Check sample application that is included with Microsoft BizTalk Server 2000 incorrectly states that it uses two credit checking methods. |
| 27506 | If you try to install Microsoft BizTalk Server on a domain controller, Setup fails and an error message that is similar to the following may appear: Product: Microsoft BizTalk Server 2002 -- Error 1722. There is a problem with this Windows Installer... |
| 27507 | You can use Microsoft BizTalk Server Orchestration Designer to implement schedule ports by using Microsoft Windows Scripting Component (.wsc) components. This article describes how to step through the .wsc script code in a debugger after an XLANG... |
| 27508 | After you upgrade your Microsoft BizTalk Server computer to Microsoft Windows 2000 Service Pack 3, you may receive the following error message in BizTalk Server when you process multi-part MIME files: An error occurred in BizTalk Server. Details:... |
| 27509 | The Microsoft SQL Server computer that hosts the Microsoft BizTalk Server XLANG database may generate Unspecified Error and Timeout errors. Additionally, error messages that are similar to the following are generated in the BizTalk Server... |
| 27510 | When you try to run any of the tools in Microsoft BizTalk Server 2000 or BizTalk Server 2002 (such as Editor, Mapper, or Orchestration Designer), you receive the following error message: Thank you for evaluating Microsoft BizTalk Server 2000/2002. The... |
| 27511 | To run the Microsoft BizTalk Accelerator for RosettaNet version 2.0 on Microsoft Windows XP, you must install a Windows XP pre-Service Pack 1 fix. |
| 27512 | If you install Microsoft BizTalk Server 2000 on a stand-alone computer and the Microsoft SQL Server databases are running on a Windows Clustering-based cluster, Setup fails during the database setup portion and the following error message is... |
| 27513 | The Microsoft BizTalk Server 2000 online documentation may not be displayed properly if Microsoft Internet Explorer 6.0 is installed on the same computer. When you select a topic from the left pane of the online documentation, the article may not be... |
| 27514 | When you use the Japanese version of Microsoft BizTalk Server, the SDK sample ReceiveFunction.vbs may fail with an error that is similar to the following: Existing Receive Functions: C:\Program Files\Microsoft BizTalk Server\SDK\Messaging... |
| 27515 | If you compile the Microsoft Visual Basic version of the SDK sample DistributionList (located in Program Files\Microsoft BizTalk Server\SDK\Messaging Samples\DistributionList\DistributionList.bas) into an EXE and run it, the program stops executing... |
| 27516 | When you use some of the samples that ship with Microsoft BizTalk Server on a non-English (localized) version of BizTalk Server, you may encounter one or more of the following errors: In the Microsoft Visual Basic version of the BTSAppIntegration... |
| 27517 | When you uninstall BizTalk Server 2000, Microsoft recommends that you manually delete the Program files\Microsoft BizTalk Server directory (folder) before you reinstall BizTalk Server. |
| 27518 | You can use Microsoft BizTalk Server Orchestration Designer to implement schedule ports by using Microsoft Windows Scripting Component (.wsc) components. However, if you start an XLANG schedule that calls a .wsc file that uses the Microsoft Visual... |
| 27519 | A default installation of Microsoft BizTalk Server 2000 or Microsoft BizTalk Server 2002 creates several Microsoft Internet Information Services (IIS) virtual directories. These virtual directories add functionality to some BizTalk Server tools that... |
| 27520 | When you are using the Microsoft BizTalk Editor or the Microsoft BizTalk Mapper to access a WebDAV repository on a Microsoft Internet Information Services (IIS) server that is running on a port other than the default TCP port 80, you may receive an... |
| 27521 | The XLANG file data source name (DSN), which BizTalk Orchestration uses to connect to the XLANG database, uses Microsoft Windows security by default. This article describes how to modify the XLANG DSN to use SQL security. IMPORTANT : This modification... |
| 27522 | If you attempt to search for Messaging Manager objects in the BizTalk Server Messaging Manager, the following error may occur when you click the Search Now button: BizTalk Messaging Manager Error Microsoft XML Parser V2.6, is not registered on this... |
| 27523 | Microsoft has released a patch to correct two vulnerabilities in Microsoft BizTalk Server 2002 and one vulnerability in Microsoft BizTalk Server 2000. This patch is included in Microsoft Biztalk Server 2002 Service Pack 1 (SP1). about the latest... |
| 27524 | If you attempt to open the Microsoft BizTalk Server 2000 Readme.txt files that are stored in a Microsoft Word format (with a .doc extension), you may get the following error message if Microsoft Word is not installed: Microsoft Word 97 Conversion... |
| 27525 | If you try to connect to a Microsoft BizTalk document tracking database with the Document Tracking user interface from a client computer that is not running Microsoft BizTalk Server or Microsoft SQL Server, you may receive the following error message:... |
| 27526 | When you install Microsoft SQL Server 2000 on a Microsoft Windows 2000 clustered computer that already has BizTalk Server 2000 installed, you may receive the following error: Microsoft Visual C++ Debug Library Debug Assertion Failed! Program:... |
| 27527 | If you uninstall any Microsoft BizTalk Server 2000 service packs, Microsoft BizTalk Server 2000 Setup reverts any installed Microsoft XML (MSXML) 3.0 service packs back to the original installation bits for Microsoft XML 3.0. |
| 27528 | After you install the Microsoft BizTalk Server pre-SP1 Rollup Hotfix from the following Microsoft Knowledge Base article, BizTalk Server may experience degraded performance when you are processing documents: 293789 Availability of Microsoft... |
| 27529 | This article describes the steps to configure Commerce Server 2000 sites to submit purchase orders through BizTalk Server 2000. NOTE : The information in this article is for users who have BizTalk Server and Commerce Server 2000 installed on the same... |
| 27530 | The More Information section of this article describes the steps to configure Commerce Server 2000 sites to send and receive catalogs through BizTalk Server 2000. Note that the information in this article is for users who have BizTalk Server and... |
| 27531 | This article describes the following two newly reported vulnerabilities in Microsoft BizTalk Server 2002: BizTalk Server 2002 allows documents to be exchanged by using the HTTP format. A buffer overrun exists in the component that is used to receive... |
| 27532 | After you install Microsoft Visio 2002 on your BizTalk 2000 server, if you try to start the BizTalk Orchestration Designer, you may receive one or more dialog boxes that prompt you to enable or disable macros. If you opt to enable macros, a series of... |
| 27533 | The Microsoft BizTalk Server Pre Service Pack 1 (SP1) Rollup Fix corrects the problems that are described in the following Microsoft Knowledge Base articles: 281470 BizTalk Server Appends Random Characters to Flat File Output 281470 BizTalk... |
| 27534 | If document processing stops, the following event may be logged to the event log: Source: BizTalk Server Category: Document Processing Event ID: 324 Description: An error occurred in BizTalk Server. Details: ------------------------------ The server... |
| 27535 | Session Summary Wednesday, October 22, 2003: 10:00 AM Pacific time (Greenwich mean time - 7 hours) Microsoft BizTalk Server 2004 connects systems, people, and trading partners through manageable business processes. This Support WebCast session will... |
| 27536 | When you double-click the Xlang.hlp file, which is found in the Program Files\Microsoft BizTalk Server\Docs folder, you encounter a blank Help window with no functionality. |
| 27537 | If you try to install Microsoft BizTalk Server on a domain controller, Setup fails and an error message that is similar to the following may appear: Product: Microsoft BizTalk Server 2002 -- Error 1722. There is a problem with this Windows Installer... |
| 27538 | When you try to use the Microsoft BizTalk Document Tracking interface, you may receive the following error message: VBScript: BizTalk Document Tracking This page is entered with invalid parameters When you click OK , you may receive the following... |
| 27539 | You can use Microsoft BizTalk Server Orchestration Designer to implement schedule ports by using Microsoft Windows Scripting Component (.wsc) components. This article describes how to step through the .wsc script code in a debugger after an XLANG... |
| 27540 | You can use Microsoft BizTalk Server Orchestration Designer to implement schedule ports by using Microsoft Windows Scripting Component (.wsc) components. However, if you start an XLANG schedule that calls a .wsc file that uses the Microsoft Visual... |
| 27541 | When you start Microsoft BizTalk Server Document Tracking, an error message box appears that is named VBScript: BizTalk Document Tracking Error . This error message box contains no text. It contains a warning icon and an OK button. When you click OK ,... |
| 27542 | If you install Microsoft BizTalk Server 2002, and then you select the option to join an existing BizTalk Server group that is running Microsoft BizTalk Server 2002 Service Pack 1 (SP1), the database setup does not succeed. When this behavior occurs,... |
| 27543 | If a Microsoft BizTalk Server XLANG schedule receives a message, and then experiences an error condition and fails, you may notice that the message queue that it received the message from has been deleted and that the message no longer exists. |
| 27544 | When you generate an 0A1 Partner Interface Process (PIP) by using the Microsoft BizTalk Server Accelerator for RosettaNet version 2.0, the toRole element and the fromRole element are reversed. |
| 27545 | If Microsoft BizTalk Server 2002 loses its connection to the BizTalk Messaging Management database, BizTalk Server may put the interchanges that it is processing in the Suspended queue with a status of Channel Missing or Channel Removed. This... |
| 27546 | When Microsoft BizTalk Server 2002 SP1 Setup has completed, you receive an error message that states that one of the post-install steps was not completed. When this problem occurs, you receive an error message that is similar to the following in the... |
| 27547 | If you follow the instructions in the Microsoft BizTalk Server 2002 SP1 Readme.htm file to register the CDO System Library (Cdosys.dll), you may receive the following error message: DllRegisterServer in cdosys.dll failed. Return code was: 0x800704da... |
| 27548 | A resource starvation issue may occur when you running multiple XLANG schedule instances that fail with a 0x8004e007 error. This problem may cause the database connection to be orphaned. XLANG uses Microsoft ActiveX Data Objects (ADO) for database... |
| 27549 | Session Summary Wednesday, October 22, 2003: 10:00 AM Pacific time (Greenwich mean time - 7 hours) Microsoft BizTalk Server 2004 connects systems, people, and trading partners through manageable business processes. This Support WebCast session will... |
| 27550 | This article describes a backup transport and how it is used with BizTalk Server Messaging Services. |
| 27551 | This article contains information from the BizTalk Server 2000 Readme.htm |
| 27552 | The BizTalk Mapper creates a blank attribute in an element of the output document when there is a link created from an optional field in the source schema to a destination field. This occur even if the incoming document does not contain that optional... |
| 27553 | When you use the XLANG Event monitor to monitor an XLANG schedule that has a port or action name with double-byte characters, the XLANG event history may return garbage characters in some of the event fields such as SourceEnter, SourceLeave, and... |
| 27554 | Some organizations may have a need to translate an inbound flat file source document into an XML destination document. This article uses the same document specification for both the inbound and the outbound documents, and therefore does not require a... |
| 27555 | If you have configured the BizTalk Server Messaging service to start under a different user or start manually instead of automatically, these configurations are lost when you install BizTalk Server 2000 SP1. This can cause problems when the configured... |
| 27556 | In the BizTalk Server 2000 Orchestration Designer, if you click Print on the File menu or the Print button on the tool bar when there is no printer installed, the following error occurs and the BizTalk Server 2000 Orchestration Designer shuts down:... |
| 27557 | When you browse the Application Integration Component (AIC) transports that are available, the BizTalk Messaging Manager may generate a server timeout or return the following error message when it attempts to bind a Port to a Primary Transport of... |
| 27558 | When you use the SubmitSync () method of the IInterchange interface, you may notice that even though you have the channel configured to retry document delivery, if an error occurs, the document is immediately placed into the Suspended Queue. |
| 27559 | When you create an XSL map in the BizTalk Mapper, you can add functoids without linking them to anything. These unused functoids are saved as part of the XSL map, even though they appear to be unused. This behavior is by design. |
| 27560 | Many locales use a decimal separator other than a period (.). For example, five and three quarters may be represented as 5,75 . When you attempt to use this format in BizTalk Server 2000, a document validation error may occur. |
| 27561 | The BizTalk Orchestration Designer is a design-time tool that allows users to diagram and implement business processes. The business process typically includes the handling of business documents, and the business documents can include XML or non-XML... |
| 27562 | When you use the BizTalk Server 2000 Orchestration Designer to bind a COM object to a schedule, the Orchestration Designer may stop responding (hang) when the binding wizard completes. NOTE : This problem only seems to occur with the French versions... |
| 27563 | An error message may occur when a user attempts to send data to a partner. If the partner requires that the data be encrypted with a certificate, the following error message occurs: An error occurred in BizTalk Server. Details:... |
| 27564 | After you install BizTalk Server 2000 Service Pack 1 (SP1), X12 documents fail validation. |
| 27565 | This article describes how to locate Microsoft product information and how to make purchases online. |
| 27566 | Microsoft distributes bug fixes in service packs. Service packs help keep a product current, and extend and update the functionality of your computer. Service packs include updates, and may include system administration tools, drivers, and additional... |
| 27567 | When you send BizTalk messages with the HTTP transport protocol and an envelope type of either Reliable or Custom XML , the SOAPAction header value in the HTTP header that is sent with the document may not be enclosed in quotation marks. |
| 27568 | When you use the Simple Mail Transfer Protocol (SMTP) to transmit a document to an Open Destination messaging port in BizTalk Server, the subject of the resultant e-mail message is the Interchange tracking ID and cannot be modified. |
| 27569 | When you exchange binary data by using a custom C# preprocessor or postprocessor with the BizTalk Adapter for MQSeries, you may notice that your custom processor does not manage the data correctly. |
| 27570 | BizTalk Messaging may generate an output document that contains unreadable, garbage characters from a MIME-encoded input document, which contains attachments with Japanese double-byte character set (DBCS) characters. |
| 27571 | When you create a BizTalk messaging port to an XLANG application, the option for data encryption is disabled. |
| 27572 | When you attempt to set the date format in the Custom Date/Time Format property in the BizTalk Editor, you cannot use a period (.) as a date separator. |
| 27573 | You cannot perform the following actions in the BizTalk Mapper without a mouse: Create, delete, or redirect a link. View link properties. Drag a functoid from the Functoid Palette window to the mapping grid. Move or delete a functoid in the mapping... |
| 27574 | A correlational message is a message that uses the instance ID of a running XLANG schedule instance as its message label. This article discusses a problem that occurs in the following scenario: You have several XLANG schedule instances in the... |
| 27575 | In a high volume message system, the BizTalk Server Accelerator for RosettaNet may intermittently fail to process RosettaNet messages. When this problem occurs, you may receive the following error message in the log: An error occurred in BizTalk... |
| 27576 | BizTalk Server 2002 cannot decrypt a message and the following error appears in the Event Log: An error occurred in BizTalk Server. Details: ------------------------------ [0x00000000] Security: Error occurred [0x80091001] An error occurred while... |
| 27577 | The list below contains any articles that describe issues that may occur if you install Microsoft BizTalk Server 2002 Service Pack 1 (SP1): 825886 Data Loss May Occur When You Submit Signed or Encrypted Documents to BizTalk Server 2002 SP1 825886 Data... |
| 27578 | This article gives reference information for some of the security-related issues that BizTalk Server 2002 Service Pack 1 ( SP1) addresses. |
| 27579 | When you submit a document to Microsoft BizTalk Server 2002 Service Pack 1 (SP1) the document fails delivery and an entry for the document is created in the suspended queue that contains the following line of text: This document is at following... |
| 27580 | A default installation of Microsoft BizTalk Server 2000 or Microsoft BizTalk Server 2002 creates several Microsoft Internet Information Services (IIS) virtual directories. These virtual directories add functionality to some BizTalk Server tools that... |
| 27581 | When BizTalk Server 2002 communicates with an HTTP Web server by using HTTP/1.1, the HTTP Web server may gracefully close a TCP connection and BizTalk Server may stop responding. The following unspecified error message is logged in the application... |
| 27582 | When you use the BizTalk Messaging Manager to create a new port with a port name that already exists, you are prompted with the following error message when you complete the wizard: The messaging port could not be saved. Error 0xC0C01244: The... |
| 27583 | During the BizTalk Messaging Management Database portion of BizTalk Server Setup, you may receive the following error message: An error occurred while attempting to create the BizTalk Messaging Management database. The specified SQL server might not... |
| 27584 | When you receive a secure e-mail message from BizTalk Server 2000, your e-mail client may display the following error message: This document has an invalid digital signature. Open the message for more information. |
| 27585 | In BizTalk Server 2000, users can set the times to perform final processing for documents that are destined for a specific port. This time interval is known as a Service Window. When BizTalk Server processes the data according to the Service Window,... |
| 27586 | BizTalk Server Messaging Manager allows users to choose SMIME (Secure Multipurpose Internet Mail Extensions) encryption when they are creating a port. However, the user cannot adjust the SMIME encryption parameters needed to change the encryption... |
| 27587 | In a high volume message system, the BizTalk Server Accelerator for RosettaNet may intermittently fail to validate the preamble or service header of RosettaNet messages. When this problem occurs, you may receive the following error message in the log:... |
| 27588 | BizTalk Server 2000 may not correctly verify a digital signature and decrypt an S/MIME encoded file. When this problem occurs, the message is immediately placed into the Suspended queue. |
| 27589 | When the BizTalk Editor tries to validate a document that contains double-byte character set (DBCS) characters, the validation is not successful because it does not correctly count the byte length of the DBCS characters. This problem also occurs in... |
| 27590 | An access violation may occur in BizTalk Server 2002. The following COM+ error is logged in the application event log: The system has called a custom component and that component has failed and generated an exception. This indicates a problem with the... |
| 27591 | When you execute the Dta_purge_old_records stored procedure to archive or remove your tracking database, you may experience exclusive table locks. These table locks cause table locking problems with other processes that are trying to access the... |
| 27592 | When you install BizTalk Server 2000, the sort order on the Programs menu may change from the order that was set before installation. |
| 27593 | When you open a document specification with the BizTalk Editor that contains an invalid content type, you receive a dialog box that states the following: Content must be empty, eltOnly, textOnly, or mixed. However, BizTalk Editor does not... |
| 27594 | BizTalk Server 2000 requires a minimum of 25 MB of free disk space on the system drive to install correctly. Insufficient disk space on the system drive may result in a runtime error during the BizTalk Server Setup file copy process. |
| 27595 | When you submit a large interchange, you may receive one or more of the following error messages: An error occurred in BizTalk Server. Details: ------------------------------ The database call failed and returned the following error string: String... |
| 27596 | Under heavy loads, documents in the Work Queue are marked as in-process . When many documents are moved at the same time, documents are left in the Work Queue and marked as in-process instead of being moved to the Suspended Queue. There is no data... |
| 27597 | When you test a map in the BizTalk Mapper, the following message may occur in the output window: The XML page cannot be displayed. Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.... |
| 27598 | The following error message may appear in the Application Event Log upon submitting XML data to BizTalk Server 2000: An error occurred in BizTalk Server. Details: The XML document has failed validation for the following reason: Error parsing '0.00' as... |
| 27599 | When you use an XLANG Scheduler that uses custom COM+ components and transactions, the Event Viewer may log one or more of the following events: Event ID: 12322 Event Source: XLANG Scheduler Event Description: The state of the schedule instance could... |
| 27600 | When you execute an Orchestration schedule, you may receive one or more of the following error messages in the Event Viewer: Event Type: Error Event Source: XLANG Scheduler Event Category: Engine Event ID: 12293 Description: The XLANG Scheduler Engine... |
| 27601 | When you are using BizTalk Messaging Manager remotely to access the advanced properties of a channel, you may receive the following error message: BizTalk Messaging Manager Error Unable to display configuration properties. Error 0x1FB: An exception... |
| 27602 | If you configure a Messaging Port using the file transport and you do not specify a filename with the directory path, you may receive the following error message: An error occurred while opening the target file. The server encountered a transport... |
| 27603 | When you submit a flat file to BizTalk for processing, the message ends up in the Suspended Queue with an Error Description of Parsing Failure. When this occurs, one of the following error messages may be logged into the Application event log: Event... |
| 27604 | When you open and close new drawings in the BizTalk Orchestration Designer, a memory leak may occur until you close the Orchestration Designer. |
| 27605 | When you use an XSLT map with BizTalk Server 2000, the output data may contain empty records or fields. This can cause validation against the destination schema to fail. |
| 27606 | When you install BizTalk Server 2000, you cannot use the Tab key to move to the Select an Existing BizTalk Server Group option in the Configure a BizTalk Server Group dialog box. |
| 27607 | When BizTalk Server 2000 experiences a low memory or out of memory condition, it does not stop trying to process incoming documents, even though out of memory errors are logged in the event log. When this occurs, the documents are not processed, but... |
| 27608 | If you enable tracking for an element or attribute as Integer data type on a BizTalk Server with a system locale that uses a non-period as the decimal point delimiter (for example, Korean), you may receive the following error in the BizTalk Server's... |
| 27609 | When you import a Microsoft BizTalk Framework 2.0-compliant schema into the BizTalk Editor, you may receive the following error messages: Generating warnings for Renamed Nodes and Specification Validation... Warning: The Order attribute of the... |
| 27610 | When you use the IInterchange interface SubmitSync method, you may receive the following error message: An error occurred in BizTalk Server. Details: The synchronous submission could not be completed because the channel matched a distribution list... |
| 27611 | When you attempt to shut down or start the XLANG Scheduler COM+ application, you may receive the following error message: Catalog Error You do not have permission to perform the requested action. If security is enabled on the System application of the... |
| 27612 | When you compile a drawing in BizTalk Orchestration Designer, the estimated percent that is complete may jump from a very low percentage to Done. |
| 27613 | The ALT + ENTER key combination does not display the properties for shapes in the BizTalk Orchestration Designer. |
| 27614 | When you view the XLANG Scheduler COM+ Component properties through a Terminal Service Client session, the XLANG tab may be missing. |
| 27615 | When you create or edit drawing in the BizTalk Orchestration Designer, you cannot copy or cut implementation shapes or ports. |
| 27616 | When a COM component is registered, and the Visual Basic source code of the component is being executed for debugging purposes, if you use the BizTalk Orchestration Designer to bind the component to a port, it may not appear in the list of components... |
| 27617 | When you install BizTalk Server 2000, if a user chooses to cancel the setup process while the database setup wizard is running, an internal error message dialog displays. |
| 27618 | The BizTalk Messaging Manager design time application allows users to create ports and channels that describe how to process business documents. Ports and channels have properties that allow users to select certificates for the purpose of encrypting... |
| 27619 | This article describes the methods used by BizTalk Server 2000 to determine the timeout values for database connection and command objects. |
| 27620 | When you move your mouse pointer over a functoid in the BizTalk Mapper grid area, tool tips are not displayed. |
| 27621 | This article describes the functionality of the Expect Receipt and Generate Receipt properties on the Source Organization page of the Channel Wizard. |
| 27622 | When you use the BizTalk Orchestration Designer, if the application fails while you are creating a drawing, the changes are not saved automatically and are lost. |
| 27623 | When you modify a rule in a decision shape, the same rule in a different shape may also be modified without notification of the change. This can have adverse affects on your Orchestration Drawing. |
| 27624 | When you attempt to drag an Orchestration Drawing (*.skv) into an open window in the BizTalk Orchestration Designer, you may receive the following error message: BizTalk Orchestration Designer Insertion of OLE objects is not supported. |
| 27625 | When a child schedule completes, it does not receive a ScheduleDone event until its parent schedule has completed. |
| 27626 | If you interchange a multi-byte character set (MBCS) flat file between BizTalk and other applications (such as a SAP application), the document may be corrupted. If you apply hotfix 312616 to correct this problem and you then submit the data of... |
| 27627 | When the keyboard layout and settings are set to French, German, or any other language that uses marked characters, text box fields such as User name and Password at the advanced channel properties do not accept special characters such as the at sign... |
| 27628 | After a connection interruption between the computer that is running BizTalk Server and the computer that is running Microsoft SQL Server, you may receive the following error message when you call IInterchange::Submit() or IInterchange::SubmitSync() :... |
| 27629 | After you create a new trading partner relationship by using the Trading Partner Manager (TPM) in Microsoft BizTalk Accelerator for HIPAA 2.0, the interchange control version number of the envelope properties may not be populated with the correct... |
| 27630 | When you use a custom Messaging Port encoding component with Microsoft BizTalk Server, you may notice that documents are both transmitted and sent to the Suspended Queue. Note This problem only occurs when you use non-transactional transports, such... |
| 27631 | When you post double byte character set (DBCS) data to an HTTP Receive function from the Microsoft BizTalk Server Software Development Kit (SDK) sample processPo.asp page, the data becomes corrupted if the HTTP Receive function is configured to submit... |
| 27632 | When you call the ADO Stream LoadFromFile method from a custom Microsoft BizTalk preprocessor to open the file that is provided in the vDataIn variable, you receive a cannot open file error message that states that the file is in use by another... |
| 27633 | When you try to duplicate a decision shape with the French version of the BizTalk Server 2000 Orchestration Designer on a computer that has the French version of Microsoft Visio 2002 installed, the following error message may occur: Probleme dans... |
| 27634 | When you try to duplicate a while shape with the French version of the BizTalk Server 2000 Orchestration Designer on a computer that has the French version of Microsoft Visio 2002 installed, the following error may occur: Probleme dans... |
| 27635 | In the BizTalk Server 2000 Orchestration Designer, the text in the Constants and in the Messages objects may wrap incorrectly in the borders of the objects. NOTE : This problem only seems to occur in localized non-English versions of Microsoft BizTalk... |
| 27636 | When you run the ThirdPartyApp.exe program, which is located in the Microsoft BizTalk Server\SDK\XLANG Samples\Integrating BizTalk Services\BTF Correlation\ThirdPartyApp folder, the following error message occurs if you click Reflect before you click... |
| 27637 | When you delete a transaction shape from your BizTalk Orchestration drawing, all of the shapes that are contained in that transaction are also deleted. |
| 27638 | When you try to put certain Unicode characters in your IBM MQSeries server by using the Microsoft BizTalk Adapter for MQSeries version 1.0, some of the characters are not converted correctly into ASCII. For example, a Unicode 0x85 (NEwLine) character... |
| 27639 | BizTalk Server is not compliant with the BizTalk Framework. The BizTalk Framework 2.0: Document and Message Specification states that the //deliveryReceipt/identity element belongs to the http://schemas.biztalk.org/btf-2-0/receipts namespace. However,... |
| 27640 | The BizTalk Server 2002 online help states the following: The maximum supported size limit for a document submitted to BizTalk Server is 20 MB. The maximum supported size limit for an interchange submitted to BizTalk Server is 20 MB. However, this... |
| 27641 | When you attempt to delete a BizTalk Server from the BizTalk Server Group in the BizTalk Server Administration Microsoft Management Console (MMC) snap-in, you may receive the following error message: The server cannot be deleted because of a failure... |
| 27642 | When you are using Orchestration Designer to edit a script component binding in an existing Orchestration Schedule, you may receive one or both of the following error messages: Microsoft VBScript compilation error - path to file [25,3] Expected... |
| 27643 | When you run UndoCleanQueuesPatch.sql in Microsoft SQL Server Query Analyzer to uninstall the CleanQueues stored procedure patch, the following errors may occur: Server: Msg 111, Level 15, State 1, Line 5 'CREATE PROCEDURE' must be the first statement... |
| 27644 | When you try to add a constant to the data page of BizTalk Server 2000 Orchestration Designer on a computer that has the German version of Microsoft Visio 2002 installed, the following error may occur: Problem bei... |
| 27645 | After you install the Microsoft XML 4.0 Beta on a computer running BizTalk Server 2000, the following behavior may occur in the BizTalk Editor or BizTalk Mapper: If you install the MSXML 4.0 Beta in replace mode, the BizTalk Editor and BizTalk Mapper... |
| 27646 | When you attempt to import a Messaging Manager configuration by using the Microsoft BizTalk Server 2000 SDK sample BizTalkConfigAssistant, no configuration is imported. |
| 27647 | Several Microsoft Visual C++ sample projects in the \Microsoft BizTalk Server\SDK folder will not compile without generating errors. See the More Information section of this article for specific projects and error messages. |
| 27648 | When you view the XML Representation window from the BTConfigAssistant SDK sample, and choose to save the data from the XML tab, it may save it as Microsoft Visual Basic Script data instead of XML data. |
| 27649 | You may experience lost messages in your BizTalk Server application when Microsoft SQL Server shuts down gracefully. |
| 27650 | The BizTalk Software Development Kit (SDK) XLANG Monitor sample (XLANGMon.exe) does not display any events for monitored schedules until you start a second instance of the XLANG Monitor. XLANG Monitor is located in the \Program Files\Microsoft BizTalk... |
| 27651 | When you try to open the CreditChecker Visual Basic sample that is included in BizTalk Server 2000, you may receive the following error: Disk is not ready: 'f:\programs\microsoft biztalk... |
| 27652 | When you use X12 documents with Microsoft BizTalk Server that use either Real (R) or Number (N) data types, your documents may fail data validation. The reason provided for validation failure may be similar to the following error message: Length is... |
| 27653 | When you run the PublicInterfaces sample, Sked.vbs, you may receive the following error: /remote server name path to sked.vbs(156, 5) Microsoft VBScript runtime error: The remote server machine does not exist or is unavailable |
| 27654 | The Orchestration Designer may generate the following error message when you use different functions in the Orchestration Designer: Microsoft Visual Basic Run-time Error '-2147417848 (0x80010108)': Method 'RequestFromVisio' of object '_Application'... |
| 27655 | In localized versions of the BizTalk Editor, the Microsoft Corporation hyperlink in the About BizTalk Editor dialog box links to an unlocalized Web site. |
| 27656 | Several SDK samples included with BizTalk Server 2000 contain syntax errors. The files can be modified manually to correct the problems. The following files in the Program Files\Microsoft BizTalk Server\SDK\Messaging Samples directory have a specific... |
| 27657 | When you change the computer name on a computer running BizTalk Server 2000, and you restart (reboot) the computer, error messages may occur. When you attempt to manually start the BizTalk Service in the Microsoft Management Console (MMC), the... |
| 27658 | When you invoke the Invalid Character Ranges dialog box for non-XML document specifications that are loaded into the Microsoft BizTalk Editor (from the View menu, click Invalid Character Map ), you cannot add, edit, or delete character ranges. When... |
| 27659 | This article describes the following two newly reported vulnerabilities in Microsoft BizTalk Server 2002: BizTalk Server 2002 allows documents to be exchanged by using the HTTP format. A buffer overrun exists in the component that is used to receive... |
| 27660 | At the BizTalk Server Setup Configure BizTalk Orchestration database screen, after you input your SQL server information and select Select an existing database , you may receive the following error message: [Microsoft][ODBC SQL Server Driver][SQL... |
| 27661 | When you use a BizTalk Framework (BTF) 2.0 envelope with Microsoft BizTalk Server 2000, the sentAt and expiresAt tags use Greenwich Mean Time (GMT) time instead of local time. For example: prop:sentAt2000-10-09T08:00:23+00:00/prop:sentAt... |
| 27662 | If you submit a document to BizTalk Server for processing by using a BizTalk Messaging port with a primary transport of Microsoft Message Queue Services (MSMQ), the following error may occur in the Application log: Event Type: Error Event Source:... |
| 27663 | The Microsoft BizTalk Accelerator for Financial Services Rollup corrects the problems that are described in the following Microsoft Knowledge Base articles: 319290 HIPAA Properties Lost When You Save Schema in BizTalk Editor 319290 HIPAA Properties... |
| 27664 | The Readme file for the Credit Check sample application that is included with Microsoft BizTalk Server 2000 incorrectly states that it uses two credit checking methods. |
| 27665 | When you are using the PublicInterfaces sample that is supplied with BizTalk Server 2000, you may receive the following error message: remote computer name XLANG Scheduler path to sked.vbs (157, 9) Microsoft VBScript runtime error: Invalid... |
| 27666 | When you use some of the samples that ship with Microsoft BizTalk Server on a non-English (localized) version of BizTalk Server, you may encounter one or more of the following errors: In the Microsoft Visual Basic version of the BTSAppIntegration... |
| 27667 | If you compile the Microsoft Visual Basic version of the SDK sample DistributionList (located in Program Files\Microsoft BizTalk Server\SDK\Messaging Samples\DistributionList\DistributionList.bas) into an EXE and run it, the program stops executing... |
| 27668 | When you install Microsoft SQL Server 2000 on a Microsoft Windows 2000 clustered computer that already has BizTalk Server 2000 installed, you may receive the following error: Microsoft Visual C++ Debug Library Debug Assertion Failed! Program:... |
| 27669 | When you use the Japanese version of Microsoft BizTalk Server, the SDK sample ReceiveFunction.vbs may fail with an error that is similar to the following: Existing Receive Functions: C:\Program Files\Microsoft BizTalk Server\SDK\Messaging... |
| 27670 | After you install the Microsoft BizTalk Server pre-SP1 Rollup Hotfix from the following Microsoft Knowledge Base article, BizTalk Server may experience degraded performance when you are processing documents: 293789 Availability of Microsoft... |
| 27671 | When you uninstall BizTalk Server 2000, Microsoft recommends that you manually delete the Program files\Microsoft BizTalk Server directory (folder) before you reinstall BizTalk Server. |
| 27672 | If document processing stops, the following event may be logged to the event log: Source: BizTalk Server Category: Document Processing Event ID: 324 Description: An error occurred in BizTalk Server. Details: ------------------------------ The server... |
| 27673 | After you install Microsoft Visio 2002 on your BizTalk 2000 server, if you try to start the BizTalk Orchestration Designer, you may receive one or more dialog boxes that prompt you to enable or disable macros. If you opt to enable macros, a series of... |
| 27674 | Microsoft BizTalk Server provides a feature that enables an administrator to view and manage documents by means of a Document Tracking and Administration (DTA) Web interface. A SQL injection vulnerability exists in some of the pages that are used by... |
| 27675 | When you double-click the Xlang.hlp file, which is found in the Program Files\Microsoft BizTalk Server\Docs folder, you encounter a blank Help window with no functionality. |
| 27676 | If you attempt to search for Messaging Manager objects in the BizTalk Server Messaging Manager, the following error may occur when you click the Search Now button: BizTalk Messaging Manager Error Microsoft XML Parser V2.6, is not registered on this... |
| 27677 | Microsoft has released a patch to correct two vulnerabilities in Microsoft BizTalk Server 2002 and one vulnerability in Microsoft BizTalk Server 2000. This patch is included in Microsoft Biztalk Server 2002 Service Pack 1 (SP1). about the latest... |
| 27678 | When you try to view files from Web Distributed Authoring Version (WebDAV) in BizTalk Editor or BizTalk Mapper, you may receive the following error message: No BizTalk Server repository was found on http://localhost/BizTalkServerRepository/DocSpecs.... |
| 27679 | When a user or process attempts to start an XLANG schedule from a remote Microsoft Terminal Server connection, BizTalk Server may return an error. The error message that is returned varies depending on how the user or process attempts to start the... |
| 27680 | After you pass an XML document through BizTalk Server, your white space may not be preserved. Where you previously saw a space, represented by hexadecimal 0x20, you may now see the following sequence of characters: 0D0A09. These characters are... |
| 27681 | A File Receive function fails and becomes disabled and an error message similar to the following appears in the BizTalk Server application log: Event Type: Error Event Source: BizTalk Server Event Category: Document Processing Event ID: 324 Computer:... |
| 27682 | This article describes how to contact Microsoft for help with the following issues: Replace lost, broken, damaged or defective Microsoft software disks. Purchase product upgrades. Replace broken or defective Microsoft hardware products. Check the... |
| 27683 | If a BizTalk application integration component (AIC) is set up as a COM+ server application that is running under a specific identity, some client applications may receive a General Access Denied error message while calling Channel.Create to create... |
| 27684 | When you try to run any of the tools in Microsoft BizTalk Server 2000 or BizTalk Server 2002 (such as Editor, Mapper, or Orchestration Designer), you receive the following error message: Thank you for evaluating Microsoft BizTalk Server 2000/2002. The... |
| 27685 | Each interchange in Microsoft BizTalk Server has its own transaction. A BizTalk Application Integration Component (AIC) can participate in this transaction through COM+ Service. When the AIC experiences an error, you can do one of the following:... |
| 27686 | When BizTalk Server validates a delimited flat file document that contains positional records, and the records are not in the order specified in the validating schema, an error message similar to the following appears in the BizTalk Server application... |
| 27687 | When you install Microsoft BizTalk Accelerator for Health Insurance Portability and Accountability Act of 1996 (HIPAA) 2.0 on a domain controller, you may receive the following error message: Failed to install trading partner manager -2146368497 |
| 27688 | BizTalk Application Integration Component (AIC) typically participates in the transaction that the BizTalk interchange starts. If a processing error occurs, AIC can either return a HRESULT error code to let the BizTalk engine abort the transaction, or AIC can abort the transaction directly. If AIC aborts the transaction directly, the message may be stuck in |
| 27689 | The Work queue, Scheduled queue, Retry queue, and Suspended queue in the BizTalk Server Administration Microsoft Management Console (MMC) may show an incorrect number of items. For example, the Suspended queue should show the number of records in the... |
| 27690 | When you use any of the Cumulative functoids in a map in BizTalk Server 2002, you may notice the following behavior: You supply a second parameter to limit the scope of the functoid. However, the functoid still accumulates the values for the whole... |
| 27691 | When you start the BizTalk Document Tracking interface, you may receive a blank error dialog box with only the title VBScript: BizTalk Document Tracking Error. |
| 27692 | Orchestration Designer may fail to launch if you have one of the listed regional locale setting. |
| 27693 | When you validate an X12 document instance in the BizTalk Editor, you may receive the following error message: The data contains a field value (01~26.60~MJ) that doesn't meet maximum length requirement for tag QTY01 (maximum length is 2). The... |
| 27694 | This step-by-step article describes how to set up a way to pass a flat file from BizTalk Orchestration to BizTalk Messaging. The ability to send and to receive flat file data is critical in many business processes. You may have to send or receive flat... |
| 27695 | This article describes how to install updates to SQL Server 2000 to help protect against the Slammer worm when you are using BizTalk Server 2000 or BizTalk Server 2002. |
| 27696 | If you attempt to open the Microsoft BizTalk Server 2000 Readme.txt files that are stored in a Microsoft Word format (with a .doc extension), you may get the following error message if Microsoft Word is not installed: Microsoft Word 97 Conversion... |
| 27697 | BizTalk XLANG schedules do not complete, and you receive an error message similar to the following in the application event log of the computer running BizTalk Server: Date: 1/20/2003 Time: 2:49:17 PM Type: Error User: N/A Computer: BIZTALKSERVER... |
| 27698 | When you call SubmitSync/Submit by using a document that starts with a null character, the submission fails and you receive the following error message: The submit method did not contain a document or file path. |
| 27699 | When you run BizTalk Server on a cluster, and you use a clustered XLANG Scheduler resource or a clustered Message Queuing (also known as MSMQ) resource, you may receive error messages similar to the following in the application log of the clustered... |
| 27700 | The Event log on your computer running BizTalk Server may become filled with an error message similar to the following: Event Type: Error Event Source: Perflib Event Category: None Event ID: 1008 Date: 12/10/2002 Time: 3:52:34 PM User: N/A Computer:... |
| 27701 | When you try to create an organization, either through code or through the Messaging Manager application, you may receive the following error message: Catastrophic Failure 0x8000ffff |
| 27702 | When you view the native instance of a flat file document in the BizTalk Document Tracking tool, the document does not appear as expected. |
| 27703 | A BizTalk Mapper database lookup functoid that works correctly when you test the map from Test Map on the Tools menu fails when it is called from a BizTalk channel. An error message similar to the following is generated in your BizTalk Server... |
| 27704 | After a connection interruption between the computer that is running BizTalk Server and the computer that is running Microsoft SQL Server, you may receive the following error message when you call IInterchange::Submit() : An error occurred in BizTalk... |
| 27705 | When you install a hotfix on your computer that is running Microsoft BizTalk Server after you upgrade from BizTalk Server version 2000 to version 2002, you may receive the following error message: Server: Msg 1781, Level 16, State 1, Line 3 Column... |
| 27706 | After you upgrade your Microsoft BizTalk Server computer to Microsoft Windows 2000 Service Pack 3, you may receive the following error message in BizTalk Server when you process multi-part MIME files: An error occurred in BizTalk Server. Details:... |
| 27708 | When you run the dta_purge_old_records script to clean out records from the Document Tracking database, the records in the dta_group_correlation_keys table that should be deleted remain in the table. |
| 27709 | When you try to run a dynamic report in Commerce Server, you may experience memory errors or blank dynamic reports. |
| 27710 | This article contains information from the BizTalk Server 2000 Readme.htm file. |
| 27711 | Do not install BizTalk Server 2002 for use in a production environment on a computer that is running Windows XP Professional. Installation of BizTalk Server 2002 is fully supported on Windows XP Professional for development purposes. |
| 27712 | The dta_purge_old_records stored procedure in BizTalk Server may delete the inbound document for an interchange and still leave the outbound document in the database. This causes the nInDocKey field in the dta_outdoc_details table to point to records... |
| 27713 | To determine the version or service pack level of BizTalk Server that is currently installed, view the file properties for any of the DLLs in the BizTalk Server installation folder, and then compare the version number with the values in the chart that... |
| 27714 | When you try to open the Trading Partner Manager, you may receive the following error message: A Runtime Error has occured. Do you wish to Debug? Line: 540 Error: Object Required |
| 27715 | After you install a hotfix for BizTalk Server, the BizTalk Messaging Service on a local computer may not start correctly. The BizTalk Server computer may not return an error message. If the server does return an error message, you see the following in... |
| 27717 | When you use a built-in mathematical functoid in the BizTalk Mapper tool to return a float value, the floating point value that is returned may not seem to be accurate. |
| 27718 | During serialization, if an incoming field contains a null value, the output document may not contain the field. This was originally by design, but this behavior will change when you install Microsoft BizTalk Server 2002 Service Pack 1 (SP1) . You can... |
| 27719 | When a File receive function uses a document specification that has an envelope that matches the document specification, the File receive function uses the envelope on the incoming document whether this is specified by the File receive function or not. |
| 27720 | Microsoft BizTalk Accelerator for HIPAA version 1.0 may serialize some fields of your document when these fields do not exist in the inbound document. Also, the value for these incorrectly serialized fields is set to 0 . |
| 27721 | By using reliable messaging and MIME encoding, the HTTP transport moves the MIME Content-Type header to the HTTP Content-Type header. However, you may want to retain the MIME Content-Type header in the HTTP body. |
| 27722 | When an XLANG schedule is waiting for a correlating message from a Microsoft Message Queuing queue, the XLANG schedule may not receive the message notification, although the message has arrived at the Message Queuing queue. If this occurs, the XLANG... |
| 27723 | SYMPTOMS When BizTalk Server 2000 is running in a properly configured clustered environment, and you move a group from one node to the other, the XLANG Scheduler application may take a long time to go offline. Also, when the application does go |
| 27725 | SYMPTOMS When you select optional fields of an incoming document, if these fields do not exist in the document, the document is not accepted by the XLANG Schedule engine. |
| 27726 | When a client calls the IInterchange::SubmitSync method, BizTalk eventually calls a custom parser if there is one custom parser registered for this interchange. However, the custom parser cannot gain access to these parameters, which are passed to... |
| 27727 | SYMPTOMS Q319448 and Q322017 resolved problems in the BizTalk 2002 reliable message interchange. If you installed either of these fixes, BizTalk uses the certificates that are stored in the computer's personal store for signature verification and not |
| 27728 | When you do a Controlled Shutdown from the XLANG Scheduler COM+ application, some schedules that have a WHILE loop may not dehydrate. In some instances, the XLANG Scheduler application may stop responding (hang). |
| 27729 | When you use a Microsoft Message Queue Server (MSMQ) receive function to receive data from a well-known queue, the following error message may occur: Event ID: 324 Source: BizTalk Server Category: Document Processing Description: An error occurred in... |
| 27730 | SUMMARY When you use the BizTalk Server Editor to validate a data instance by using the X12 schema, you may receive the following error message: The value of HL04 is incorrect. The parser failed to convert the document due to processing errors. See |
| 27731 | Under high stress, a Microsoft Visual Basic component that makes a call to the GetObject method ( some valid moniker) may intermittently receive the following error message from the Visual Basic runtime, although the moniker is valid: No Object You... |
| 27732 | The Microsoft BizTalk Server 2000 EDIFACT parser cannot convert DBCS characters correctly. If the BizTalk Server EDIFACT parser parses an EDIFACT document that contains DBCS characters, these characters translate as garbage characters. |
| 27733 | SYMPTOMS When you try to process an X12 document by using BizTalk messaging, you may receive an error message similar to the following in the Application log of your BizTalk Server: Event Type: Error Event Source: BizTalk Server Event Category: |
| 27734 | SUMMARY Microsoft BizTalk Server 2002 is available in four editions that have different pricing and licensing to meet the needs of various customers. The table in the More Information section of this article summarizes the differences between these |
| 27735 | SUMMARY This article demonstrates how to use a BizTalk Application Integration Component (AIC) to send BizTalk documents as attachments to Simple Mail Transfer Protocol (SMTP) messages by means of Visual C#. The AIC writes the document that it is |
| 27736 | In the advanced properties for a channel, you can set whether the file transport overwrites the file, appends to the file, or creates a new file. When you select Append to file , BizTalk Server cannot append to the file if the file is being monitored... |
| 27737 | SUMMARY This article describes the impact that the threading model of BizTalk Application Integration Components (AICs) has on the performance of these components. Also, this article discusses why AICs that you develop by using Visual Basic 6.0 can |
| 27738 | SYMPTOMS BizTalk Server moves documents that are processed with a custom parser component to the suspended queue, and the Application log of BizTalk Server generates an error message that is similar to the following: Event Type: Error Event Source: |
| 27739 | Microsoft BizTalk Server Reliable Messaging is a feature of the BizTalk Framework 2.0 protocol that supports guaranteed, one-time-only delivery of documents in heterogeneous environments across the Internet. In accordance with the BizTalk Framework... |
| 27740 | SYMPTOMS When you use the BizTalk Editor to import schemas that contain element groups, you may receive one of the following error messages: Warning: Element groups are not supported. The occurrence properties for the affected nodes have been |
| 27741 | SYMPTOMS When the BizTalk Server and the XLANG Scheduler Engine are clustered, running XLANG schedules on the first node may not finish on the second node after cluster failover. This occurs on schedules that have the whole business process (except for |
| 27742 | SYMPTOMS If you try to run a COM+ application that is set to host XLANG Schedules, and the application is not configured with an appropriate DSN, you may receive the following error message: The database connection could not be established. The |
| 27743 | When you try to test a map in the BizTalk Mapper by using a generated XML instance, you may receive the following error message: The XSL transformation that uses the test-instance document for the source specification failed. Reason: Microsoft... |
| 27744 | Documents are listed in the BizTalk Server Work queue or Retry queue with the following status: No Processing Server |
| 27745 | When you try to run an XLANG schedule, you may receive the following error message: The XLANG Scheduler Engine was unable to create an interceptor object for the interface ID shown in the following message. Probable causes for this are 1) the... |
| 27746 | When you try to submit a document to BizTalk Server by using the Interchange.Submit method with the Document parameter, the following event is logged in the Application event log of your BizTalk Server: Event Type: Error Event Source: BizTalk Server... |
| 27747 | When you try to start the BizTalk Orchestration Designer, you may receive the following error message: Problem in General.startVisio Error Number: 70 Error Description: Permission denied After you click OK to dismiss this error message, you receive... |
| 27748 | This step-by-step article describes how to create a simple preprocessor for BizTalk Server by using Visual Basic .NET. Create the Interop DLLs NOTE : In the following steps, you will run several commands from the Microsoft Visual Studio .NET command... |
| 27749 | A BizTalk HTTP transport may be unsuccessful when the HTTP transport posts messages to the partner. The problem may cause duplicated messages to be sent to the partner and may cause messages to be moved to the suspended queue. The problem occurs if |
| 27750 | Stopping and restarting the BizTalk Messaging Service may not reset the BizTalk Server Performance Monitor counters for Documents Received and Documents Processed. |
| 27751 | BizTalk Server may try to use up all available system memory when it is processing a large number of large documents. |
| 27752 | If a Multipurpose Internet Mail Extensions (MIME)-encoded message does not have MIME-Version as the first header, BizTalk Server does not parse the data, and you receive the following error message: An error occurred in BizTalk Server. Details:... |
| 27753 | The BizTalk Server Flat File Serializer may overwrite the data in the previous field when input data is larger than destination field. This problem can occur whenever the schema is using right justification and the input data for a field is |
| 27754 | This article describes how to implement the single-instance correlation that is used in the XLANG correlation sample that is included with BizTalk Server 2002 Software Development Kit (SDK). |
| 27755 | If BizTalk Server 2002 loses connectivity to its messaging databases because of an unexpected database failure or network problem: |
| 27756 | If you set up a BizTalk server as a receive-only server, and the computer that is running Microsoft SQL Server for the BizTalk server fails, the receive functions of BizTalk server may stop responding even after you restart the computer that is... |
| 27757 | Although a reliable message is delivered successfully to the partner, the BizTalk InterchangeDTA database may display an nError code value of 8 in the dta_interchange_details table, which indicates that the message is still in the Retry queue. The... |
| 27758 | When a BizTalk Server HTTP receive function is configured to synchronously submit messages to BizTalk Server, the receive function may return a "500 Internal Server" error to the application that is sending messages to the server. |
| 27759 | In BizTalk 2002, you can manually move documents from the Work queue to the Suspended queue to resubmit the document. BizTalk 2002 may create a duplicate outbound interchange record for a single inbound interchange record if documents are m |
| 27760 | When you view the properties of any COM+ application from the Component Services Microsoft Management Console (MMC) on the inactive node of a BizTalk cluster, the XLANG schedules may fail after failover. This is specific only to any COM+ ap |
| 27761 | When you use Microsoft BizTalk Server 2002, the DateTime string that is returned when it is added to a messaging post (%datetime%) as part of the file name is not displayed in the same format as in BizTalk Server 2000. |
| 27762 | You may notice that the XLANG Scheduler COM+ component leaks memory when the schedules are processed in a "burst and wait" manner instead of a constant, steady flow of new schedules as older schedules complete. |
| 27763 | Work items in the BizTalk Server 2002 work queue may be marked for processing, but are not processed by a processing server. This may occur when the BizTalk Server is running in a moderate to high stress environment. If this occurs, it can |
| 27764 | You may notice that the private bytes in BizTalk Server XLANG Scheduler COM+ component increase substantially after periods of high activity. When the activity stops, and when the computer is idle for 15 to 20 minutes, the high activity is |
| 27765 | This article describes how to programmatically re-enable all disabled BizTalk Receive functions on your BizTalk Server computer. |
| 27766 | If you map a constant value of the int data type to a Microsoft Visual Basic Script scripting component as a parameter on an Xlang schedule, the workflow may fail to complete and an error message that is similar to the following one is logged in |
| 27767 | You may receive the following error message when you open the Microsoft Management Console (MMC) interface for BizTalk Server 2002 Administration: Instances of MicrosoftBizTalkServer_Group cannot be enumerated: The connection to the BizTalk |
| 27768 | You cannot use XLANG correlation with XLANG receive actions that are bound to BizTalk Messaging. XLANG Correlation requires the use of a shared MSMQ queue. When you use the BizTalk Messaging Binding Wizard to create a receive action, per-instance |
| 27769 | BizTalk Server 2002 includes Application Center 2000 Service Pack 1 (SP1), which provides support for the deployment of BizTalk resources with Application Center 2000. The following BizTalk resources are available with Application Center 2000 |
| 27770 | When an XLANG schedule is using correlation: Significant delays may occur in the time that it takes to complete multiple schedules. The data instance that is being correlated may be moved to the suspended queue. |
| 27771 | The French and German versions of BizTalk Server 2002 do not have Microsoft Application Center deployment capabilities. |
| 27772 | After you create an HTTP Receive function and submit a document to the URL specified in the Receive function, an error message similar to the following may occur the event log: Event Type: Error Event Source: BizTalk Server Event |
| 27773 | When you store documents that have double-byte character set (DBCS) characters in the file name to a WebDAV repository from the BizTalk Mapper or the BizTalk Editor, the actual file name that is stored in WebDAV may contain garbage characters. |
| 27774 | When you run the ExecuteTutorial.exe file that is included with the BizTalk Server 2002 tutorial, the scripting components should generate pop-up messages in the tutorial's schedule. However, if you run ExecuteTutorial.exe from a Terminal Services |
| 27775 | When you drag a Port implementation shape onto an XLANG drawing (an .skv file), the port name is displayed with unreadable, meaningless characters. This problem occurs under the following conditions: If you are using a computer that is running |
| 27776 | When you submit a document to an HTTP Receive function that is configured to output to a file, if the file location specified uses the %tracking_id% variable, the following error message may occur in the Application log for BizTalk Server: |
| 27777 | You may experience one or both of the following problems: When you create a new application in Microsoft Application Center, if you click BizTalk resources , and then click Add , a list of high-level objects, such as BiztalkCustomCounters ,... |
| 27778 | BizTalk Server does not track the document type of an input document when the input document is in a plain text format. |
| 27779 | When you try to deliver a message to a Microsoft Message Queuing queue with the Microsoft BizTalk Server Message Queuing transport, an error message that is similar to the following is generated in the Application log of BizTalk Server: |
| 27780 | There are two variations of the HTTP receive correlation token format: One is returned when the Receive function makes a call to Interchange.Submit and one that is returned when the Receive function writes the incoming document to a file. |
| 27781 | You can validate an XML document with a target namespace in BizTalk Messaging Manager. However, if you try to use the same XML document and the same schema in the XLANG Scheduler, the validation is unsuccessful, and an error similar to the following |
| 27782 | If you interchange a multi-byte character set (MBCS) flat file between BizTalk and other applications such as SAP, the document may be corrupted. |
| 27783 | To run the Microsoft BizTalk Accelerator for RosettaNet version 2.0 on Microsoft Windows XP, you must install a Windows XP pre-Service Pack 1 fix. |
| 27784 | If you call IInterchange::Submit() to submit a document to a distribution list that has a large number of ports, the operation remains pending and prevents other Submit calls from completing until one document for each port is populated in the |
| 27785 | BizTalk Server has added the ability for the BizTalk messaging engine to prioritize the processing of messages from the work queue. After you install the fix that is described in this article, you can set a priority level between 1 and 10 on a... |
| 27786 | When you correlate messages to running BizTalk schedule instances, and some of the instances have been dehydrated, some of the schedules may not complete. |
| 27787 | When you open a Health Insurance Portability and Accountability Act (HIPAA) schema that contains attributes of reserved properties (that is, reserved_prop1 to reserved_prop5 ) in BizTalk Editor, and you then use BizTalk Editor to save the |
| 27788 | When you run Lesson 7 of the Learning BizTalk Server tutorial, users may encounter the following error in the Windows 2000 Application Event Log: An error occurred in BizTalk Server. Details ------------------------------- [0x80004005] |
| 27789 | When you try to add a server to a BizTalk Server group through the Microsoft Management Console (MMC) Administration Interface, you may receive the following error message: The specified server cannot be added because of a failure returned from |
| 27790 | When you run the NestedTxns sample, which is located in the Program Files\Microsoft BizTalk Server\SDK\XLANG Samples\NestedTxns folder, the following error message occurs: [27,13] Variable uses an Automation type not supported in VBScript [27,13] |
| 27791 | When you attempt to start the BizTalk Server Orchestration Designer on a computer running Microsoft Windows XP, the following error message may occur: Problem in General.startVisio Error Number: -2147319779 Error Description: Automation error |
| 27792 | When you try to uninstall BizTalk Server 2002, you may receive one of the following error messages: Internal Error 2744. LocalGroupDel_Tracking, C:\WINNT\Installer\MSI528.tmp, /Silent /NoFail /Del BizTalk Server Report Users Internal |
| 27793 | You may receive the following error message while you are configuring the BizTalk Server 2002 Messaging Manager to point to a remote BizTalk 2002 Server: The response document is not a valid document. This could be due to an incorrect BizTalk |
| 27794 | When you use the BizTalk 2002 SDK Refresh Messaging Manager tool to refresh a specific channel, the corresponding map definition is not refreshed as expected. |
| 27795 | When you view document specifications with the Microsoft BizTalk Server Editor New Document Specification dialog box, you may not be able to view all of the specifications that are available in a folder. |
| 27796 | To set up the environment that is required to go through the Learn BizTalk Tutorial, you must run the Setup.vbs script file that is located in the C:\Learnbiztalk\Scripts folder. However, you may receive one or more of the following error m |
| 27797 | When you try to run a BizTalk Orchestration schedule that contains at least one COM+ component that is written by using Visual Studio .NET, you may receive the following error message in the BizTalk Server Application event log: |
| 27798 | The BizTalk Server event log does not log any errors when a client posts messages to a disabled HTTP Receive function. |
| 27799 | If you try to start the ODBC Data Source Administrator for more than one XLANG Schedule host simultaneously from the same Microsoft Management Console (MMC) interface, the COM+ Explorer experiences a deadlock condition and it stops responding. |
| 27800 | When you use the BizTalk Configuration Object Model to retrieve an instance of a BizTalk.BizTalkConfig Management object, you may receive the following error code: BTS_E_NOOBJECT 0x1202 The object was not found. This error can occur even if you are... |
| 27801 | When you validate an XML instance or document against a schema, Date and Date Time fields are not checked for a valid number of days per month, other than ensuring that the numeric value in a Day field is not greater than 31. |
| 27802 | The selection of messages from the Retry queue in BizTalk Server 2002 may cause some messages to not be processed for a long time (which is also known as starvation). If these unprocessed messages are related to messages on which the running XLANG... |
| 27803 | When you use SMTP as a Primary Transport, the default subject line that is sent with the message contains the interchange GUID. You can manually modify the subject line by opening the Channel that is bound to the port and overriding the properties by... |
| 27804 | This article details the steps that are required to create a BizTalk Server Application Integration Component (AIC) to parse XML data into a Microsoft SQL Server 2000 table. |
| 27805 | When you use the Database Value Extractor functoid in a map to extract a date field, your document may fail validation against the outbound document definition. BizTalk Server may log the following validation error in the event log: Event Source:... |
| 27806 | The Microsoft BizTalk Server Pre Service Pack 1 (SP1) Rollup Fix corrects the problems that are described in the following Microsoft Knowledge Base articles: 281470 BizTalk Server Appends Random Characters to Flat File Output 281470 BizTalk... |
| 27807 | When you use XLANG schedules with transactions or long-running actions, the persistence database is filled with all the information that is related to that schedule instance. However, this information is never purged. Even when a schedule |
| 27808 | BizTalk Server Parser and Serializer components or Custom Parser and Serializer components may fail to serialize output. BizTalk Server may fail to serialize data into its native format, if the data contains embedded nulls. The document being... |
| 27809 | When BizTalk Server attempts to process a document that requires a Custom Parser Component, the document may never move from the Work Items queue. |
| 27810 | When you open an XLANG schedule (.skv) file numerous times without closing the BizTalk Orchestration Designer, most of the BizTalk Orchestration Menu items are disabled (grayed out). |
| 27811 | When a connection to SQL Server fails, BizTalk Server sends documents that are being processed to the Suspended queue. |
| 27812 | When BizTalk Server sends data through an HTTPS POST request to a Web server by using a VeriSign Global Server ID certificate, the following error may appear in the Application log: |
| 27813 | When you configure a channel, you can select a client certificate to use for a HTTPS transport in the Advanced Configuration dialog box. The certificate should have Client Authentication as its intended purpose. Both Microsoft Client Authentication... |
| 27814 | When you try to access certain resources from within components in BizTalk Server (for example, an AIC that needs to write to a specific folder), access may succeed or fail depending on if you use the |
| 27815 | If the Health Insurance Portability and Accountability Act of 1996 (HIPAA) parser is under heavy stress, Biztalk Server may report the following access violation in the event log, which forces the parser to quit: |
| 27816 | If you create a file transport that specifies a local folder (such as C:\FileDest) for a messaging port and you have more than one processing server in your BizTalk Server Group, documents that are sent to this messaging port are sent to th |
| 27817 | After a BizTalk Server cluster failover, sometimes the temporary private Microsoft Message Queuing queues that the XLANG Scheduler creates are not automatically deleted from the previously active node. |
| 27818 | If you bind an XLANG port to a Microsoft Visual Basic COM component and you select the No instantiation option, the resulting compiled schedule may stop responding or hang when you run it, particularly if the schedule is dehydrated. |
| 27819 | The Microsoft SQL Server computer that hosts the Microsoft BizTalk Server XLANG database may generate Unspecified Error and Timeout errors. Additionally, error messages that are similar to the following are generated in the BizTalk Server... |
| 27820 | When you use the BizTalk Server Messaging Manager to save a Channel, a Document a Definition, or an Envelope that references a specification or map in a WebDAV repository, you may receive an error message that is similar to the following: |
| 27821 | The BizTalk Adapter for MQSeries stops receiving files after periods of inactivity. |
| 27822 | During the BizTalk Server 2000 Service Pack 2 (SP2) installation, a dialog box with the following text is displayed: The feature you are trying to use is on a CD-ROM or other removable disk that is not available. Insert the 'Microsoft BizTalk Server... |
| 27823 | The Microsoft BizTalk Server 2000 online documentation may not be displayed properly if Microsoft Internet Explorer 6.0 is installed on the same computer. When you select a topic from the left pane of the online documentation, the article may not be... |
| 27824 | When you try to start the Japanese version of the BizTalk Editor, the BizTalk Mapper, or the BizTalk Orchestration Designer, the following error message is displayed: Thank you for evaluating Microsoft BizTalk Server 2000. The period for this... |
| 27825 | While you are starting or using Orchestration Designer, an error message may be generated that displays error code 0x500C, which translates to the error label: |
| 27826 | File receive functions fail and generate an error that is similar to the following one in the BizTalk Server Application log: Event Type: Error Event Source: BizTalk Server Event Category: Document Processing Event ID: 324 Date: 10/16/2001 Time: 19:10... |
| 27827 | This article provides information on the bugs that are fixed by BizTalk Server 2000 service packs. Service packs are cumulative, so bugs that are fixed in one service pack are also fixed in subsequent service packs. For example, the bugs that are... |
| 27828 | You cannot edit the XPath filter field in BizTalk Server 2002. |
| 27829 | When you run the COM Application Export Wizard to export a COM+ application that contains a BizTalk Server Pipeline Application Integration Component (AIC), you receive the following error message: |
| 27830 | When you configure BizTalk Sever to communicate to an HTTP 1.0 server, the BizTalk HTTP client does not honor the protocol requirements that are specified in the published HTTP RFCs with regard to persistent connections behavior. |
| 27831 | When you click |
| 27832 | If you attempt to connect to a WebDAV repository through Secure Sockets Layer (SSL) with the BizTalk Editor, Mapper, or Seed Wizard: |
| 27833 | When you run Btssetupdb.exe to rebuild the BizTalk InterchangeBTM database, the Disk Transfer Address (DTA) tracking user interface may not point to the new tracking database. |
| 27834 | When BizTalk Server sends documents through the HTTP/HTTPS transport to an ASP page that is located on a Microsoft Internet Information Services (IIS) server, document delivery fails and the documents are placed in the suspended queue of the sending... |
| 27835 | You may receive the following error message when you are trying to save to the WebDAV repository in the BizTalk Editor: |
| 27836 | When an HTTP send is performed from BizTalk Server to a redirected URL, the following error message is generated in the Application event log of the computer running BizTalk Server. In addition, the document being processed is placed in the Retry... |
| 27837 | After you install BizTalk Server Service Pack 1 or BizTalk Server Service Pack (SP) 1a, you may notice decreased performance when you are using the File Transport. You may observe this decrease in performance regardless of whether the file path is... |
| 27838 | If you uninstall any Microsoft BizTalk Server 2000 service packs, Microsoft BizTalk Server 2000 Setup reverts any installed Microsoft XML (MSXML) 3.0 service packs back to the original installation bits for Microsoft XML 3.0. |
| 27839 | If you install the BizTalk Orchestration run-time components on a computer on which you have not installed the BizTalk Messaging Service, the Orchestration Performance Monitor counters are not available. |
| 27840 | The functional acknowledgments that the BizTalk Accelerator for HIPAA creates always have ST02 set to 0001. |
| 27841 | When you attempt to access the advanced properties of a channel that is bound to a port that uses a transport of Application Integration Component the following error message is displayed: |
| 27842 | If you install Microsoft BizTalk Server 2000 on a stand-alone computer and the Microsoft SQL Server databases are running on a Windows Clustering-based cluster, Setup fails during the database setup portion and the following error message is... |
| 27843 | If you set up a BizTalk server as a receive-only server, and the Microsoft SQL Server computer for the BizTalk server fails, the receive functions of BizTalk server may stop responding even after you restart the SQL server. |
| 27844 | The BizTalk X12 parser may fail when the trigger segment of a triggered loop is missing and another segment is found in that loop. |
| 27845 | When you install BizTalk Server 2000, you may receive errors messages that are similar to the following: Error 1904. Module C:\Program Files\Microsoft BizTalk Server\INTERCHANGEPROV.dll failed to register. HRESULT = -2147024770. Error 1904.Module... |
| 27846 | When BizTalk Server is under stress, you may encounter problems with server performance, event sequence, and user event marshalling. You may also receive Access Violations. |
| 27847 | If you try to connect to a Microsoft BizTalk document tracking database with the Document Tracking user interface from a client computer that is not running Microsoft BizTalk Server or Microsoft SQL Server, you may receive the following error message:... |
| 27848 | When you are attempting to compile a BizTalk Orchestration Schedule, you may receive either of the following two messages: Just-In-Time Debugging Would you like to debug using the selected debugger? -or- Microsoft Development Environment An exception... |
| 27849 | While BizTalk Server is running, an MSI Installer dialog box may suddenly open in which you are prompted to provide the location of the BizTalk Server Setup files. This causes all of the currently-running BizTalk Server processes to pause u |
| 27850 | When you install Microsoft BizTalk Server, you may receive the follow error messages: Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or... |
| 27851 | You can upgrade BizTalk Server to the latest version without uninstalling the previous version of BizTalk Server. To do so, use the following guidelines: Back up the BizTalk Server databases as a precautionary measure. In a default Microsoft BizTalk... |
| 27852 | In BizTalk Server 2000, you may be unable to start BizTalk Orchestration Designer. |
| 27853 | When BizTalk Server uses HTTP transport to communicate to a destination server with a keep-alive connection, it will usually reuse this connection or time out the connection. However, under some circumstance, BizTalk Server may not reuse the... |
| 27854 | If you receive a document that is wrapped by BizTalk Framework envelope and the envelope has a timestamp (expiresAt) value that is interpreted as expired by BizTalk Server, the following error may be generated in the Application Log of your |
| 27855 | After you start BizTalk Orchestration Designer, the Orchestration Designer splash screen appears, but Orchestration Designer fails to load. When this occurs, an instance of Visio.exe may be running in Task Manager. |
| 27856 | When you configure a port and channel combination to use HTTPS, BizTalk Server may fail to properly negotiate a secured connection over HTTPS. |
| 27857 | BizTalk Server may not properly validate documents with text elements that do not adhere to the required minimum or maximum lengths. |
| 27858 | If a BizTalk Server receive function preprocessor is written in Microsoft Visual Basic, when you use this receive function preproprocessor to process binary data, BizTalk Server truncates the SAFEARRAY output that is returned by one byte. This data... |
| 27859 | This article briefly describes the impact of using a Microsoft Visual Basic 6.0 component in the BizTalk Configuration Object Model, more specifically, the use of a Microsoft Visual Basic 6.0 component as an Application Integration Component (AIC).... |
| 27860 | Service packs are the means by which Microsoft distributes bug fixes. Service packs keep a product current. Service packs include updates and may include system administration tools, drivers, and additional components, which are conveniently bundled... |
| 27861 | Your Microsoft BizTalk Server may send documents to the Suspended Queue without a matching entry in the Event Viewer. The error description for the document instance in the Suspended Queue is similar to the following: The document extracted from the... |
| 27862 | When you search for text in a BizTalk Orchestration drawing that does not exist, the following error message may occur: Visio has finished searching the page. |
| 27863 | When you try to search for existing objects or to create new objects in the Microsoft BizTalk Messaging Manager, you may receive the following error message: The response document is not a valid document. This could be due to an invalid BizTalk Server... |
| 27864 | When you are processing a data instance on a computer that does not have BizTalk Server 2000 Service Pack 1 (SP1) installed, the following error may occur in the BizTalk Server Application event log: |
| 27865 | This article contains information from the BizTalk Server 2000 Readme.htm |
| 27866 | When you use the BizTalk Server Administrator to change the Tracking Database Connection properties to point to another tracking database, the BizTalk Document Tracking Web page still accesses the original tracking database. |
| 27867 | When you create a port to an open destination and attempt to process a document with the destination value set to an e-mail address (for example, |
| 27868 | When you configure a BizTalk Framework 2.0 document with a reliable envelope, and it does not receive an acknowledgement from the destination server before all retry attempts are exhausted, BizTalk Server moves the document to the Suspended |
| 27869 | BizTalk Orchestration Designer allows you to bind a property accessor function of a COM+ component to a port in the XLANG schedule. However, when you reopen the schedule in BizTalk Orchestration Designer and run the binding wizard, you may |
| 27870 | When you use the BizTalk Messaging Manager to manage a remote BizTalk Server, you may experience one of the following symptoms: When the wizard creates a new configuration object, such as a port, it does not complete when you click Finish . It just... |
| 27871 | This article is a listing of article numbers for bugs that were fixed in BizTalk Server 2000 Service Pack 1. |
| 27872 | When you use the BizTalk Editor, if there is a value for the Target Namespace property on the Reference tab of a non-XML document specification, document instances may fail to validate against the specification and you may receive an error similar to... |
| 27873 | BizTalk provides the BizTalk.BizTalkConfig object for user programs to access and update BizTalk Management Objects such as Channels , Ports , Organizations , and so forth. When you have a large number of channels (such as 3000) and you try to use a... |
| 27874 | If an XLANG schedule instance is suspended while it is waiting to receive a document from a Microsoft Message Queuing (MSMQ) message queue, it may block other running schedule instances from receiving messages from the same message queue. The XLANG... |
| 27875 | In the Microsoft BizTalk Server tutorial, PORequestApproval.wsc contains the following statement which expects an English date/time format: Line 47:BR/ 'Generate a Unique Number used to generate unique files using a maskBR/ strTimeNow =... |
| 27876 | One or more of the BizTalk Server Microsoft Message Queuing (MSMQ) receive functions may be disabled and the following error message may occur in the BizTalk Server Application log: Event Type: Error Event Source: BizTalk Server Event Category:... |
| 27877 | The More Information section of this article describes the steps to configure Commerce Server 2000 sites to send and receive catalogs through BizTalk Server 2000. Note that the information in this article is for users who have BizTalk Server and... |
| 27878 | If you try to open a Schedule (.skv) file that has been created with a pre-release version of the BizTalk Orchestration Designer with the released version of the BizTalk Orchestration Designer, you may receive the following error messages: |
| 27879 | You cannot access BizTalk Configuration information from a client that is configured to run under the credentials of an account that is not a member of the BizTalk Server Administrators Group. |
| 27880 | When BizTalk Server is located in one domain (Domain1) and the polling location of the Receive Function is in another domain (Domain2), two-way trust must be established between Domain1 and Domain2. In addition, the Domain2 account configur |
| 27881 | This article describes the steps to configure Commerce Server 2000 sites to submit purchase orders through BizTalk Server 2000. NOTE : The information in this article is for users who have BizTalk Server and Commerce Server 2000 installed on the same... |
| 27882 | Many organizations need to automate the installation process for BizTalk Server. This article provides a simple batch file that demonstrates how to use the silent installation features in Microsoft Installer. The BTSSilentInstall.exe file that is... |
| 27883 | When you use a localized version of Microsoft BizTalk Server, you may experience a corrupt display in the Orchestration Designer. For example, text strings are wrapped differently within the flowchart shapes than when the drawing was saved. |
| 27884 | You cannot use your keyboard to access or manipulate flowchart shapes when you use Microsoft BizTalk Server 2000 Orchestration Designer. |
| 27885 | When you submit a document for processing by Microsoft BizTalk Server, the document may not move out of the Work Items queue, and the following informational messages may appear in the Application log of the BizTalk Server: Event Type: Information... |
| 27886 | When you attempt to connect BizTalk Server to a clustered Microsoft SQL Server computer, the BizTalk Server Setup program and the BizTalk Messaging Service fail, and the following error message occurs: CIS_E_ADMIN_DBCONNECT - BizTalk Server failed to... |
| 27887 | When you use Microsoft Application Center to deploy BizTalk Server channels and ports that use certificates, the deployment fails if the certificates are not installed on the destination BizTalk Server computer prior to the Application Center... |
| 27888 | After you install BizTalk Server on a cluster, you cannot save a BizTalk Server messaging port that uses a primary or backup transport type of SMTP. When you attempt to save a BizTalk Server messaging port that has been created with the SM |
| 27889 | After you uninstall BizTalk Server 2000 Service Pack 1 (SP1), you may experience SQL Server connection problems when you attempt to access the BizTalk Document Tracking user interface. |
| 27890 | When you add new message fields from a schema that was created with the BizTalk Editor to a port in the BizTalk Orchestration Designer, the XML data types that are used in the schema are converted to a String data type. |
| 27891 | When you register an Application Integration Component (AIC) as a transport in the BizTalk Messaging Manager, you may receive the following error message: |
| 27892 | When you are using the Microsoft BizTalk Editor or the Microsoft BizTalk Mapper to access a WebDAV repository on a Microsoft Internet Information Services (IIS) server that is running on a port other than the default TCP port 80, you may receive an... |
| 27893 | When you configure a channel that is bound to a port that uses a Reliable Messaging envelope, if you set the |
| 27894 | On a channel's |
| 27895 | In Visio, you experience performance degradation when performing any of the following: You close a property dialog box. You start BizTalk Orchestration Designer. You create a page. |
| 27896 | This article describes how to create a BizTalk Application Integration Component (AIC) that sends a document to a trading partner's Internet Information Services (IIS)-based server and writes the IIS server's response to a text file. This s |
| 27897 | The |
| 27898 | If you try to open a schedule file that is already open in BizTalk Orchestration Designer, you receive the following error message: |
| 27899 | The |
| 27901 | Many schedules that are running or dehydrated may cause high memory usage. This high memory usage may prevent additional schedules from being instantiated due to exhausted system resources. This high level of memory usage only occurs if the |
| 27902 | If you leave a few drawings open in BizTalk Orchestration Designer, close Orchestration Designer, and try to start Orchestration Designer again immediately, you may receive the following error message: Microsoft Visio has encountered a problem and... |
| 27903 | In BizTalk Orchestration Designer, if you click Print on the File menu when no printer is installed, Orchestration Designer closes, and then you receive the following error message: Microsoft Visio has encountered a problem and needs to close. We are... |
| 27904 | The XLANG file data source name (DSN), which BizTalk Orchestration uses to connect to the XLANG database, uses Microsoft Windows security by default. This article describes how to modify the XLANG DSN to use SQL security. IMPORTANT : This modification... |
| 27905 | The BizTalk Orchestration Designer may take an unusually long time to start. This problem occurs if Orchestration Designer is running on Microsoft Visio 2002. |
| 27906 | During BizTalk Server setup, if you cancel the setup process after one or more databases are created, the newly created databases are not removed. |
| 27907 | The BizTalk tracking database may contain entries that indicate that an interchange was not transmitted successfully. These entries appear with a status of DTA_ERR_INTERCHANGE_TRANSMISSION_FAILED_HIT_MAX_RETRIES (nError value of 9). These entries... |